Select to view content in your preferred language

Using a task scheduler for geoprocessing within a production server environment

4218
11
10-29-2013 09:40 AM
BenjaminBauman
Deactivated User
Hi there,

We have a model that is being used for weekly processing. A Python script checks to see if a file exists within an assigned directory, and then triggers the model process. This is accomplished without intervention, through the use of the Windows 7 Task Scheduler. We are now in need of migrating this weekly process to our production server. This server does not contain ArcGIS for Desktop, only ArcGIS for Server. How can we maintain our hands-off weekly processing given this limitation? Would it be be possible to export the model into a Python script, convert it to an executable and then assign that to Windows Task Scheduler without the existence of ArcGIS for Desktop? Or is there an ArcGIS for Server feature for scheduling a geoprocessing service (assuming we publish the model)? It seems to me as if published services are more for distributed use, and given that we only need to use this internally, it is not entirely appropriate.
We have no access to our production server yet, so I am still unclear as to what we can and cannot do. Any advice would be greatly appreciated.
Tags (2)
0 Kudos
11 Replies
BenjaminBauman
Deactivated User
Hi Kevin, I have a follow-up question. Our testing environment has both ArcGIS for Desktop and ArcGIS for Server. Before we migrate the process to the production server, we want to know how to invoke ArcGIS for Server with our batch file. We call our Python "master" script with a batch file containing the following line:

D:\Python27\ArcGIS10.1\python.exe Z:\WDIA_Production\extra_py\master_script.py

If we want to use the ArcPy contained within ArcGIS for Server, is it just a matter of changing the path of the Python executable to the one contained within the ArcGIS for Server directory? If so, what is the directory? D:\Python27\ArcGISx6410.1\python.exe?
0 Kudos
MichaelVolz
Esteemed Contributor
Benjamin:

You need to be careful with the 64 bit version of python (ArcGISx6410.1\python.exe) as it does not work on personal geodatabases (not supported in a 64 bit environment).  Maybe this does not apply, but this could explain issues if you are using a personal geodatabase.
0 Kudos