You can publish services right away in ArcGIS Pro, because many of the service properties are set by default. However, if you expect a large volume of users to access your services, you can change the default service property values to accommodate your deployment.
When you publish a geocode service, you set properties that control how the service can be used. These properties are set during the publishing configuration process on the Configuration tab in the Publish Geocode Service pane before you publish.
The geocode services properties are described below.
You can enable the following capabilities for the geocode service in the Capabilities section:
- Geocode—Find addresses or geocode a table of addresses.
- Reverse Geocode—Return an address for a point location on a map.
- Suggest—Generate autocomplete suggestions for user input.
Set the following parameters for the geocode service in the Parameters section:
- Choose the cluster hosting the service—The cluster that will host your locator. A cluster is a group of two or more GIS servers that work together to provide services to clients.
- Maximum number of candidates returned by the server—The number of candidates returned when you find addresses interactively. The response time is less when there are fewer candidates to return. This property applies to both SOAP and REST applications.
- Maximum number of records to be processed in each batch job—The number of records, as a record set, to be processed at a time on the server when you geocode a table of addresses. The default value, 1000, is an optimal size for avoiding large overhead costs and excessive consumption of CPU resources on the server. This property only applies to applications using SOAP.
- Recommended number of records to pass in each batch job—The number of records the client passes to the server for processing at a time on the server when you geocode a table of addresses. This value must not exceed the value of the Maximum number of records to be processed in each batch job parameter. In most cases, both parameters are set with the same value. Using this parameter, the server administrator can optimize the process by controlling the number of records to be passed to the server in each batch geocoding request.
All services published with ArcGIS Server are pooled. This means that instances of the service can be shared between multiple application sessions.
Expand the Pooling section to specify the minimum and maximum number of instances of the geocode service that can run on the server at any one time. Because of the way the server shares these instances among clients, it may be that the number of clients you can support is greater than your number of running instances.
The Pooling section allows you to specify how the geocode service will accommodate users.
Expand the Processes section to specify how the locator will run as a process on the server. See Tuning and configuring services for an overview of the considerations you should understand when setting isolation, determining recycling intervals, and checking for invalid data connections.