I heard that ArcGIS Pro cannot publish map or feature services to ArcGIS Server. It would be great if it could just like ArcGIS Desktop.
I'm using Pro v 1.3.1 & in all my testing, it certainly cannot publish to ArcGIS Server. I would really like to see this be an option.
I'm so happy I'm not the only one who feels this way! I think ArcMap can publish content to ArcGIS online, why couldn't ArcGIS Pro publish content to ArcGIS Server?
ArcGIS Pro does a great job of publishing hosted layers to AGOL, but there is no support for publishing to server. Having to go back and forth between ArcMap and Pro depending on where you are publishing is going to get old fast. Server is not going away anytime soon, so Pro has to catch up to support this very common workflow.
Is anyone else having ArcGIS Server 10.5 drawing errors with same feature class name in multiple schemas?
I definitely support this idea, I would love to hear from Esri on whether or not this will ever be available.
Please correct me if I'm wrong on these notes. ArcGIS Pro currently only supports publishing to Portal. This means:
1. You need to federate your portal with ArcGIS Server.
2. ArcGIS server must use portal's authentication (named users) instead of its built in user store
3. An organization must purchase a named user license for every user to access to authenticated resources
Portal might not work for every organization (especially small ones) because:
1. The additional overhead of setting up and maintaining the portal software is not preferred. In my experience, many issues can arise when configuring the portal/ags/web adapters and can be quite time consuming. We need something that is easy to configure, and ArcGIS Server is just that. Portal adds another layer of complexity that some organizations just don't need.
2. Named user licenses are cost prohibitive for small organizations, instead of paying for a server license, your paying for a server license plus a license for every user needing to access authenticated resources.
3. Named user licenses are not as flexible as ArcGIS server's user store. For instance, new users can be created on the fly using Server in minutes, but adding a new user to a portal may require additional purchases.
As others have mentioned, ArcMap supports publishing directly to Server, but from what the word is, ArcMap is eventually being phased out. This means organizations must either step up to the named user scheme, or continue using ArcMap despite lack of support.
This is an absolute requirement before we can even think about moving to Pro.
We develop SOIs and SOEs. We need the ability to publish traditional mapping services directly to the Server so that we can enable SOIs and SOEs on them. Publishing to the Portal means you end up with a hosted service instead of a traditional service and you can't enable an SOI or SOE on a Hosted Service.
I agree with others. I have been using Pro almost exclusively for several weeks, and this lack of functionality is holding us back from full adoption. I'm in a two-man shop, and we have no use for Portal. Additionally, we also have no interest in hosting our huge datasets on AGO. This might not be a feature needed by the majority of end users, but it is essential for anyone managing enterprise data.
Add me to the list, Pro has been great for multiple layouts and maps but the inability to publish to server has us standing still on further adoption. ArcMap it is until we can get the server publishing going in Pro!
Hi Joe Plattner
I'd like to assume that ESRI won't abandon this functionality. But they have been awfully quiet about it.
Check out this comment to the latest Pro roadmap. Unfortunately there is no answer:
This string is also worth reading: https://geonet.esri.com/thread/117751#comment-578726
Retrieving data ...