Publishing a geodata service with a map service
If you want to use replication or data extraction commands from the Distributed Geodatabase toolbar in ArcMap with your geodata service, you can publish a map service with the same name. The service names must match, they must reside in the same folder on ArcGIS Server, and the layer names in your map document table of contents must exactly match the feature class names in your geodatabase. When you add the service to ArcMap, the commands will be accessible.
Legacy:
In 10.0 and earlier versions, you enabled the Geodata Access capability on a map service in order to pair a map service with a geodata service. In 10.1 and later versions, the Geodata Access capability has been removed and you must follow the steps in this topic if you want to access the Distributed Geodatabase toolbar using a geodata service.
Follow these steps to publish a geodata service with a map service:
- Publish a geodata service to ArcGIS Server. If you need help with this step, see Publishing a geodata service for full instructions.
- Prepare a map document containing datasets from the geodatabase from which your geodata service is derived. Make sure the layer names in the ArcMap table of contents match the dataset names in your geodatabase.
- Publish the map document as a service, choosing the same name and folder as your geodata service. For example, if your geodata service is named ROADS, your map service should also be named ROADS. Additionally, if your geodata service is in a folder on the server named TRANSPORTATION, your map service should also be placed in the TRANSPORTATION folder. See Publishing a map service for full instructions.
- With both services running, add your map service to the ArcMap table of contents and display the Distributed Geodatabase toolbar.
You can now use the toolbar to perform replication and data extraction with the geodata service.
Since the services are managed independently, you can configure each service to work well for different types of operations. For example, you might want to allow more instances and set longer time-outs to support replication operations with a geodata service. With the map service, however, you might want to keep shorter time-outs and limit the maximum number of instances to support operations such as viewing.