<portalStatistics_uri>/resource/accumulatedcount[.<format>]
accumulatedResourceCount is the resource that records the iPortal resources' increase during a period of time. The increase number of certain types of resources can be get by sending GET request.
Supported Methods:
Supported output formats: rjson, json, html, xml.
Implement the HTTP request on the following URI, where supermapiportal is the server name, with rjson being the output format.
http://supermapiportal:8090/iportal/manager/portalstatistics/resource/accumulatedcount.rjson
GET: To get the the increase number of several types of iPortal resources.
Following arguments need to be transmitted in the request, with arguments contained in URI:
| Name | Type | Description |
| types | ResourceType[] | [Required] ResourceType including:MAP(Map resource),SERVICE(Service resource),SCENE(Scene resource),DATA(Data resource),APP(Application resource) |
| startTime | Long | The start time of resource sum record. If not a positive number, it will be queried from the earliest record. The value is the milliseconds from 00:00:00 GMT January 1, 1970. |
| endTime | Long | The end time of the accumulated Resource Count record. If it's null or not a positive number, use the server time as the end time. The value is the milliseconds from 00:00:00 GMT January 1, 1970. |
To get the accumulated Resource Count of all types of newly added resources during a period of time, set parameters as: startTime=1492063745780&endTime=2492063745789&types=[MAP,SERVICE,SCENE,DATA,APP]&intervalType=DAY. The following lines describe the resource in rjson format returned by sending GET request to the accumulatedResourceCount resource:http://localhost:8090/iportal/manager/portalstatistics/resource/accumulatedcount.rjson?startTime=1492063745780&endTime=2492063745789&types=[MAP,SERVICE,SCENE,DATA,APP]
{
"APP": 0,
"DATA": 0,
"MAP": 2,
"SCENE": 0,
"SERVICE": 1
}
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 whether the accumulatedResourceCount resource exists, or whether the client has the permission to access it. It can also determine if the accumulatedResourceCount resource supports an output format <format> if performed on a URI with .<format> included.