Separate Publishing Environment For Portal

RPGIS

Hi,

Currently, the workflow for publishing services requires using ArcGIS Pro, which limits the process to the machine where the service was originally published. This dependency creates a significant drawback: requiring the installation of the entire ArcGIS Pro application on each machine designated for publishing services. Additionally, configuring symbology, labels, and other elements must be done on the same machine.

To address these limitations, I propose creating a publishing app or service configurator hosted on the portal server. This solution would allow services to reside on the server and enable the creation and configuration of symbology, labels, filters, and other settings through registered database connections. This approach would save considerable time and reduce the complexity of managing multiple services across different machines.

RPGIS

Hi @JustinMallinckrodt,

 

It isn't an issue with publishing from the server manager or using a script; rather it has to do with having to have an arcgis pro project, symbolizing the layer in the map, and then publishing to the server.

Rather than using pro as a means of designing the service, there could be a portal/web application that already accessed a database and the layer(s) could be designed and ran from that application. Or, if possible, add an extension to server manager to symbolize the layer and set as a service.