Azure

Virtual DTAP

The Virtual DTAP uses one ArcGIS Enterprise Base deployment. It is adviced to use multiple Enterprise geodatabases (on the same database server) and to use Folders on ArcGIS Server and Portal for ArcGIS to differentiate between the environments. Install the Azure Agent on the ArcGIS Enterprise Server together with the GaiaBuilder Python Toolboxes. Configure the jobs to use the Python installation that comes with ArcGIS Server

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated

DTAP

The DTAP uses multiple ArcGIS Enterprise Base deployments. Each deployment has it's own Enterprise geodatabases. The Azure Agent is configured on only one the ArcGIS Enterprise Servers together with the GaiaBuilder Python Toolboxes. The firewalls on all other ArcGIS Enterprise deployments and on all Enterprise geodatabases are configured to accept incoming connections from the ArcGIS Enterprise server containing GaiaBuilder. By using only one ArcGIS Enterprise Server as an Agent with GaiaBuilder, some resources are saved on the other servers and the configuration of GaiaBuilder and the Agent is less complex and time consuming. It is adviced to install the Agent and GaiaBuilder on Test or Development to save the resources for production and to keep Acceptance like Production. Configure the jobs to use the Python installation that comes with ArcGIS Server

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated. When a Development environment is added, GaiaBuilder and the Devops Agent can be installed on either Test or Development

Full DTAP

The Full DTAP uses multiple ArcGIS Enterprise Base deployments without a possible connection. Each deployment has it's own Enterprise geodatabases. The Azure Agent is configured on all the ArcGIS Enterprise Servers together with the GaiaBuilder Python Toolboxes. Although this configuration takes some extra resources for the Devops Agent and extra configuration for the Agent and the Python Toolboxes, it makes it possible to deploy to a DTAP with very strict Firewall configurations separating the DTAP ArcGIS Enterprise Environments. Configure the jobs to use the Python installation that comes with ArcGIS Server.

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated.

Multiple Servers

ArcGIS Enterprise components can be installed on different servers. In this case, the Devops Agent and GaiaBuilder should be installed and configured together with ArcGIS Server.

When there are multiple ArcGIS Servers federated with Portal, it is not necessary to install and configure Devops Agent and GaiaBuilder on all federated servers.

Jenkins

Virtual DTAP

The Virtual DTAP uses one ArcGIS Enterprise Base deployment. It is adviced to use multiple Enterprise geodatabases (on the same database server) and to use Folders on ArcGIS Server and Portal for ArcGIS to differentiate between the environments. Install ArcGIS Pro with a Single Use license or Floating license together with the GaiaBuilder Python Toolboxes on the Jenkins server. Configure the jobs to use the Python installation that comes with ArcGIS Pro

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated

DTAP

The DTAP uses multiple ArcGIS Enterprise Base deployments. Each deployment has it's own Enterprise geodatabases. Install ArcGIS Pro with a Single Use license or Floating license together with the GaiaBuilder Python Toolboxes on the Jenkins server. Configure the jobs to use the Python installation that comes with ArcGIS Pro. The firewalls on all other ArcGIS Enterprise deployments and on all Enterprise geodatabases are configured to accept incoming connections from the Jenkins server containing GaiaBuilder.

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated.

Virtual DTAP with Jenkins agent

The Virtual DTAP uses one ArcGIS Enterprise Base deployment. It is adviced to use multiple Enterprise geodatabases (on the same database server) and to use Folders on ArcGIS Server and Portal for ArcGIS to differentiate between the environments. Install ArcGIS Pro with a Single Use license or Floating license together with the GaiaBuilder Python Toolboxes on the Jenkins server. Configure the jobs to use the Python installation that comes with ArcGIS Pro

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated

DTAP with Jenkins agent

The DTAP uses multiple ArcGIS Enterprise Base deployments. Each deployment has it's own Enterprise geodatabases. The Jenkins Agent is configured on only one the ArcGIS Enterprise Servers together with the GaiaBuilder Python Toolboxes. The firewalls on all other ArcGIS Enterprise deployments and on all Enterprise geodatabases are configured to accept incoming connections from the ArcGIS Enterprise server containing GaiaBuilder and the firewall on the Agent Server to accept incoming connection from the Jenkins Server. By using only one ArcGIS Enterprise Server as an Agent with GaiaBuilder, some resources are saved on the other servers and the configuration of GaiaBuilder and the Agent is less complex and time consuming. It is adviced to install the Agent and GaiaBuilder on Test or Development to save the resources for production and to keep Acceptance like Production. Configure the jobs to use the Python installation that comes with ArcGIS Server

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated. When a Development environment is added, GaiaBuilder and the Jenkins Agent can be installed on either Test or Development

Full DTAP with Jenkins agent

The Full DTAP uses multiple ArcGIS Enterprise Base deployments without a possible connection between them. Each deployment has it's own Enterprise geodatabases. The Jenkins Agent is configured on all the ArcGIS Enterprise Servers together with the GaiaBuilder Python Toolboxes. Although this configuration takes some extra resources for the Jenkins Agent and extra configuration for the Agent and the Python Toolboxes, it makes it possible to deploy to a DTAP with very strict Firewall configurations separating the DTAP ArcGIS Enterprise Environments. Configure the jobs to use the Python installation that comes with ArcGIS Server.

This image shows only Test, Acceptance and Production from the DTAP to make the schema less complicated.