processingjobs

URI

<root_uri>/{version}/jobs[.<format>]

Supported methods

GET, HEAD

Parent resource

root

Child resources

spatialanalystJobs, dataprocessingJobs

Introduction

processingJobs resource indicates the root directory of distributed analysis services. It includes distributed spatial data processing jobs and distributed spatial analysis jobs supported by iServer.

Supported Methods:

Supported output formats: RJSON, JSON, HTML, XML.

Resource hierarchy

 

HTTP request methods

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.rjson

GET request

Gets the list of distributed spatial processing jobs.

Response structure

After executing a GET request on the resource, the response entity is a set of data processing resource descriptions, and the response fields of single resource are as follows:

Field Type Description
name String The name of data processing resource.
path String Resource URL.
resourceConfigID String The configuration item ID of the resource.
resourceType String The resource type.
supportedMediaTypes String[] The media-type of the supported representation.

Response example

Sending a GET request to jobs, the description of returned format rjson is as follows:

[

  {

    "name": "mappingJobs",

    "path": "http://supermapiserver:8090/iserver/services/distributedanalyst/rest/jobs/mapping",

    "resourceConfigID": null,

    "resourceType": null,

    "supportedMediaTypes": null

  },

  {

    "name": "spatialanalystJobs",

    "path": "http://supermapiserver:8090/iserver/services/distributedanalyst/rest/jobs/spatialanalyst",

    "resourceConfigID": null,

    "resourceType": null,

    "supportedMediaTypes": null

  }

]

HEAD request

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 processingJobs 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 processingJobs resource supports the <format> representation.

See