services


URI

http://<server>:<port>/iserver/services[.<format>]

Supported methods

GET, HEAD

Child resources

root, login, logout, tokens, profile, proxyservers

Introduction

The services is the service list resource. Users can get GIS Service List and Metadata provided by current server through accessing the services resource. The CSW representation of the services resource is the catalog service of OGC-compliant CSW 2.0.2 provided by SuperMap iServer.

While service security has been enabled, logging or Token authentication are needed to access protected services. Authentication information needs to be carried while accessing resource in the REST method. For example, Cookie information generated while logging in HTTP Form-based Authentication can be carried in the HTTP request head, or you can Access Protected REST Service Resources based on Token. Cookie information can be acquired whiling logging and Token can acquired through the token resource.

Supported Methods:

Supported output formats: rjson, json, html, xml, csw.

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/services.rjson

GET request

Gets the list of all services on the server.

Response structure

Returns service list, including the basic information osf services, which should inlcude the following fields:

Field Type Description
componentType String

Service component type, for example, the type of the data component is "com.supermap.services.components.impl.DataImpl".

interfaceType String

Service interface type, for example, the type of restlet interface is "com.supermap.services.rest.RestServlet".

name String The service name, "data-world/rest" for instance.
url String The service URL, "http://localhost:8090/iserver/services/data-world/rest" for instance.

Response example

The returned rjson format resource representation after implementing the GET request on the services resource http://localhost:8090/iserver/services.rjson is as follows:

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can be used to check if the services resource exists, or if the services resource can be accessed by clients. It can also determine if the services resource supports an output format <format> if performed on a URI with .<format> included.

See