deploying ESRI solutions on Enterprise GDB

[dsinha]

Hello everyone,

I have deployed couple of solutions (Citizen Problem Reporter, Lead Service Line) on our Enterprise Portal. Since both contain private information and could potentially contain voluminous data, I was wondering if it was possible to deploy these solutions (and others) on our on-site Enterprise GDB. I have scoured the web looking for an answer and have not found anything. Which possibly means that its not possible?

Thanks for your help! 

[ChrisFox · Accepted solution]

Hi @dsinha, It is not possible to deploy feature layers included with solutions to your Enterprise GDB. We are only able to create hosted feature layers in both Online and Enterprise when deploying an ArcGIS Solution.

[bsanders69]

Is there some documentation or best practice to "easily" migrate Hosted data to a RDBMS where we have more control over the data and storage thereof?

[AyanPalit]

@bsanders69 You have valid reasons to deploy solutions on-premise. Many organizations do so, even though the solution is designed to work with ArcGIS Online. This may involve deconstructing the solution and re-configuring per your organizational architecture.

You will find the following blog useful:

https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/a-guide-to-migrating-data-from-... 

[Joshua-Young]

@bsanders69 migrating the data to a RDBMS is not very difficult and @AyanPalit provides a great resource on how to do it. The more time-consuming part is then utilizing that RDBMS data in a solution. It is possible but you have to be very comfortable using ArcGIS Online Assistant to swap all the references in the solution apps, maps, and forms to your RDBMS based services.

Things to keep in mind are:

1. You will have to publish your own "views" of the source data using ArcGIS Pro. Make sure those services have the exact same fields available and editing permissions to match their hosted counterparts.
2. Save a copy of the original JSON of an item (app, map, etc.) before making any changes in ArcGIS Online Assistant. If something breaks you can always add back the original.
3. Experience Builder and sites/hubs are a bit tricky to update through ArcGIS Online Assistant because of their draft functionality. I think in both situations updating the JSON there only updates the published version.
4. Depending on your RDBMS, you may have to change field names in the JSON. For example, the hosted feature service may have "OBJECTID" but your RDBMS created the field as "objectid". You just need to verify that the casing is the same or change it in the JSON where needed.
5. If you create attribute rules make sure there is not a form expression accomplishing the same thing. For example, check the editing map in Map Viewer for a form expression to calculate an asset ID before creating an attribute rule that does the same thing.

[dsinha]

Hi @ChrisFox , thanks for your reply. I have a follow-up question: Are there any qualitative difference between deploying the solution on Enterprise vs. AGO?

Thanks!

[ChrisFox]

@dsinha, you will find that we have less solutions available in Enterprise vs AGO which is often due to capabilities that are missing or not yet available in Enterprise. However, for solutions that are available in both Enterprise and AGO there is really no different in the capabilities they offer.

I would just consider for some of your solutions intended for the public like Citizen Problem Reporter that by hosting in your own Enterprise it needs to be publicly accessible and down time will impact the user experience for your residents.