Logical architecture

This logical view of the reference architecture defines individual software components, how they are separated or combined together, and key interactions between them.

Software components

This diagram contains a variety of software components that contribute to the overall system design, including:

• Applications providing end-users with access to system capabilities. The primary applications used in Network Management Systems are:
  • ArcGIS Pro, a professional GIS desktop application used by editors.
  • Configurable applications and application builders used by general users and editors.
• A base deployment of ArcGIS Enterprise, including the following components:
  • Portal for ArcGIS.
  • ArcGIS Server configured as a hosting server.
  • ArcGIS Data Store configured as a relational store for persisting ArcGIS-managed data.
• An additional ArcGIS Server site configured with the GIS Server role and used to deliver utility network editing services.
• An enterprise geodatabase for storing and managing an ArcGIS Utility Network through a supported relational database management system (DBMS).
• Load balancing and reverse proxy capabilities are provided by the ArcGIS Web Adaptor. Additional load balancing and reverse proxy components may be recommended or required for certain scenarios, including high availability deployments.
• An identity provider is recommended for single sign-on (SSO) within the enterprise, though not strictly required. Learn more about ArcGIS authentication models and providers.
• ArcGIS License Manager for configuring and managing ArcGIS Pro licenses used by desktop editors.
• ArcGIS Monitor for monitoring and optimizing the system components and overall health.
• ArcGIS Online provides basemaps and other location services.

Key interactions

The software components described above interact with each other in the following ways:

• Client applications communicate with enterprise data services over HTTPS, typically via stateless REST APIs. A friendly, well-defined domain name is recommended as the entrypoint to the system. Three separate ArcGIS Web Adaptor instances configured in the web server handle context path based routing to the Portal for ArcGIS and ArcGIS Server components described above. Learn more about DNS, naming, and URLs.
• Client applications communicate with basemaps and location services provided by ArcGIS Online over HTTPS, typically via stateless REST APIs. This requires connectivity from client machines to the internet.
• ArcGIS Server maintains persistent TCP connections to both the database management system (DBMS) hosting the enterprise geodatabase as well as the ArcGIS Data Store. The former requires that appropriate database client software be installed on the ArcGIS Server machines communicating with the DBMS.
• ArcGIS Pro communicates with the ArcGIS License Manager using TCP/IP protocols. Learn more about configuring ArcGIS License Manager with ArcGIS Enterprise Portal and configuring ArcGIS License Manager to work through a firewall.
• ArcGIS Monitor communicates with a variety of ArcGIS and IT (e.g., DBMS) components using a variety of mechanisms. See ArcGIS Monitor documentation for more information.
• References to location services hosted and managed by ArcGIS Online are typically registered and made available for use within ArcGIS Enterprise. 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.