The first five chapters of this book introduce the core set of decisions administrators should make before deciding how to best implement their ArcGIS Enterprise deployment. This section begins by reviewing prerequisites for the operating system, hardware, and security. It then introduces the ArcGIS Enterprise base deployment, which is made up of four components: Portal for ArcGIS, ArcGIS Server, ArcGIS Data Store, and two instances of ArcGIS Web Adaptor. Part 1 details important installation and security considerations for ArcGIS Enterprise and concludes with a section on extending the base deployment. Although each chapter in part 1 offers best practices, they are not in any way prescriptive; you may need to modify many of the steps introduced here to meet your organization’s needs. These chapters will help you understand what factors need to be considered to ensure the successful deployment and long life of ArcGIS Enterprise for your organization.
In this chapter, you’ll discover the meaning of various prerequisites that should be considered before designing and deploying ArcGIS Enterprise. We will consider how different OSs come into play with ArcGIS Enterprise, as well as what self-hosted options are available and what factors should be considered when choosing your base infrastructure.
ArcGIS Enterprise is a part of the ArcGIS geospatial platform. The ArcGIS geospatial platform frames all ArcGIS software offerings as part of a greater whole, created to meet a wide variety of needs across the GIS industry. In the scope of this book, you will see references to additional software, such as ArcGIS Online, ArcGIS Monitor, and other applications. These pieces of software exist to add additional functionality to your organization by working with ArcGIS Enterprise in a variety of architecture constraints.
As a note, this chapter goes over basic information and considerations before ArcGIS Enterprise is deployed. Being an enterprise-grade software, it has many permutations and advanced deployment options that may be implemented in system design. We will acknowledge and discuss the benefits of pursuing more advanced system design later in this chapter.
To someone just beginning to use ArcGIS Enterprise, let’s start by explaining what enterprise software is. At its core, any enterprise software seeks to be scalable to the needs of an organization. Unlike desktop-based software, enterprise software seeks to fulfill the needs of many concurrent users. Each implemented feature asserts how to best fulfill the needs of an ever-growing organization. ArcGIS Enterprise follows industry best practices to be a scalable and secure technology. Consider the six architectural pillars of enterprise software:
ArcGIS Enterprise aligns with these principles to fit a variety of user needs. At times, the number of options may seem overwhelming. When considering what type of deployment to pursue, it can be helpful to think of ArcGIS Enterprise as a system. To help illustrate what this system may look like, ask yourself the following questions:
The answers to these questions are the beginning of an ArcGIS Enterprise implementation that is not only technically viable but also considers the core needs of an organization. Identifying these requirements early in the system design stage of an ArcGIS Enterprise deployment will make choosing prerequisites such as OSs and underlying architecture providers easier.
). This resource was created to bridge the IT-GIS knowledge gap and addresses key knowledge on understanding how to configure and create a resilient deployment that meets various needs.Now that we’ve presented the basics of enterprise software, let’s bring it back to ArcGIS Enterprise. ArcGIS Enterprise supports many popular self-hosted options. ArcGIS Enterprise runs on infrastructure that you or a trusted vendor control. This gives you maximum flexibility when configuring your architecture. It also means that you have responsibility for configuring ArcGIS Enterprise to meet your organization’s needs. You can choose from several infrastructure options.
Some organizations want to deploy ArcGIS Enterprise on physical machines running in their own data centers. This option is the traditional model of server architecture, and many organizations have deep expertise in running their own physical infrastructure. It is a good option for organizations that need to keep their deployment disconnected from the internet. Building on this option, customers may also deploy ArcGIS Enterprise on virtualized environments that are disconnected from the internet.
The growing popularity of cloud-based resources and virtual machines has had a dramatic impact on the GIS software industry. Many organizations are taking a hybrid approach to their IT infrastructure. A 2023 poll from Zippia reported that 94 percent of organizations use some level of cloud services for their needs (). ArcGIS Enterprise was developed to support not only on-premises deployments such as traditional server architecture but also virtual machines and cloud offerings. This support can include running ArcGIS Enterprise on Linux and Microsoft Windows or a cloud native offering, such as ArcGIS Enterprise on Kubernetes®.
ArcGIS Enterprise also provides workload separation. Each major component of ArcGIS Enterprise can be placed on individual machines to separate the workload. We will discuss these components in chapter 2. More information on workload separation, as well as some strategies, can be found in the ArcGIS Architecture Center ().
So far, we’ve talked generally about how ArcGIS Enterprise works. For the rest of the chapter, we will cover specific prerequisites that contribute heavily to a functioning ArcGIS Enterprise deployment. Deciding on which OS to use requires a level of coordination with the rest of your organization. Although not the flashiest consideration, choosing the OS will have substantial downstream effects in the form of OS maintenance, updating the OS, and meeting organization-level standards.
ArcGIS Enterprise as a software set is built to accommodate the most popular OS being used for enterprise-level software. ArcGIS Enterprise supports Windows and a set of enterprise-level Linux options.
).The key takeaway is to remain flexible. It is common for newer implementations to change the hardware resources available for ArcGIS Enterprise once load figures become available. Additionally, ArcGIS Enterprise can be extended with different ArcGIS Server roles depending on customer and system needs. These can be configured once a base deployment is achieved as those needs arise. It is wise to set up resource monitoring for ArcGIS Enterprise to keep track of how well your deployment is functioning.
).ArcGIS Enterprise is designed to be deployed in a variety of network configurations. If legal obligations prevent data access outside of an internal network or other security requirements, ArcGIS Enterprise will function as a cohesive system without an external network connection in what’s called a disconnected environment. Alternatively, ArcGIS Enterprise can be deployed to be accessible from the internet through a security system and the use of a perimeter network.
A common implementation decision at this level is to adopt a hybrid system. This can be done in a variety of ways, but one of the most effective is to add arcgis.com domains to the allow list in the firewall. You might want to do this to take advantage of various functionalities in ArcGIS Online that are available for use in ArcGIS Enterprise. For example:
Each of these features has different requirements, which can be found in the documentation at .
Once ArcGIS Enterprise is deployed, ArcGIS Enterprise administrators need to work with their organization’s IT department to maintain the software environment. Active maintenance includes patching ArcGIS Enterprise and other necessary software, upgrading ArcGIS Enterprise, adding system resources when required, and creating backups of the environment. We will explore maintenance tasks in greater detail in part 4.
.In this chapter, we discussed ArcGIS Enterprise as an enterprise-grade system. Esri identified the pillars of enterprise system software: automation, integration, observability, performance and scalability, reliability, and security. Throughout the rest of the book, we will refer to these pillars to articulate how ArcGIS Enterprise fulfills them.