This topic describes the properties you should configure for a locator that you are sharing to your portal using the Share Locator pane. These properties are set during the sharing configuration process on the Configuring tab of the Sharing pane, just before you share.
The available properties for locators shared to your portal from the Share Locator pane are described below.
Capabilities
Expand the Capabilities section to choose the capabilities to enable for your portal locator. Capabilities specify the allowed operations for your geocode service including Geocode, Reverse Geocode, and Suggest.
Operations allowed
- Geocode—Find addresses or geocode a table of addresses
- Reverse Geocode—Return an address for a point location on a map
- Suggest—Generate auto-complete suggestions for user input
Parameters
Expand the Parameters section to set the basic parameters for your locator shared to your portal. These include the following:
Choose the cluster hosting the service—The cluster that will host your locator.
A cluster is a group of one 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 faster 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 in 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.
Pooling
Expand the Pooling section to specify the minimum and maximum number of instances of the portal locator 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 portal locator will accommodate users.
Processes
Expand the Processes section to specify how the portal locator will run as a process on the server.