We have created a GP Service via a published tool layer in ArcGIS Server 9.3.1. The MXD and model are attached. The output of the model is a polygon shapefile which is then exposed via resulting map service. The model seems to run correctly with no errors and the service has been consumed successfully from the ArcGIS Desktop application. The final output will be a mailing list generated from a FLEX Web App.
We have been unsuccessful in figuring out how to call the REST API from FLEX or the predefined HTML interfaces. One point of confusion is the scratchworkspace. This is defined in the application as the Scratch folder under the toolshare folder as directed, however it is not clear to me how this information is updated when the task is executed from the web client. The shapefile in the jobs folder is updated but since the sublayer in the MXD references the scratch folder under the toolshare folder how is the output ever exposed? The result is that there does not to appear to any link between the GP Service and the resulting map service. I think we are just missing something obvious but at this point have hit a wall. Any help is appreciated.
Chase Barnard
I have a similar question. The online example for creating a Buffered Point service describes creating Scratch.gdb, which is never used in the example. The instructions then go on to direct the output polygon to %scratchworkspace%\BufferedPoints.shp
When testing this it seems that the output data (as shapefiles) will never be overwritten. If the output is directed to Scratch.gdb, the model fails to run consecutively as a the output feature class already exists after the first execution of the model.
It would be helpful to understand the seeming inconsistency in the online documentation with regard to the scratch workspace.
http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=GP_Service_step-by-step%3A_Buffer_poin...
If the service is used by an online client, how do you manage output data for calls from multiple instances of the web application?