<managerRoot_uri>/instances[.<format>]
The service instance list. Information of all service instances and configuration can be acquired through the instances service.
Supported Methods:
Supported output formats: rjson, json, html, xml.
Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.
http://supermapiserver:8090/iserver/manager/instances.rjson
Gets all current service instances and the corresponding configuration information.
A provider list will be returned by implementing the GET request on the instances resource. The representation structure of a single component will be as follows:
Field | Type | Description |
authorizeSetting | AuthorizeSetting | The authorization setting. |
componentName | String | Name of the consumed service component. |
componentSetName | String | Name of the consumed service component set. |
componentType | String | Name of the consumed service component. |
enabled | boolean | Whether the current service instance is usable. The default is true, indicating usable. |
id | String | ID of the service instance. |
interfaceName | String | Name of the consumed service interface. |
interfaceType | String | Type of the consumed service interface. |
name | String | Name of the current service instance. |
Status | String | The service status information, the value can be INITIALIZING, OK or FAILED, indicating service is being initialized, service has been started successfully, or service failed to start respectively. While the value of enabled is false, the value of state is DISABLED. |
The returned representation after implementing the GET request on sample instances resource http://localhost:8090/iserver/manager/instances.rjson is as follows:
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 instances resource exists, or if the instance resources can be accessed by clients. It can also determine if the instances resource supports an output format <format> if performed on a URI with .<format> included.