Publishing the Results as Geoprocessing Service

After the configuration file is set up and the tool is executed, the results of the tool should be published as a Geoprocessing service in the ArcGIS server

To publish the Extract_​Delta_​Changes tool results as a Geoprocessing service:

1. In the ArcCatalog tool, navigate to Geoprocessing Menu and then click Results.
   • The results of the tool are displayed.
2. Right-click Extract_​Delta_​Changes […] and select Share As and then click Geoprocessing Service.
3. In the Share as Service window, select Publish a Service, and then click Next.
4. From the Choose a Connection drop-down list, select ArcGIS Server.
5. Enter ExtractDeltaChanges in the Service Name field and click Next.
6. Select Create New Folder.
7. Enter GPServices and click Continue.
8. In the Service Editor dialog box, select the required parameters in the Extract_​Delta_​Changes node. Then, provide the details in the Description field:
   • Task_​Name: Enables the service to retrieve GUIDs of the requested feature classes. The other possible values for task are:
     • Query Specific Changes
     • Query Complete Changes
     • Query Inserts
     • Query Updates
     • Delete Version
   • Execution_​Mode: Assists in retrieving all the GUIDs of the feature class or updated GUIDs of the feature class. The possible values are “Initial” and “COU” (Change Only Updates.
   • Feature_​Class_​List: Enables to query the GUIDs in the feature class of interest. Only one feature class name should be passed to service at a time.
   • Feature_​Count_​Range: The limit on the records that can be sent using QueryCompleteChanges task.
   • Fields: Helps the GP service to extract the information only for the fields of interest. Oracle Utilities Application Framework batch process reads the list of fields from extendable lookup and passes the value as a comma separated list.
   • Life_​Cycle_​Status: Field and its value (comma separated) to identify if a feature is Abandoned.
   • Skip_​Feature: Configuration to identify features to skip while retrieving data.
   • GUIDs: The list of GUIDs should be provided to extract the attribute information for the mentioned GUIDs.
   • WKID: The WKID of the coordinate system in which the features has to be present in results.
   • Source_​Version: Establishes a connection with the underlying Geodatabase.
   • Temp_​Version: Creates a temporary version on top of the DEFAULT/parent version.
   • WAM_​Sync_​Version: Connects to WAMSync version and performs a version difference between the Temp version and the WAMSync version.
   • Response_​XML: Output XML response.
9. Provide the Summary, Tags, and Description (Optional parameters).
10. Click Analyze and then click Publish.
11. Click OK.

The service should be published in asynchronous mode. It is set by default while publishing the Geoprocessing service.

Important! If any error occurs while publishing the Geoprocessing service, modify the configuration ‘synchronous’. After the service is published, navigate to the service properties in ArcGIS server and change the configuration to ‘asynchronous’.

While publishing the Geoprocessing service, configure the service instances and client timeout configurations (using pooling option) based on the number of records that need to be in sync from GIS. The configurations can also be altered after the service is published in ArcGIS server.

To configure Geoprocessing service instances:

1. Login to ArcGIS Server Manager.
   • https://xxxxxxxxxx:6443/arcgis/manager
2. Navigate to the Geoprocessing service directory where the Extractor program is deployed.
   • For example: GPServices > Extract DeltaChanges
3. From the service options, select Pooling.
4. Specify the minimum and maximum number of instances per machine along with maximum time a client can use a service.
   • The configurations are based on the number of records processed by the Geoprocessing service. On an estimate, a single Geoprocessing service instance can process 90000+ records at a time. However, the number of records are tentative and is dependent on multiple factors including the number of fields for which information is requested and memory consumed by the Geoprocessing service. The number of instances should be selected accordingly.
   • Also, configure the time in seconds (example: 36000) during the initial load based on the number of records to be synchronized and the maximum time a client can use the Geoprocessing service.
5. Restart the Geoprocessing service/ArcGIS server for the configurations to reflect.