To share an analysis result as a web tool, ensure that you have sufficient publishing permissions and that the versions of ArcGIS Pro and ArcGIS Enterprise are compatible. The role of a portal login account should be either Administrator or a custom role. If the role is custom, the minimum requirement is an existing default Publisher role with the Publish web tool option of the administrative privileges . To learn more about compatibility of ArcGIS Pro to ArcGIS Enterprise versions, see Web tool compatibility.
When sharing a web tool, you can either share as a new web tool or overwrite an existing web tool. Overwriting an existing web tool is only available from ArcGIS Pro 2.6. To share your web tool with either option, see Share your web tool. When either sharing as a new web tool or overwriting the existing tool, you need to set multiple properties to define how the users of the service interact with the web tool.
You can share a web tool to a federated server from ArcGIS Pro 1.4 and later using the Share as a web tool pane or Python. You can use ArcGIS Enterprise or Python to publish a geoprocessing service to a stand-alone server from ArcGIS Pro 2.3 or later. To learn more, see Publish web tools in a Python script.
One of the first steps before publishing is to analyze the web tool. The analyze process looks for issues that will prevent the tool from being published. Information on the data and tools that will make up the service and potential solutions will be offered. Some analyzer errors can only be resolved by modifying the tools or data that comprise your tool. Other messages and warnings provide guidance and best practices. After critical errors have been addressed and the settings of the service have been configured, the web tool can be published. To learn more, see Analyzer messages.
Add a tool
When sharing a web tool, the process starts with the result of a model or script tool. You can build a web tool using multiple results. Any successful geoprocessing history item can be included in a web tool to be published as a service. Adding multiple tools is a good technique when grouping similar tools or tools that are part of a workflow.
A new tool cannot be added to an existing web tool. You must republish the existing tool and the tool to be added into a new, single geoprocessing service (web tool).
By default, a web tool is only accessible by the account from which is was created. The web tool can be shared within the organization, to specific groups, or to everyone.
When sharing a web tool to a local portal, the hosting server is the default server for the underlying geoprocessing service. Web tools and the geoprocessing services that power them are expected to be fast and responsive. Sharing many web tools to a hosting server where many feature services are also running may incur a performance penalty due to the lack of system resources. If you have multiple servers available and they are federated into your portal, it may be advantageous to separate the geoprocessing services from the default hosting server to their own federated server. Without having multiple federated servers, geoprocessing services can be shared to the hosting server without a problem as long as good service and resource management by administrators and publishers is undertaken.