Behavior of a hosting server
When you designate a federated ArcGIS GIS Server site to act as the hosting server, you provide publishers the ability to create cached map tiles, hosted feature layers, and scene services (tile layers, feature layers, and scene layers). These users do not require any ArcGIS products on their computers; they may just publish the services by uploading a shapefile or a .csv file through the organization; however, publishing through ArcGIS Pro is still an option.
Services published directly to the organization are hosted services, and the services are placed in an ArcGIS Server folder called Hosted on the hosting server. This way, you can keep track of which services are hosted services and which are not.
If you delete a hosted layer item in the organization, the service is also deleted from the hosting server. Similarly, if you delete an item that references a service on a federated server, deleting the item from the portal deletes the service. This is true both for services published to the federated server and hosted services published directly to the organization.
The following table lists supported hosted services and their item types:
|
ArcGIS Server service type |
Portal item type |
|---|---|
|
Cached map service |
|
|
Cached map service with feature service |
|
|
Feature service |
|
|
Image service |
|
|
Scene service |
|
|
WFS service |
|
|
Vector tile service |
|
|
Knowledge graph service |
Knowledge Graph |
The image service that a hosted imagery layer references runs on the raster analysis server or image hosting server, not the hosting server.
The knowledge graph service that a hosted knowledge graph references runs on the knowledge server, not the hosting server.
When viewing and editing hosted service properties in Server Manager, only a subset of ArcGIS Server capabilities or operations are available. For example, some services will not display instance information in the service gallery or on the service Pooling tab in Server Manager.
A hosting server needs sufficient storage space, CPU, and memory to accommodate the services that it will host. Train your publishers to understand how services impact resources on the hosting server, and monitor the metrics on the hosting server machines to avoid exceeding capacity.