clusterOverview

URI

Supported methods

Parent resource

Introduction

clusterOverview is the cluster configuration information resource. You can view all configuration of the current cluster through this resource, including the cluster usage, cluster child node list and cluster reporter.

Cluster means to register SuperMap iServer services to the cluster server, and provide the single customer view service. Using the cluster can integrate GIS server resource, which provides the system tolerance and concurrency.

Supported Methods:

GET: Gets the confiuration information of the current cluster, including cluster configuration usage, cluster child nodes list and the cluster report.
HEAD: Check whether the clusterOverview resource exists. or to access the clusterOverview resource.

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

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/manager/cluster.rjson

GET request

Get the confiuration information of the current cluster, including cluster configuration usage, cluster child nodes list and the cluster report.

Response structure

Performs GET request to the clusterOverview resource. The result of the representation returns as follow.

Field	Type	Description
memberAuthorizedCount	int	The number of cluster child node.
members	List<ClusterMemberInfo>	The member information of the cluster child nodes.
reporterUsedCount	int	The reporter number..
说明setting	ClusterSetting	The cluster configuration information.

Response example

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

{ "memberAuthorizedCount": 2, "members": [ { "active": true, "agentId": null, "authorized": true, "hostName": "HOST1", "id": "e0dec207b2e547f3bf908327fab03585", "ip": "192.168.17.149", "isAgent": false, "isControllable": false, "isOffLine": false, "isTileWorker": false, "port": 8091, "uriRoot": "http://192.168.17.149:8091/iserver/services" }, { "active": true, "agentId": null, "authorized": true, "hostName": "HOST2", "id": "d7c64eb1ea1a4f11983082488ab9fba9", "ip": "192.168.17.148", "isAgent": false, "isControllable": false, "isOffLine": false, "isTileWorker": false, "port": 8090, "uriRoot": "http://192.168.17.148:8090/iserver/services" } ], "reporterUsedCount": 0, "setting": { "DEFAULT_CONNECT_TIMEOUT": 20000, "DEFAULT_READ_TIMEOUT": 120000, "address": "http://localhost:8090/iserver/services/cluster", "connectTimeout": 2000, "dataSyncInterval": null, "enabled": true, "excludeFormats": null, "includeFormats": null, "localAddress": null, "readTimeout": 120000, "reporters": [ { "address": "http://anotherclusterservice:8090/iserver/services/cluster", "enabled": false, "isTileWorker": false, "iserverId": "d7c64eb1ea1a4f11983082488ab9fba9", "localAddress": null, "token": "" } ], "status": "OK", "token": null, "useLocalCluster": true } }

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 clusterOverview resource exists, or if the clusterOverview resource can be accessed by clients. It can also determine if the clusterOverview resource supports an output format <format> if performed on a URI with .<format> included.

URI