We ran into some problems in the afternoon that prevented us from working with our mobile applications. The internet is a double-edged sword…..
We made the best of our time and talked about ArcGIS Enterprise, editor tracking in AGOL v. Portal for ArcGIS, some new functionality coming in AGOL, and ArcGIS Pro.
The ArcGIS Server Help has some excellent documentation on ArcGIS Enterprise and the concept of a Base Deployment. One of the ideas I really stressed on was the concept of Federating your ArcGIS Server with Portal. The biggest ‘you must be aware of’ in my mind is that doing this shifts identity management from ArcGIS Server to Portal for ArcGIS. This is important to existing ArcGIS Server customers and how individuals and existing applications interact with ArcGIS Server. Take caution and plan carefully when implementing Portal for ArcGIS into a traditional ArcGIS Server environment.
Here’s a great link that helps you understand the three relationships between ArcGIS Server and Portal for ArcGIS.
When dealing with Editor tracking there is simple and not as simple. Simple involves enabling editor tracking on a hosted feature layer in ArcGIS Online or Portal for ArcGIS. The only difference between the two environments is where the data resides. In ArcGIS Online your data is stored behind the scenes in a Data Store that is managed by AGOL. With Portal for ArcGIS the data is on premises in a Data Store that you installed as part of your ArcGIS Enterprise Base Deployment. This deployment requires a Federated ArcGIS Server that is designated as a hosting server. The Data Store is registered with ArcGIS Server as a managed database.
The not as simple is when you have a layer that is sourced from an Enterprise Geodatabase. In this setup the feature class is published to Portal for ArcGIS (we’re all using ArcGIS Pro, right?) as a feature layer or as part of a web map. The underlying ArcGIS Server service can then be registered in ArcGIS Online as an item. Because the source of the feature layer is an Enterprise geodatabase the database needs to be configured manually to enable editor tracking. Manually means using Desktop to Enable Editor Tracking in the database. Additionally, the service in ArcGIS Server needs to have Feature Access in order to edit. ArcGIS Pro does make this a more streamlined process, but it can be accomplished through ArcMap as well.
As a group we discussed some of the new functionality coming to the March release of ArcGIS Online. One that I am particular excited about adds to an already awesome capability of creating a view against hosted feature layer. For anyone who has tried to edit hosted feature layers in ArcGIS Online and then share that content as read-only….this is for you! To accomplish the aforementioned, set up was no easy task, but now it is as simple as creating a view and assigning access to the view. The latest release gives users even greater granular control on the view, allowing field and row filtering. Very powerful stuff and I applaud it.
What I really wanted to demonstrate in ArcGIS Pro was the Deployment Tool. This Add-In allows users to quickly deploy a solution to ArcGIS Online or Portal for ArcGIS, configure the created hosted feature layers and load data into those hosted feature layers. This tool really streamlines the process of setting up one of the Esri solutions.
Here are some additional ArcGIS Pro resources that I use:
Other resources that I use: