Deploying services on multiple computers - LocalJobsDirectory
Deploying services on multiple computers - LocalJobsDirectory
|
| Release 9.3 |
   |
The jobs directory is where the output of your service is written so that clients can retrieve your results. If your ArcGIS Server configuration has mulitple computers, the jobs directory must be a location accessible by all computers that host the service. This means that you will use a UNC path to this shared location. However, writing output across your LAN is slow compared to writing data to a local disk. To make for more efficient services, your server administrator can specify an optional property, <LocalJobsDirectory>, in the service configuration file.
NOTE: Using local job directories will significantly improve performance with SOCs on multiple machines.
Configuring a local jobs directory does not affect how you publish services—you still enter the UNC path to the shared directory when publishing your service. Behind the scenes, your service will write output to the local jobs directory. When your service has finished executing, ArcGIS Server moves the contents of the local jobs directory to the shared jobs directory so that clients can access the results. While the same amount of data is still being moved across the LAN, it is much more efficient for ArcGIS Server to move the contents of the entire local directory than it is for your service to write individual files piece by piece across the LAN.
It is up to your ArcGIS Server administrator to configure local job directories. Nothing changes for how you publish your service other than you specify a UNC path to the jobs directory.
Learn more about how configuration files work.
Learn how to configure a local jobs directory.
Learn more about UNC pathnames.
