Access requirements
Required privileges
The Enterprise Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Enterprise Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Enterprise Directory API. For security reasons, all POST requests made to the Enterprise Administrator API must include a token in the request body.
Description
An individual microservice property template resource returns the default property template, which defines the default scaling and resource allocations for a specific microservice. The default property configuration is applied to microservices that match the type, provider, and mode values of the corresponding template. The default properties of a microservice can be updated using the Edit.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default format is Values: |
Response properties
| Property | Details |
|---|---|
| The microservice mode. A mode type of Values: |
| The microservice provider. Only microservices related to an ArcGIS service type have a provider type. A provider type of Values: |
| The template ID. Example |
| The microservice type. For example, if the microservice is a shared feature server containing feature services, Values: |
| The JSON object representation of the template's specifications, including replicas and container resources. Example |
| The number of replicas for the microservice. For manual scaling, the value for both Example |
| The minimum and maximum resource allocations for the microservice, including the minimum memory ( Example |
| The date, in milliseconds from epoch format, of the latest revision to the template. Example |
Example usage
The following is a sample request URL used to access an individual microservice property template resource:
https://organization.example.com/<context>/admin/system/deployments/properties/11abdae1-e44a-422c-911a-e8282dadf74a?f=pjsonJSON Response example
{
"mode": "Dedicated",
"provider": "ArcObjects11",
"id": "pfnpl9gr7gi44g1ufg3h9",
"type": "MapServer",
"spec": {
"replicas": {
"min": 3,
"max": 3,
"scalingMode": "manual"
},
"containers": [
{
"name": "main-container",
"resources": {
"memoryMin": "500Mi",
"memoryMax": "2Gi",
"cpuMin": "0.125",
"cpuMax": "2"
},
"containerImageKey": "MAP_SERVER"
},
{
"name": "filebeat",
"resources": {
"memoryMin": "32Mi",
"memoryMax": "50Mi",
"cpuMin": "0.05",
"cpuMax": "0.25"
},
"containerImageKey": "FILEBEAT"
}
]
},
"revision": 1618223886572
}