ArcGIS Server – ArcGIS Server Geoprocessing Service: Resolving Issues with Asynchronous and Synchronous Processes

arcgis-servergeoprocessing-servicepython

I'm working a geoprocessing service for ArcGIS 10.1+ written in Python / arcpy.

It runs fine in asynchronous mode, but does not write output to disk when switched to synchronous. I know that synchronous services are supposed to use the arcgisoutput directory, but nothing appears there, or output is deleted before the client can request it.

In forming the output path, I use the arcpy.env.scratchWorkspace variable, which is set to the jobs directory in both async and sync.

What can explain this instability in an ArcGIS Server geoprocessing service when running synchronously?

Thanks in advance

Best Answer

Async writes to the Job directory and those results are persisted until the Server cleans them up. Sync sends the results back to the client.

With a GP Service you should return a file or data, not a directory (especially with Sync). The framework is meant to return these outputs, it isn't meant to return a folder you can browse to. You'd have to expose output directories and then send back a basic string of that location.

In this case you may need to set your output to file and return it like:

arcpy.SetParameterAsText(#, os.path.join(arcpy.env.scratchFolder, "myfile.zip"))

Related Solutions

[GIS] Publishing Geoprocessing Service with ArcGIS Server

Server object instance creation failed on all SOC machines is triggered when the SOC account does not have access to the resources that your trying to publish.

Try right clicking ArcCatalog and running it as the SOC account. Can you browse to \MyServer\ArcGIS Resources\Test\ and able to see the MXD, layers and toolbox?

Everything used in the model needs to be accessible to the SOC.

See preparing resources for publishing for more details on how to setup the relevant permissions.

[GIS] Truncate Table tool with geoprocessing service

The problem was that the GP service is not able to use Feature Classes directly as input parameters. The solution to this is to use a parsing technique which would take a string from a user (name of the feature class) and then append this string variable to the full path of the feature class (I specify the geodatabase name forehand in the code).

It seemed as this is much easier to implement in Python rather than in ModelBuilder, so I've implemented this logic by using arcpy module in ArcGIS 10.1:

import arcpy
from arcpy import env
#Setting the env workspace to be an SDE geodatabase
#
env.workspace = r'C:\sde_at_DB101.sde'

#Getting the existing polygon feature class as input parameter
#
GetExistingPolyFC = arcpy.GetParameterAsText(0)
GetPolyFC = GetExistingPolyFC

# Truncate a feature class if it exists
#
if arcpy.Exists(GetPolyFC):
   arcpy.AddMessage("Polygon feature class exists, start working...")
   arcpy.TruncateTable_management(r'C:\sde_at_DB_101.sde\%s' %GetPolyFC)
   arcpy.AddMessage("Truncating table is complete")

else:
   arcpy.AddMessage("Polygon feature class does not exist")

I've used this logic for other bits of my bigger model and it works just fine as a GP service now. I've decided to rewrite the whole model as a Python script from scratch and it was much easier to implement and it performs much faster too when running the GP task.

Best Answer

Related Solutions

[GIS] Publishing Geoprocessing Service with ArcGIS Server

[GIS] Truncate Table tool with geoprocessing service

Related Question