Once an ArcGIS Server site is upgraded to 11.0 or later, you must migrate, republish, or remove all services that use the ArcMap service runtime. ArcGIS Server no longer supports the ArcMap service runtime, and services that use the ArcMap service runtime are unusable. Only services using the ArcGIS Pro service runtime are supported, both for newly published services and existing services on an upgraded server site.
Learn more about migrating or republishing services
You can use the Edit Runtime operation in ArcGIS Server Manager to migrate eligible ArcMap services to the ArcGIS Pro service runtime. The Edit Runtime operation does not change the service's content or settings.
The Edit Runtime operation works on one service at a time. The following conditions apply:
- The service must have been published from ArcMap. (Services originally published from ArcGIS Pro cannot be migrated to the ArcMap service runtime.)
- The service must be using ArcGIS Server dedicated instances. All services migrated in ArcGIS Server Manager will continue to use ArcGIS Server dedicated instances after migration.
- If you migrate a map service, it cannot have the Schematics capability enabled.
- The service must not have any custom server object extensions (SOEs) or server object interceptors (SOIs) enabled.
- The source data for the service cannot be stored in IBM Db2 for z Operating System (z/OS) or IBM Informix.
After you use this operation to migrate a service's runtime, thoroughly test the service. If it's not working properly, you must republish the service from ArcGIS Pro.
Tip:
If you prefer to migrate multiple services in bulk, use the UpdateArcMapServices command line tool.
Migrate a service to the ArcGIS Pro service runtime
The following steps explain how to use the Edit Runtime operation in ArcGIS Server Manager to migrate a map, image, or geodata service to the ArcGIS Pro service runtime:
- Sign in to ArcGIS Server Manager as an administrator or the owner of the service to be migrated.
- Locate the service you want to migrate and click the Edit button
.If a service uses the ArcMap service runtime, a warning message appears that tells you to migrate the service.
The service runtime is also listed on the General tab when editing the service.
- Before you migrate a map service, click the Capabilities tab to identify what is enabled on it.
You can migrate services that have the following capabilities:
- WCS
- WFS
- Network Analysis
- KML
- WMS
- Feature Access
- If the map service has the Schematics capability, or if the service has any custom SOEs or SOIs enabled, uncheck the box next to each to disable them to make the service eligible for migration, and click Save and restart.
Note:
When you disable schematics, you can no longer use this service in schematics workflows. Similarly, disabling custom SOEs and SOIs means the custom functionality will no longer be available to users of the service until you migrate the SOE or SOI to the ArcGIS Enterprise SDK and add it back to the service. Ensure that no one is relying on these functions before you disable them.
If you made any changes to the service's settings during this session, you must save those changes before you migrate the service. All unsaved changes to service settings will be lost.
- When the service restarts, click the Edit Runtime button in the Service Runtime section of the General tab.
The Edit Runtime dialog box appears.
- Select the ArcGIS Pro option on the dialog box and click Apply to begin the migration operation.
If the service was running before you migrated it, the operation restarts the service when migration completes. The runtime displayed in the Service Runtime section now displays ArcGIS Pro. If the service was not running before you migrated it, you must start it.
- Ensure that the service functions properly in your applications. If you detect any functionality issues, republish the service from ArcGIS Pro.
If necessary, migrate custom SOEs or SOIs from ArcObjects SDK to ArcGIS Enterprise SDK and add them back to the ArcGIS Pro runtime service. See the Migrating ArcObjects SOEs and SOIs to ArcGIS Enterprise SDK blog post for more information.