Available with Production Mapping license.
The Topographic Production Service is deployed to ArcGIS Server when a map that contains feature data from ArcGIS Enterprise or a file geodatabase is published as a web layer. When publishing, you can configure operations in ArcGIS Pro to run on ArcGIS Server as described below. Once the service is available, you can configure settings for the self-serve Map Production System (MPS) web app that is included with the Enterprise product data files installer. The MPS web app can export map products.
The following actions are required before publishing the service:
- The Enterprise product files must be installed on each ArcGIS Server machine in an Enterprise deployment and correspond to the Enterprise release to which the service is published..
- The service stores temporary data for each job that is configured to run on ArcGIS Server. The default location for this data is C:\ProgramData\ESRI\TopographicProduction\jobs.
- The ArcGIS Server account must have read and write access to the jobs directory location and the location that contains digital elevation models (DEMs) that are used by the map.
- If the map products use DEMs, copy the DEMs or their mosaic datasets to each ArcGIS Server machine in your Enterprise deployment and use the productName and raster parameters in the updateProduct operation to specify the location of the DEMs. Ensure that all ArcGIS Server machines in a multimachine deployment and the ArcGIS Server account have read and write access to the location that contains the DEMs.
Output files that the service creates using the generateProduct operation are copied to the output directory of the map service.
Tip:
You can make the Cleanup Interval property available if you edit service properties in ArcGIS Server Manager; it is infrequently used and unavailable by default. This property specifies the number of hours before temporary data used to produce a map product and the output map products themselves are deleted from the server. If you make it available, the default interval is 24 hours.
Enable capabilities
Ensure that you're signed in to the ArcGIS organization that the service will deploy to with an account that is licensed for ArcGIS Defense Mapping or ArcGIS Production Mapping before you complete the following steps to enable the Topographic Production Service capability.
- In ArcGIS Pro, click the Share tab.
- In the Share As group, click the
Web Layer drop-down arrow, and click Publish Web Layer.
The Share As Web Layer pane appears.
- Provide a name for the web layer in the Name text box.
- Optionally, complete the Summary and Tags fields.
A summary and tags are required when sharing to an ArcGIS Enterprise 10.9 or earlier portal.
You can enter a maximum of 128 tags.
- In the Data and Layer Type section, do one of the following:
- Under Reference registered data, choose Map Image to reference datasets in a registered Enterprise database.
Note:
Check the Feature check box to share the web feature layer as a dependent layer to the map image layer.
- Under Copy all data, choose Map Image to copy all the layers to the hosting server's managed database.
- Under Reference registered data, choose Map Image to reference datasets in a registered Enterprise database.
- Under Location, use the Folder menu to choose a folder in your portal content in which to store the web layer. Optionally, create a folder.
By default, the web layer is stored at the root level of your portal content.
Tip:
Click the Browse button to browse to a folder in your portal content. You can also type a folder name in the text box.
- Use the Server and Folder drop-down menus to specify the federated server where the service will be published and the folder where it will be stored. Optionally, create a folder.
By default, the service is stored in the root folder of the server.
Note:
The Server and Folder options appear only if you are sharing to ArcGIS Enterprise using the Reference registered data option. In this case, you can also click the Data Stores button to open the Manage Registered Data Stores pane. Use this pane to register geodatabases and folders with federated servers.
- Under Sharing Level, specify how the web layer will be shared:
- Owner—Only the owner (and organization members with privileges to view content owned by other members) can access the item. This is the default option.
- Organization—Share your content with all authenticated users in your organization. This option is available when you are signed in with an organizational account.
- Everyone (public)—Share your content with the public. Anyone can access and see it.
- Optionally, under Groups, select groups to which you belong to share your content with their members.
- Click the Configuration tab.
- Ensure that the Configure Layers tab is active.
- In the Capabilities section, check the Topographic Production check box to enable the service.
Configure the service properties
To configure service operations and other service properties, complete the following steps:
- In the Capabilities section, for Topographic Production, click Configure Service Properties .
The TopographicProductionServer Properties pane appears.
- Optionally, check any of the check boxes in the Operations section to enable or disable the service operations.
Topographic Production Service operations are enabled by default. The following operations are supported:
products
Retrieves the map products that the Topographic Production Service supports
jobs
Enables the query, cancel, and delete operations, as well as the job resource
addProduct
Adds a map product definition that the service can use to generate a map
removeProduct
Removes a map product definition from the service
updateProduct
Updates an existing map product definition's properties
generateProduct
Automates the process of producing a layout or map based on a map product definition
- In the Properties section, specify the following properties:
- For tmserverDatabase, specify the path to an Enterprise spatial database engine (SDE) connection file.
This updates the location of the jobs directory, which is used to store temporary data for each job.
Your Enterprise organization must have read access to the location specified in the connection file and the database user must be able to perform data manipulation language (DML) statements in the database. All machines with multiple map services enabled must use the same .sde connection file.
Note:
If the server logs show an error such as -2147220893 Workspace or data source is read only when initializing the Topographic Production Server database, confirm that you are using an .sde connection file.
If ArcGIS Server is deployed as a single-machine site and you only have one map service enabled, leaving this blank automatically creates a file-based database at the following location after the service is published: C:\ProgramData\ESRI\TopographicProduction. This database cannot be used for multi-machine deployments or when working with more than one service.
Legacy:
Starting at the ArcGIS Enterprise 11.5 release, SQLite databases, or any other file-based databases, will not be supported. An SDE connection file configured to one of the following relational database management systems (RDBMS) will be required:
- PostgreSQL
- Oracle
- Microsoft SQL Server
- Specify the type of map products the service will support in the productType text box, such as CTM, JOG, MTM, and TM.
Map product definitions have a type property. When you specify a value in the productType text box, only the products that match this value are returned by the service. For example, if a single service contains the Multinational Geospatial Co-production Program (MGCP) data to produce MTM products, specify MTM as the product type. You can specify more than one product type by separating product type values with a comma.
Caution:
If you leave this text box blank, no products are returned.
- Specify how long in seconds the data extraction can run before timing out in the extractionTimeout text box.
The default is 900 seconds. If a data extraction time out error occurs when running the generateProduct operation, try increasing this value before running the operation again.
- Specify whether the service automatically updates existing map product definitions in the autoUpdateProducts text box.
The default is True.
- For tmserverDatabase, specify the path to an Enterprise spatial database engine (SDE) connection file.
- Optionally, click Configure Parameters to configure more properties.
- Click Configure Pooling .
- Ensure that the Dedicated instance option is chosen in the Instance Type group.
- Optionally, specify the range for the number of instances per machine in the Number of instances per machine section.
This is the minimum and maximum number of dedicated instances that can run for the service at any given time, including when the service is not in use. These are the instances that handle calls to the map service, as well as REST operations that don't consume many resources and are handled quickly.
Tip:
Adjust the range of instances as necessary after monitoring the network traffic to these endpoints. The generateProduct operation uses the TopographicProductionSystemTools geoprocessing service to perform the work. Adjusting the range of instances of this service impacts the throughput of generating map products.
- Optionally, click the Content tab to view the folder, new web layers, and sublayers with assigned IDs if available.
If you enabled the Allow assignment of unique numeric IDs for sharing web layers option on the Map Properties dialog box, assigned IDs appear for each sublayer. To change an ID, click the number next to the layer or table. On the Layer Properties or Standalone Table Properties dialog box, on the General tab, type a custom integer ID in the Layer ID or Table ID text box. For more information, see Assign layer IDs.
You're ready to analyze and publish the map as a service web layer.
Publish the service
Once you have configured all of the settings for the service, complete the following steps to analyze the configuration and publish it to your active Enterprise portal:
- Click Analyze to run a check for problems.
Errors and warnings are listed on the Messages tab. Right-click a message to open its help topic or take corrective action. Errors must be resolved before you can share the web layer. Resolving warnings is recommended but not required.
- After you have resolved errors and warnings, click Publish to share the web layer.
To save a service definition of the web layer to publish later, click the Publish drop-down arrow, and click Save As SD.
- When the web layer is finished publishing, click Manage the web layer at the bottom of the Share As Web Layer pane.
A browser page appears. Sign in to your portal to open the web layer's item page if necessary.
Once published, the service's operations are available in ArcGIS GIS Server from the ArcGIS REST API and in a configured, self-serve Map Production System (MPS) web app on the Enterprise portal with the ArcGIS Defense Mapping or ArcGIS Production Mapping server extension.