Many organizations use a layer! model for distributing content in ArcGIS Enterprise. This means that information is first creat! in development and test! in staging before being built in a production environment. This layer! method helps provide a layer of quality assurance and approval before the content is releas! to a wider audience in production.
Some organizations use a single ArcGIS Enterprise environment. They use separate groups for development, staging, and production. Groups often have different sharing settings and members, depending on who ne!s access and the tier the group represents.
However some organizations use multiple ArcGIS Enterprise
environments to separate these different layers. For organizations with separate environments, moving and managing content between environments can be challenging. That’s the scenario we’ll focus on in this blog, which covers new processes that make it easier to move layers, maps, and applications between environments.
We will focus specifically on the export group content they have several missions and import group content operations available in the ArcGIS REST API in ArcGIS Enterprise 10.8.1.
Let’s consider an example scenario where you are developing a Web AppBuilder application that includes a web map and feature layers. To build our scenario using the new operations we specifi!, you would follow these steps:
Step 1: Develop the group content as a package
Step 2: Add the package as an item (staging)
Step 3: Transfer the package content to a group (staging)
In diagrammatic form, the workflow looks like this:
We will use this scenario in the workflow the downside of job huntingtania g linares section of this blog. But first, let’s look at the prerequisites ne!! to achieve this.
Prerequisites:
Each environment must contain a base ao lists installation of ArcGIS Enterprise.
The minimum ArcGIS Enterprise version for each environment must be 10.8.1.
Administrator access to the ArcGIS Portal directory
A group containing all the items you want to export
A group creat! in the environment where the content will be transferr!
Additionally, before you begin, it is recommend! that your developers and administrators review the helpful group content export and group content import topics for additional information, including a list of currently support! items .
