Enterprise application hosting and management system (Windows/Linux)

The enterprise application hosting and management system pattern is typically deployed to Windows and Linux using the ArcGIS Enterprise for Windows and Linux software.

ArcGIS Enterprise for Windows and Linux includes several components that span the data, services/logic, and presentation tiers. These components work together to provide a complete system. ArcGIS Enterprise for Windows and Linux is fully supported on virtual environments (running a support operating system), as well as cloud providers running virtual machines that meet the system requirements. Esri also provides deployment tooling for cloud platforms including Amazon Web Services (AWS) and Microsoft Azure.

Related resources:

Base architecture

The following is a typical base architecture for an enterprise application hosting and management system deployed on Windows or Linux.

This diagram should not be taken as is and used as the design for your system. There are many important factors and design choices that should be considered when designing your system. Review the using system patterns topic for more information. Additionally, the diagram depicted below delivers only the base capabilities of the system; additional system components may be required when delivering extended capabilities.

Enterprise application hosting and management system base architecture (Windows/Linux)

Key components of this architecture include:

  • A base deployment of ArcGIS Enterprise, including the ArcGIS Data Store, ArcGIS Server, and Portal for ArcGIS. The ArcGIS Web Adaptor component of ArcGIS Enterprise is also recommended and may be required in some situations. The base deployment enables data publishing and hosting through hosted feature, vector tile, map tile, and scene services. Many of these services in turn use the ArcGIS Data Store which provides ArcGIS-managed storage capabilities for hosted services.
  • ArcGIS Server, specifically the GIS Server role, which delivers feature and map services for data stored in registered, user-managed data stores. The ArcGIS Server providing enterprise data services is depicted as a logically distinct component of this system from the ArcGIS Server that provides hosted and utility services (and that completes the base deployment described above). This is because they play two different roles in the system and are often designed and deployed separately at a physical level. The ArcGIS Web Adaptor component of ArcGIS Enterprise is also recommended and may be required in some situations.
  • The data powering enterprise services typically comes from registered, user-managed data stores that include file and object stores, databases (DBMS), and cloud data warehouses. Learn more about the ArcGIS data architecture.
  • ArcGIS Online, Esri’s SaaS infrastructure, which typically provides basemaps (e.g., satellite map), reference data (e.g., places), as well as other location services (e.g., geocoding and search) for this system. Alternatively, it is possible for the organization to host and manage their own location services instead of using Esri’s SaaS system. See the location services system pattern for more information.
  • A wide range of web, mobile, and desktop applications designed to support a variety of user personas and workflows. Learn more about the applications used in an enterprise application hosting and management system.

Key interactions in this architecture include:

  1. Client applications communicate with enterprise data services as well as location services over HTTPS, typically via stateless REST APIs.
  2. ArcGIS Server maintains persistent TCP connections to both the ArcGIS Data Store as well as databases. The latter typically requires that appropriate database client software be installed on the ArcGIS Server machines communicating with the DBMS. Data supporting location services may also be stored in cloud data warehouses or file stores. Learn more about data and ArcGIS Server.
  3. ArcGIS Monitor, recommended for monitoring and optimizing the GIS system components, communicates with a variety of ArcGIS and IT (such as DBMS) components using a variety of mechanisms. See ArcGIS Monitor documentation for more information.
  4. References to location services hosted and managed by ArcGIS Online, such as basemaps, are typically registered and made available for use within ArcGIS Enterprise. Some services are referenced automatically when installing ArcGIS Enterprise, though additional sharing of content and services between these two systems can be performed manually or automatically. See configuring ArcGIS Online utility services, configuring ArcGIS Living Atlas content, and distributed collaboration.

Additional information on interactions between ArcGIS Enterprise components can be found in the ArcGIS Enterprise on Windows and Linux product documentation, including a diagram of ports used in an ArcGIS Enterprise on Windows and Linux deployment.


The capabilities of the enterprise application hosting and management system on Windows and Linux are described below. See the capability overview and comparison of capability support across deployment patterns for more information.

Capabilities used in an enterprise application hosting and management system, but typically provided by other systems, such as basemaps, geocoding, and other location services provided by a location services system are not listed below. Learn more about related system patterns.

Base capabilities

Base capabilities represent the most common capabilities delivered by enterprise application hosting and management systems and that are enabled by the base architecture presented above.

Extended capabilities

Extended capabilities are typically added to meet specific needs or support industry specific data models and solutions, and may require additional software components or architectural considerations.

  • Data interoperability and transformation capabilities support data movement among hundreds of systems and apps using the visual programming interface provided by ArcGIS Data Interoperability, which includes reading and writing to many data stores supported by ArcGIS Enterprise.
  • Workflow management and automation extends self-service mapping, analysis, and sharing workflows with the ability to orchestrate and automate work across teams using ArcGIS Workflow Manager.
  • Indoor GIS extends the capabilities of ArcGIS Online with ability to create and manage floor plan data, map building interiors, and share floor-aware maps and services. This capability requires ArcGIS Pro, and is made possible by ArcGIS Indoors. Indoor GIS commonly serves indoor maps and applications to broad groups of stakeholders including, but not limited to, enterprise and public audiences through lightweight mobile apps or kiosks. As such, portions of an indoor GIS may be best delivered through an enterprise application hosting and management system.
  • Mission management brings a geographic approach to command and control. Powered by ArcGIS Mission, mission management helps streamline mission operations and inform decision-making by fusing a real-time data with other operational and asset data sources.
  • Other industry solutions allow for rapid deployment of industry-specific apps and configurations of ArcGIS Enterprise using ArcGIS Solutions. Note, not all industry solutions are available for ArcGIS Enterprise.


The considerations below apply the pillars of the ArcGIS Well-Architected Framework to the enterprise application hosting and management system pattern on Windows and Linux. The information presented here is not meant to be exhaustive, but rather highlights key considerations for designing and/or implementing this specific combination of system and deployment pattern. Learn more about the architecture pillars of the ArcGIS Well-Architected Framework.


Reliability ensures your system provides the level of service required by the business, as well as your customers and stakeholders. For more information, see the reliability pillar overview.

  • SLAs requiring high levels of availability are common.
    • High availability and fault tolerance is achieved through redundant infrastructure at all system tiers.
    • Disaster recovery is possible, and commonly implemented with this system pattern.
    • Learn more about minimizing data loss and downtime in ArcGIS Enterprise.
  • Backup processes and procedures are common.


Security protects your systems and information. For more information, see the security pillar overview.

  • Authentication and authorization are typically required. One notable exception is publicly shared apps and supporting content, which do not require authentication.
    • Due to the wide range of users logging in from across the organization, this system pattern almost always leverages a single sign-on (SSO) approach to authentication. SSO is typically implemented using SAML and/or OpenID Connect.
    • User access and data collaboration are governed by role-based access controls and modern authorization and authentication models, including OAuth, SAML, OpenID Connect, and multifactor authentication.

Explore the ArcGIS Enterprise Hardening Guide to learn about strategies and associated settings that can be implemented to improve the security posture of ArcGIS Enterprise deployments.

Performance & Scalability

Performance and scalability aim to optimize the overall experience users have with the system, as well as ensure the system scales to meet evolving workload demands. For more information, see the performance and scalability pillar overview.

  • Performance and scalability is typically important or critical for enterprise applications that are hosted and managed in this system. Applications, along with supporting content like maps and layers, should be designed and engineered to meet the performance and scalability expectations of users and the organization (including SLAs if required). Learn more about optimizing apps and services in ArcGIS.
    • Data read performance is typically a major factor in overall system performance.
    • Content distribution networks (CDNs) may be considered for improving performance of tiled services for a large, geographically distributed userbase.
  • Scalability is an important design consideration, especially when applications are delivered to organization-wide or public-facing audiences.
  • Scaling may be performed automatically in response to demand certain cloud environments.


Automation aims to reduce effort spent on manual deployment and operational tasks, leading to increased operational efficiency as well as reduction in human introduced system anomalies. For more information, see the automation pillar overview.


Integration connects this system with other systems for delivering enterprise services and amplifying organizational productivity. For more information, see the integration pillar overview.

  • Incorporation of external data and services into this system for use by enterprise applications is common. Integration approaches tend to focus on data or services-level integration, sometimes involving automation. Learn more about integration approaches and methods.
  • Enterprise application hosting and management systems are commonly used to deliver data, analytic results, or other content produced or managed in another ArcGIS system. Learn more about related system patterns.


Observability provides visibility into the system, enabling operations staff and other technical roles to keep the system running in a healthy, steady state. For more information see the observability pillar overview.

  • Careful monitoring of service and application utilization is important with this system pattern. The delivery of enterprise applications typically extends to the whole organization (and possibly beyond), and therefore usage patterns and growth may not be anticipated by the system designers or operators. Monitoring helps people make decisions about when to scale and evolve to meet demand while continuing to operate properly (and in accordance with SLAs).
  • ArcGIS Enterprise on Windows/Linux can be observed in a variety of ways including server logs and server statistics. Monitoring of app and service availability, performance, and usage is most critical to this system pattern. In addition to monitoring the ArcGIS Enterprise software, it is important to monitor all supporting components and infrastructure such as the Windows or Linux operating system, databases and other data stores, as well as compute, network, security, and other infrastructure. Learn more about monitoring system health and reliability.
  • Some extended capabilities of this system pattern, such as workflow management and automation with ArcGIS Workflow Manager, have additional observability support. Please review the corresponding product documentation for more information.
  • Use of web analytics should be strongly considered when using ArcGIS Instant Apps, ArcGIS StoryMaps, and custom applications.
  • Additional observation of user logins and account changes may be possible through the configured identity provider when using SAML and/or OpenID Connect logins.


Additional considerations for designing and implementing an enterprise application hosting and management system on Windows and Linux include:

  • This pattern is typically designed to meet strict non-functional requirements and/or SLAs. As such, strong governance and alignment with IT policies and roles, such as data steward and content manager, should strongly be considered when implementing this system pattern.

Related resources: