Split solutions between ArcGIS Online and ArcGIS Enterprise

Question

I am looking for ways to split ArcGIS Solutions between ArcGIS Online (AGO) and ArcGIS Enterprise (AGE). We are looking to deploy several emergency operations solutions and we want the staff side on AGE and the public side on AGO. Is it better to publish on AGO and use distributed collaboration to sync to AGE or the other way around?

We need the staff side to keep working even if the internet goes down, hence the AGE requirement.

LindsayThomas · Answer

@Joshua-Young You can use the approach outlined above. There are a few other ways to do this as well.

The syncing btw environments could also be accomplished in many ways using ArcGIS. Whatever works for you and your organization is best. For example, using ArcGIS Data Pipelines to sync the layer information between AGOL and AGE. ( This syncing could also be done via python scripting, using an ArcGIS Notebook, and a variety of other ETL\sync workflows.)

A tip for identifying the internal and external lineage of apps would be to use the ArcGIS Solution Diagram and help documentation to understand public facing maps, apps, and layers, as well as what is truly internal as well.

AGOL Assistant works well to "swizzle" layers and item ids and layers, especially when the schema's are the same.

One thing to consider when swapping layers, any layer that is using the Living Atlas should not be swapped because the id is the same for AGOL and AGE. For example, in Emergency Management Operations we have the USA structures from the living atlas and that id wouldn't need to be switched. This isn't always clear in the code.

Another tip to think about, look at the version of the solution item in AGOL and the version of Enterprise you are using. Matching solution item version means the included layers, maps, and apps are the same in the majority of cases. If the versions are out of sync then using the release notes at the bottom of the intro help topic will give you a better understanding of what could be different and identify any adjustments that will have to be accounted for.

joyoung_kerrvilletx · Answer

I am planning on deploying the following:

* Damage Assessment
* Emergency Debris Management
* Emergency Management Operations
* Emergency Shelter Management
* Special Event Operations

My current plan is to:

* Deploy all of them, except Damage Assessment, to both AGO and AGE
* On AGE create a distributed collaboration workspace to sync public facing views from AGE to AGO by copy
* Use AGO Assistant to swap the distributed collaboration layers on AGO in the public facing apps on AGO
* Then delete all of apps, maps, and layers from the solutions on AGO that are not public facing

I deployed the Damage Assessment last summer during our flood response and cloned the items to AGE. That created some issues that I had to use AGO Assistant to resolve. I think I am going to start over with a fresh deployment on AGO and do the following:

* Use distributed collaboration to create a two-way sync by copy between AGO and AGE for the layers
* Manually recreate the necessary maps and apps on AGE that staff need to use
* Delete the maps and apps that are not public facing from the solution on AGO

I was just curious if there is a better way of going about this.

LindsayThomas · Answer

Hi @Joshua-Young, which EM Solutions are you planning to deploy? That will help us get you the best answer.