managerRoot


URI

http://<server>:<port>/{iserver}/manager[.<format>]

Used to manage the service root resources, all the managed items will be listed. The {iserver} value is iserver or iportal,that is, the URI address in iPortal management services is iportal.

iServer supports all the management service resources; the management service resources supported by iPortal include: securityManager , logs , logsOperation, logsHar resources and its sub-resources.

 All the resources under portalManager directory are the portal management resources, only supported by iPortal.

Supported methods

GET, HEAD

Child resources

workspaces, tileService, tileStorages, tileVersions, fileManager, serverStatus , securityManager , instances , logs , logsOperation, logsHar , clusterOverview , clusterConfig , clusterMembers , clusterReporterConfig, dataflow, streaming

Introduction

The managerRoot resource is the root node for SuperMap iServer to manage services and it is also the entrance to access management service REST API. Users can get the child resource information through the GET request on the managerRoot resource. These child resources can be used to manage current GIS services. Items that can be managed include service component sets, service provider sets, service components, service providers, service interfaces, service instances.

For managed resources, 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.

Resource hierarchy

HTTP request methods

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

http://localhost:8090/iserver/manager.rjson

GET request

Gets the representation of the managerRoot resource, hat is, the entrance to all manageable items of the current GIS service.

Response structure

Suppose we implement the GET request on the managerRoot resource to get resource information list in the current application, information list of service component (set), service interface, service provider (set), etc. for example. The returned representation of a single resource is as follows:  

Field Type Description
name String The resource name.
path String The resoruce URI.
resourceConfigID String The ID of the implementation class of the current resource in the resource configuration file.
resourceType ResourceType The resource type.
supportedMediaTypes List<MediaType> The support format of resource representation.

Response example

The rjson format response result after implementing the GET request on the managerRoot resource (http://localhost:8090/iserver/manager/instances/restart.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 managerRoot resource exists, or if the managerRoot resource can be accessed by clients. It can also determine if the managerRoot resource supports an output format <format> if performed on a URI with .<format> included.

See