Using ArcCatalog or the Catalog window in ArcMap, you can overwrite an existing service to reflect changes to a GIS resource or its source data.
A service overwrite is necessary in the following scenarios:
- If you update settings in the map document or other GIS resource underlying your service
- If your source data (such as a feature class displayed in your map document) was automatically copied to the server at publish time and you subsequently make changes to the source data that you want to see reflected on the server
Before proceeding with an overwrite, make sure the GIS resource you are using to overwrite the existing service is configured exactly the way you want it. All layers, tables, data references, and service properties in the original service are replaced as part of the overwrite.
- Follow the directions in the table below based on what service type you want to overwrite:
If the service you want to overwrite is a map service…
…open the ArcMap document you want to overwrite the service with and choose File > Share As > Service from the main menu.
If the service you want to overwrite is a geoprocessing service…
…browse to a successful result of the model or tool you want to overwrite the service with in the Results window, right-click it, and choose Share As > Geoprocessing Service.
If the service you want to overwrite is something else, such as a geodata or geocode service…
…browse to the item you want to overwrite the service with in ArcCatalog or the Catalog window, right-click it, and choose Share As Service.
- In the Share as Service window, choose Overwrite an existing service and click Next.
- Choose the ArcGIS Server connection you want to use from the Choose a connection drop-down list. If the server connection you want to use is not listed, you can create a new one by clicking Connect to ArcGIS Server . If you need help with this step, see Connect to ArcGIS Server from ArcGIS Desktop.
- From the table list, choose the service you want to overwrite and click Next.
- If your service has a map cache, click the Caching of the Service Editor to decide if you want to modify the cache automatically or manually:
- If you select Update cache automatically, all existing tiles are disassociated from your service and become associated with an additional automatically generated service named <service>_<timestamp>. The update will then begin creating new tiles in a cache for the original service. This workflow is sufficient for most deployments. If you are concerned about clients experiencing downtime, you can enable on-demand caching on the Advanced Settings tab.
- If you select Update cache manually, all existing tiles are disassociated from your service and become associated with an additional automatically generated service named <service>_<timestamp>. This service exists so that you can delete the old cache at a time that is convenient for you, since deleting a cache can be a time-consuming process. You'll need to run the caching tools yourself if you want to update the cache.
- In the Service Editor, set the properties that you want for your service. For details on how to set service properties, locate your service in the Types of services section of the help. For information on how to best configure your services for deployment, see Tune and configure services.
To give yourself more viewing area when configuring your service, click the Collapse button at the top of the Service Editor.
- Click Analyze . This examines your current configuration to see if the existing service can be overwritten.
- Fix any errors () in the Prepare window; this must be done before you can overwrite your existing service. Optionally, you can fix the warnings and informational messages to further improve the performance and appearance of your service. For more information about resolving these issues, see Analyze your GIS resource.
- Once you've fixed the errors and, optionally, any warnings and messages, click Publish .
If you will be copying data to the server as part of the overwrite, the size of the data and your network bandwidth will affect the time it takes to publish.
Your existing service is overwritten with your new service.