Checklist for authoring and publishing geoprocessing services
Models and scripts
Description |
More information | ||
---|---|---|---|
|
Use supported input and output parameter data types, such as feature sets. |
||
|
Desired outputs of your service should be model parameters (a P appears next to the variable in ModelBuilder). |
In ModelBuilder, right-click the variable and click Model Parameter. |
|
|
Intermediate data is either:
|
||
|
Output data is written to:
|
||
|
Data used by your model (other than inputs from the user) must be accessible by the server. |
||
|
Your service should be fast and efficient. |
Tool layers
This checklist is for creating tool layers prior to publishing.
Description |
More information | ||
---|---|---|---|
|
Results are temporary by default option is unchecked. |
||
|
Before opening and running tool layers, set your scratch workspace environment. |
||
|
If you change any of the parameters of the corresponding model or script, you need to re-create the tool layer. |
||
|
Remove unnecessary layers from the map document. |
Result map services
This checklist is for tasks published with a result map service.
Description |
More information | ||
---|---|---|---|
|
All data to be drawn by the result map service must exist on disk. This means that layer data types, or data written to in_memory, are not allowed as output. |
||
|
If you only want the client to view the data and not be able to download data, set the Maximum Number of Records Returned by Server option to zero when publishing. |
||
|
Do not use your result map service as a basemap for your service. |
Symbolizing input and output data
Description |
More information | ||
---|---|---|---|
|
Only use symbology that the client can draw. (This does not apply if you are using a result map service.) |
||
|
If the output of your task is a layer data type variable, the symbology defined for the output variable will be used, not the symbology of the tool layer. (This does not apply for result map services.) |
||
|
If you are using a feature set as input, the client will be drawing features that the user digitizes. The symbology you use for these input features must be symbology that the client can draw. |
General publishing
Description |
More information | ||
---|---|---|---|
|
When publishing, set the Maximum Number of Records Returned by Server option to a number appropriate for your output data. |
||
|
For initial testing, check Show Messages. For final deployment, you may want to uncheck Show Messages. |
||
|
Choose a jobs directory that is appropriate for your service. |