This logical view of the reference architecture supports all implementation options of the network information management system and defines individual software components, how they are separated or combined, and key interactions between them.
Download a Microsoft Visio file of this logical architecture.
Learn more about diagramming resources for ArcGIS systems.
This reference architecture was designed with a focus on specific workflows and capabilities.
The diagram above contains several software components that contribute to the overall system design, including:
An additional ArcGIS Server site configured with the GIS Server role and used to deliver utility network editing services. This is required for implementation options 2 and 3.
An enterprise geodatabase for storing and managing data within an ArcGIS Utility Network through a supported relational database management system (DBMS). This is required for options 2 and 3.
Request routing 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.
This component is no longer required for ArcGIS Enterprise 11.4 and later deployments and is not required for the next network information management system release.
ArcGIS Monitor for monitoring and optimizing the system components and overall health.
ArcGIS Online provides basemaps and other location services.
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 entry point 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 and configuring ArcGIS License Manager to work through a firewall.
This component is no longer required for ArcGIS Enterprise 11.4 and later deployments
ArcGIS Monitor communicates with a variety of ArcGIS and IT (e.g., DBMS) components using a variety of mechanisms. See ArcGIS Monitor 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 deployment.