myServices

URI

<myContent_uri>/services[.<format>]

Supported methods

GET, HEAD

Parent resource

myContent

Introduction

The myServices resource is the collection of all the services registered by the current user.

Supported Methods:

GET: Get the list of all the services registered by the current user.
HEAD: Check whether the myServices resource exists. or if the current user has the permission to access the myServices resource.

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

Resource hierarchy

HTTP request methods

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

http://supermapiportal:8090/iportal/web/mycontent/services.rjson

GET request

Gets the list of all the services registered by the current user.

Request parameter

If this parameter is not set, then the list of registered services on the first page will be returned. If the parameter is set, the list of the services registered by the user will be returned. The request parameters are included in URI.

Field	Type	Description
tags	String[]	Filter by tag.
userNames	String[]	Filter by user who registered the service. This parameter has expired, that is, SuperMap iPortal 9D or higher version will no longer use this parameter.
types	SourceType[]	Filter by service type.
checkStatus	CheckStatus	Filter by verification status.
offline	Boolean	Filter by whether the service is offline.
orderBy	ServiceOrderBy	Filter by sort field. Where, the ServiceOrderby.VISITCOUNT, which means sorting by the service count, only takes effect when enabling the service proxy function.
orderType	OrderType	Sort by ascending or descending.
keywords	String[]	Filter by keyword.
currentPage	int	Filter by page number.
pageSize	int	Filter by page size.
filterFields	FilterFields[]	Field filtering for keyword queries. Field names need to be capitalized. For example, to filter according to the key characters of the user who registered the service, you need to set: keywords=["admin"]&filterFields=["NICKNAME"].

Response structure

Execute a GET request on the myServices resource to return the list of all the scenes that the current user is allowed to check. It includes the following fields:

Field	Type	Description
content	List<ServiceInfo>	Page content.
currentPage	int	The current page number.
pageSize	int	The size of each page.
searchParameter	SearchParameter	The search parameter for the current page.
total	int	The total record number.
totalPage	int	The total number of pages.

Response example

The returned rjson format representation after executing the GET request on the myServices resource http://localhost:8090/iportal/web/mycontent/services.rjson is as follows:

{ "content": [ { "addedMapNames": null, "addedSceneNames": null, "authorizeSetting": [ { "aliasName": "admin", "entityId": null, "entityName": "admin", "entityType": "USER", "permissionType": "DELETE" } ], "checkStatus": "SUCCESSFUL", "createTime": 1473737605014, "description": "", "enable": true, "id": 1, "isBatch": false, "isDataItemService": false, "linkPage": "http://192.168.120.40:8091/iserver/services/map-changchun/rest", "mapInfos": [ { "id": null, "mapThumbnail": "http://192.168.120.40:8091/iserver/services/map-changchun/rest/maps/ChangchunMap/entireImage.png", "mapTitle": "ChangchunMap", "mapUrl": "http://192.168.120.40:8091/iserver/services/map-changchun/rest/maps/ChangchunMap", "serviceId": 1 }, { "id": null, "mapThumbnail": "http://192.168.120.40:8091/iserver/services/map-changchun/rest/maps/ChangchunMap_Local/entireImage.png", "mapTitle": "ChangchunMap_Local", "mapUrl": "http://192.168.120.40:8091/iserver/services/map-changchun/rest/maps/ChangchunMap_Local", "serviceId": 1 } ], "metadata": null, "metadataString": "", "nickname": "admin", "offline": false, "proxiedUrl": null, "resTitle": "changchun1", "scenes": [], "serviceRootUrlId": null, "tags": null, "thumbnail": null, "type": "MAP", "updateTime": 1473753306373, "userName": "admin", "verifyReason": null, "version": null, "visitCount": 0 } ], "currentPage": 1, "pageSize": 9, "searchParameter": { "checkStatus": null, "currentPage": 1, "currentUser": null, "dirIds": null, "enable": null, "filterFields": null, "groupIds": null, "isBatch": null, "isNotInDir": false, "keywords": null, "offline": null, "orderBy": null, "orderType": "ASC", "pageSize": 9, "resourceIds": null, "tags": null, "types": null, "userNames": [ "admin" ] }, "total": 1, "totalPage": 1 }

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