[GIS] Geoprocessing service saved data to scratch gdb

arcgis-serverfile-geodatabasegeoprocessing-servicemodelbuilder

I created and published a geoprocessing service from a toolbox. It works with a file geodatabase on my local drive. When run as a tool in ModelBuilder, it worked well and wrote data into the file geodatabase perfectly. However, when I published it as geoprocessing service and triggered it via REST service, it wrote data into the scratch.gdb in the job directory on the ArcGIS Server directories.

How can I configure the tool/model, or service or arcgis server to make it work with the original file geodatabase instead of the scratch file geodatabase?

Best Answer

To avoid situations like these, I rework my toolbox until I am satisfied with it, copy it to a shared folder on the AGS machine and publish the service from there, making sure that model's scratch gdb is referenced in the environment settings correctly.

You should also register the gdb with ArcGIS Server. Anecdotally, I've found this process to be hit-and-miss; half of my gdbs get copied over to the local Server directories because "it's not registered", even though it is. This should not be such a big problem though.

If you would like the user to input the file gdb to be used, add that as a model parameter and make sure all your internal tools point to that variable so that all outputs will be written there.

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