Self-service mapping, analysis, and sharing system (Windows/Linux)

The self-service mapping, analysis, and sharing 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, and 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 a self-service mapping, analysis, and sharing 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.

Self-service mapping, analysis, and sharing 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, 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. Please see the location services system pattern for more information.
  • There are a wide range of applications available through the self-service mapping, analysis, and sharing system. Those applications and types of applications commonly included in a base architecture deployment are shown in the diagram. For more information, see the full list of self-service, analysis, and sharing applications.

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 (e.g., DBMS) components using a variety of mechanisms. Please see ArcGIS Monitor documentation for more information.
  4. References to location services hosted and managed by ArcGIS Online (e.g., 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. Please see configuring ArcGIS Online utility services, configuring ArcGIS Living Atlas content, and distributed collaboration.

ArcGIS License Manager may be required for configuring and managing ArcGIS Pro licenses. See ArcGIS License Manager documentation for more information.

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


The capabilities of the self-service mapping, analysis, and sharing 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 a self-service mapping, analysis, and sharing 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 self-service mapping, analysis, and sharing 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.

  • Hosted Python notebooks enable Python-based analysis, administration, and automation using ArcGIS Notebooks hosted in 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.
  • Graph and link analysis models entities and relationships to find hidden patterns, important people, shortest paths, places, events, and other insights. Graph and link analysis is delivered in combination with spatial analytics through ArcGIS Knowledge.
  • Advanced exploratory analytics, provided by ArcGIS Insights, empowers analysts of all skill levels to directly connect data, perform advanced analytics, and take results into third-party systems. Learn more about ArcGIS Insights on-premises or in the cloud using ArcGIS Enterprise.
  • 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.
  • Indoor GIS extends ArcGIS Enterprise 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.
  • Production mapping optimizes data and map production using ArcGIS Production Mapping. ArcGIS Production Mapping is a specification-driven topographic mapping software for national civilian mapping agencies and authoritative content producers. This extension provides specialized tools to automate the production process from beginning to end through standardization, repeatability, and configuration. Production mapping is a broad capability that involves data editing and management as well as imagery data management. The subset of this capability provided by self-service mapping, analysis, and sharing systems includes high-quality, advanced cartographic production as well as general use of the maps and data produced.
  • Market intelligence, powered by ArcGIS Business Analyst, enables people to make smarter decisions for market planning, site selection, and customer segmentation by combining demographic, business, lifestyle, spending, and census data with map-based analytics. Learn more about ArcGIS Business Analyst Enterprise.
  • Project delivery and coordination enables architecture, engineering, construction (AEC) and operations teams to easily work with linked data and documentation in configurable web apps to simplify communication and collaboration. Learn more about this capability powered by ArcGIS GeoBIM and ArcGIS Enterprise.
  • 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 self-service mapping, analysis, and sharing 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 reasonably common, though it’s less common for self-service mapping, analysis, and sharing systems to be considered mission critical. For mission critical delivery of applications with strict SLAs and high levels of availability consider the enterprise application hosting and management system pattern.
    • High availability and fault tolerance is achieved through redundant infrastructure at all system tiers.
    • Geographic redundancy is less common, but possible.
    • 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 is required for almost all uses of a self-service mapping, analysis, and sharing system. One notable exception is the use of maps and apps shared without a login requirement for anonymous users.
    • Due to the wide range of users logging in from across the organization, this system pattern almost always leverage 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.

  • SLAs requiring high performance are less common with this system pattern than with others, such as enterprise application hosting and management systems.
    • Data read performance is typically a major factor in overall system performance.
  • Scalability is an important design consideration, as self-service mapping, analysis, and sharing systems are typically used heavily within an organization. Additionally usage may increase quickly and unexpectedly as the overall adoption of GIS grows across an organization.
  • Scaling may be performed automatically in response to demand certain cloud environments.
  • For applications and services requiring high-levels of performance and scalability, consider delivering them through an enterprise application hosting and management system.


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 self-service mapping and analysis workflows is common. Integration approaches tend to focus on data or services-level integration, sometimes involving automation. Learn more about integration approaches and methods.
  • Sharing of maps and other content from this system with other systems across the enterprise is common. Learn more about integration approaches and methods.
  • Self-service mapping, analysis, and sharing systems are commonly integrated with other ArcGIS systems. Learn more about related system patterns.
  • Organizations may deploy and connect more than one of these systems together, often to establish boundaries when engaging different groups of stakeholders, for example, across multiple departments or for internal and external use.


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

  • Observability is especially important with this system pattern. The flexible, self-service use of this system benefits greatly from governance, which is best implemented through awareness of evolving usage patterns and practices learned through observation. Organizations getting started with this system pattern are strongly encouraged to introduce governance and change management policies early. Additionally, ongoing review and housekeeping of content, groups, and users is strongly recommended, and can be enabled in large part through automation.
  • ArcGIS Enterprise on Windows/Linux can be observed in a variety of ways including server logs and server statistics. Monitoring of system availability, performance, and usage is important to this system pattern, as patterns of use may grow and evolve organically. 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.
  • Web analytics can be used with 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 a self-service mapping, analysis, and sharing system on Windows and Linux include:

  • Organizations getting started with this pattern are strongly encouraged to introduce governance and change management policies early.
  • Organizations should review and consider organization-level business and IT guidance around security and data sharing and implement data and application-level security protocols within the system as appropriate.

Related resources: