managerRoot_uri>/workspaces[.<format>]
Service access log is that the service administrator monitor all services published by server, getting the HTTP request data stream HAR file.
logsHar resource is used to get the service access log. It is meaningful only when enable service access log in Log Configuration", and add the service to the monitoring list.
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/logsHar.rjson
Gets the service access log.
Implement GET request on the logsHar resource. The response structure is as follows:
| Field | Type | Description |
| harFileSizes | Map<String,String> | The file name and file sizes set of all har file. |
| harZipFilePath | String | After conpressing har log as zip, the path of zip package is used to download. |
| isExisted | boolean | Whether there is the Har log file, if not, no download. |
Implement the GET request on the logsHar resource http://localhost:8090/iserver/manager/logsHar.rjson. Return rjson results:
{
"harFileSizes": {
"iServerHTTPArchive.har": "989 KB"
},
"harZipFilePath": "E:\\\\iserver\\\\supermap_iserver_710_11814_1095_win64_deploy\\\\bin\\\\..\\\\logs\\\\harLog.zip",
"isExisted": true
}
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 logsHar resource exists, or if the logsHar resource can be accessed by clients. It can also determine if the logsHar resource supports an output format <format> if performed on a URI with .<format> included.