<topologyValidator_uri>/{jobID}[.<format>]
topologyValidatorJob resource represents a topology validation analysis job. By sending a GET request to topologyValidatorJob, you can get a topology validation job's detailed configuration information, which can be retrieved by {jobID}.
Supported Methods:
Supported output formats: RJSON, JSON, HTML, XML.
Execute HTTP request on the following URI, here we take rjosn as the output format as an example. Where, supermapiserver is the server name.
http://supermapiserver:8090/iserver/services/distributedanalyst/rest/v1/jobs/spatialanalyst/topologyvalidator/{jobID}.rjson
Gets a topology validation job's detailed configuration information.
After executing a GET request on the resource, the response fields are as follows:
| Field | Type | Description |
| id | String | Application ID. |
| state | Jobstate | The status of the task. Including execution status, start time, time consuming, and so on. |
| setting | JobSetting | Lists the detailed information of the current topology validation job. |
Execute a GET request on topologyValidatorJob resource: http://supermapiserver:8090/iserver/services/distributedanalyst/rest/v1/jobs/spatialanalyst/topologyvalidator/64e3f1e9_8e4f_42b5_9f98_af204be77880.rjson, then the returned result in rjson format is as follows:
{
"id": "64e3f1e9_8e4f_42b5_9f98_af204be77880",
"setting": {
"DEFAULT_MASTER_ADRESS": "local[*] ",
"analyst": {
"datasetTopology": "smtiles_Jingjin_New_Region_1",
"inputValidating": "{\"type\":\"udb\",\"info\":[{\"server\":\"F:\\\\4.datastore\\\\Data\\\\data\\\\City - bak - bak\\\\Jingjin.udb\",\"datasetNames\":[\"New_Region_1\"]}]}",
"rule": "RegionContainedByRegion",
"tolerance": ""
},
"appName": "topologyValidator",
"args": [
"--inputSource",
"{\"sliceNum\":20,\"type\":\"udb\",\"info\":[{\"server\":\"F:\\\\4.datastore\\\\Data\\\\data\\\\City - bak - bak\\\\Jingjin.udb\",\"datasetNames\":[\"New_Region\"]}]}",
"--inputValidating",
"{\"type\":\"udb\",\"info\":[{\"server\":\"F:\\\\4.datastore\\\\Data\\\\data\\\\City - bak - bak\\\\Jingjin.udb\",\"datasetNames\":[\"New_Region_1\"]}]}",
"--rule",
"RegionContainedByRegion",
"--output",
"{\"server\":\"192.168.120.21\",\"password\":\"supermap\",\"database\":\"supermap1\",\"datasetName\":\"analystResult_1597348849\",\"blockingWrite\":null,\"type\":\"pg\",\"user\":\"postgres\"}"
],
"contextSetting": null,
"input": {
"datasetInfo": {
"available": true,
"bounds": "Left=-97.1879129784341,Bottom=38.379098407748195,Right=749.938641932885,Top=433.65169599572",
"datasetName": "New_Region",
"datasetType": "REGION",
"epsgCode": -1000,
"name": "smtiles_Jingjin_New_Region",
"readOnly": false,
"type": "UDB",
"url": "F:\\4.datastore\\Data\\data\\City - bak - bak\\Jingjin.udb"
},
"datasetName": "smtiles_Jingjin_New_Region",
"numSlices": 0,
"specField": null
},
"mainClass": "com.supermap.bdt.main.TopologyValidatorMain",
"output": {
"datasetName": "analystResult_1597348849",
"datasourceInfo": {
"alias": "supermap1_pg",
"connect": true,
"dataBase": "supermap1",
"driver": "PostgreSQL ANSI",
"engineType": "POSTGRESQL",
"exclusive": false,
"openLinkTable": false,
"password": "supermap",
"readOnly": false,
"server": "192.168.120.21",
"user": "postgres"
},
"outputPath": "F:\\1.package\\20171021\\supermap_iserver_901_15420_4680_win64_zip\\webapps\\iserver\\processingResultData\\Analyst\\64e3f1e9_8e4f_42b5_9f98_af204be77880\\topology.smwu",
"type": "pg"
},
"serviceInfo": {
"targetDataPath": "F:\\1.package\\20171021\\supermap_iserver_901_15420_4680_win64_zip\\webapps\\iserver\\processingResultData\\Analyst\\64e3f1e9_8e4f_42b5_9f98_af204be77880\\topology.smwu",
"targetServiceInfos": [
{
"serviceAddress": "http://supermapiserver:8090/iserver/services/map-topology22/rest",
"serviceType": "RESTMAP"
},
{
"serviceAddress": "http://supermapiserver:8090/iserver/services/data-topology22/rest",
"serviceType": "RESTDATA"
}
]
},
"serviceRoot": "http://supermapiserver:8090/iserver/services/",
"sparkLogFile": null
},
"state": {
"elapsedTime": 12651,
"endState": true,
"endTime": 1508833694778,
"errorMsg": null,
"errorStackTrace": null,
"publisherelapsedTime": 8446,
"runState": "FINISHED",
"startTime": 1508833669915
}
}
Returns the same HTTP response header as the GET request, but no response entity, which can be used to retrieve the meta data contained in response message header without having to transmit the entire response content. Meta data information includes media type, character coding, compression coding, entity content length, etc.
HEAD request is used to determine whether the topologyValidatorJob resource exists, or if the user has the authority to access it. By executing an HEAD request with a .<format> URI, you can quickly determine whether the topologyValidatorJob resource supports the <format> representation.