URI
<myData_uri>/services[.<format>]
Supported Methods
Parent Resource
Description
The services resource is used to get the published service information of uploaded data.
Supported Methods:
- GET: Get the published service information of uploaded data.
- HEAD: Check whether the services resource exists or whether the permissions allow access to the services resource.
Supported output formats: RJSON, JSON, HTML, XML.
Resource hierarchy
HTTP Request Methods
Perform HTTP requests on the following URI. The rjson output format is used as an example, where supermapiportal is the server name.
http://supermapiportal:8190/iportal/web/mycontent/datas/{id}/services.rjson
GET Request
Get the published service information of uploaded data.
Response Structure
The returned resource representation structure is as follows:
| Field | Type | Description |
| dataID | Integer | The ID of the data. |
| serviceID | String | The ID of the service. |
| serviceNode | String | The ID of the server node where the service is published. |
| serviceName | String | The alias of the published service. |
| serviceStatus | ServiceStatus | The status of the published service, including: UNPUBLISHED, PUBLISHING, PUBLISHED, PUBLISH_FAILED, DOES_NOT_INVOLVE, UNPUBLISHED_FAILED. |
| serviceType | DataServiceType | The type of the published service. Currently supported service types include: RESTDATA (data service), RESTMAP (map service), and RESTREALSPACE (3D service). |
| createTime | long | The creation time of the service. |
| updateTime | long | The update time of the service. |
| address | String | The published service address. If the service proxy is enabled, the proxy service address is displayed. |
| accessCount | long | The number of times the published service was accessed on that day. |
Response Example
Perform a GET request on the services resource: http://localhost:8190/iportal/web/mycontent/datas/9/services.rjson. The rjson format response is:
[
{
{
"accessCount": 0,
"address": "http://192.168.120.40:8091/iserver/services/map_City/rest",
"createTime": null,
"dataID": 9,
"serviceID": "map_City",
"serviceName": null,
"serviceNode": "dz3l683h",
"serviceStatus": "PUBLISHED",
"serviceType": "RESTMAP",
"updateTime": null
}
]
HEAD Request
Returns the same HTTP response headers as the GET request, but without the response entity. Metadata information contained in the response headers can be retrieved without transferring the entire response content. Metadata information includes media type, character encoding, compression encoding, entity content length, etc.
A HEAD request can be used to check whether the services resource exists or whether the client has permission to access the services resource. By performing a HEAD request on the URI with .<format> appended, you can also quickly determine whether the services resource supports the <format> format representation.