Test Match Job Request JSON Question
Article ID: 144558
Updated On:
Products
Issue/Introduction
We need one more confirmation from the Broadcom team about referred JSON here.
In some cases, our pools do not have Test Match ID and hence if the value of Level Id and Summary Table fields ( highlighted Yellow) are blank in the API call, will this cause any problems in TDM?
TDM Job Request : TDM Job Request: {
"jobPubParams": {
"almjobs": [{
"almdomain": "ADMIN",
"almjobType": "ATTACH_TM_RESULTS",
"almobjectID": 12086,
"almobjectType": "tli",
"almuser": "ALMServiceAccount",
"almproject": "DevTestp_SQAR_PLAY",
"almtestName": "HJSMakeData(3)",
"description": "",
"isRemote": "True",
"jobTitle": "Attach Test Match Results to ALM",
"levelID": "7848",
"profile": "TDMDM",
"projectID": "7829",
"seq": 3,
"summaryDataPoolID": 0,
"tableName": "V_ENSEMBLEDM_CUBE",
"testColumnName": "TEST_NAME"
}],
"rallyJobs": [],
"jobParams": [],
"publishJobs": [{
"batchEngineThread": "ANY",
"dataSourceProfile": "",
"dataTargetProfile": "",
"description": "",
"jobTitle": "Group Job",
"levelID": "7847",
"publishVariables": [{
"name": "TEST_ENV_SELECT",
"value": "ITE3"
}, {
"name": "almoid",
"value": 12086
}, {
"value": "Individual",
"name": "ACCOUNT_SUB_TYPE"
}, {
"value": "Individual",
"name": "ACCOUNT_TYPE"
}, {
"value": "No",
"name": "AMT_PASTDUE"
}, {
"value": "Active",
"name": "BAN_STATUS"
}, {
"value": "Any",
"name": "BILL_CYCLE"
}, {
"value": "Any",
"name": "HOME_CREDIT"
}, {
"value": "Yes",
"name": "REGISTERED_BAN"
}, {
"name": "almp",
"value": "DevTestp_SQAR_PLAY"
}, {
"name": "almd",
"value": "COMPANY"
}, {
"name": "TEST_ENV",
"value": "ITE3"
}, {
"name": "TEST_NAME",
"value": "HJSMakeData(3)"
}],
"seq": 1,
"iterations": 1,
"defaultPublishID": 6556
}, {
"batchEngineThread": "ANY",
"dataSourceProfile": "",
"dataTargetProfile": "",
"description": "",
"jobTitle": "Group Job",
"levelID": "7850",
"publishVariables": [{
"name": "almoid",
"value": 12086
}, {
"name": "TEST_NAME",
"value": "HJSMakeData(3)"
}, {
"name": "TEST_ENV",
"value": "ITE3"
}, {
"name": "TEST_ENV_SELECT",
"value": "ITE3"
}, {
"name": "AUTO_DELIVERYPATH",
"value": "tdmTempFolder"
}, {
"name": "INT_JOBTYPE",
"value": "L"
}],
"seq": 4,
"iterations": 1,
"defaultPublishID": 5052
}],
"testMatches": [{
"batchEngineThread": "ANY",
"description": "Set Search Criteria",
"isRemote": true,
"jobParams": [{
"paramKey": "ClearDown",
"paramValue": "Y"
}, {
"paramKey": "SimulationRun",
"paramValue": "N"
}, {
"paramKey": "RetryPriorPartialMatches",
"paramValue": "N"
}, {
"paramKey": "AllowPartialMatch",
"paramValue": "Y"
}, {
"paramKey": "SnapshotTestMartBeforeMatch",
"paramValue": "N"
}, {
"paramKey": "SnapshotTestMartAfterMatch",
"paramValue": "N"
}, {
"paramKey": "SnapshotMartWithNoMatchingNoCleardown",
"paramValue": "N"
}],
"jobTitle": "Group Job"
"levelID": "7848",
"profileName": "TDMDM",
"seq": 2,
"summaryTable": "V_ENSEMBLEDM_CUBE",
"testCaseName": "HJSMakeData(3)",
"testColumnName": "TEST_NAME",
"testMatchDataPoolID": "7848",
"useTempTable": false
}],
"exportJobs": [],
"selfServiceEmailMandate": false,
"email": "[email protected]",
"globalThreadName": "ANY",
"scheduledDateTimeInMillisec": "2020-01-23T12:03:05Z",
"scheduledDateTimeInMillis": 1579802585777,
"currentDay": 23,
"currentMonth": 1,
"currentYear": 2020,
"globalSourceConnection": "",
"globalTargetConnection": "",
"jobSubmissionOrder": "1",
"jobTitle": "Reserve BAN Test Data Data Request",
"username": "LitmusT"
},
"advancedToggleFlag": true,
"dataDesign": {
"projectID": "7829",
"versionID": "7831"
}
Environment
Test Data Manager
TDM Portal
Resolution
Missing the "levelID" and "summaryTable" will cause problems.
Based on the "levelID" a context gets prepared and retrieved.
Without it, we will get an "Error in ALMServiceClient method" exception.
If the "levelID" is wrong, we will get an "org.apache.axis.AxisFault: Error getting context for " exception.
The "summaryTable" is used in creating the hash code for the object.
Feedback
