--- title: "Reference Architecture for a Utility's Network Information Management System" description: Logical reference architecture for a Network Information Management System (ArcGIS Enterprise on Windows and Linux) source_url: "https://architecture.arcgis.com/en/architectures/network-management/deployment-patterns/windows-linux.html" md_url: "https://architecture.arcgis.com/en/architectures/network-management/deployment-patterns/windows-linux.md" --- # ArcGIS Enterprise on Windows and Linux (software) This logical view of the reference architecture supports all [implementation options](/en/architectures/network-management/implementation-options/implementation-options.md) of the network information management system and defines individual software components, how they are separated or combined, and key interactions between them. ![Logical reference architecture for a network information management system in ArcGIS Enterprise on Windows and Linux](https://architecture.arcgis.com/assets/images/architectures/logical-nims-architecture-w-l.png "Logical reference architecture for a network information management system in ArcGIS Enterprise on Windows and Linux") _Download a [Microsoft Visio file](/assets/diagrams/logical-nims-architecture-w-l.vsdx) of this logical architecture._ _Learn more about [diagramming resources](/en/framework/architecture-practices/diagramming-resources.md) for ArcGIS systems._ > [!NOTE] > **Note** > This reference architecture was designed with a focus on specific [workflows](/en/architectures/network-management/intended-workflows.md) and [capabilities](/en/architectures/network-management/introduction.md#capabilities). ## Software components The diagram above contains several software components that contribute to the overall system design, including: - Applications provide end-users with access to system capabilities. The primary applications used in a network information management system are: - [ArcGIS Pro](https://pro.arcgis.com/en/pro-app/latest/get-started/get-started.htm) - a professional GIS desktop application used by editors - Configurable applications and application builders used by general users and editors - An ArcGIS Enterprise [base deployment](https://enterprise.arcgis.com/en/get-started/latest/windows/base-arcgis-enterprise-deployment.htm), including the following components: - [Portal for ArcGIS](https://enterprise.arcgis.com/en/portal/) - [ArcGIS Server](https://enterprise.arcgis.com/en/server/) configured as a hosting server - [ArcGIS Data Store](https://enterprise.arcgis.com/en/portal/latest/administer/windows/what-is-arcgis-data-store.htm) configured as a relational store for hosting [ArcGIS-managed](/en/overview/introduction-to-arcgis/arcgis-architecture/data.md#storage-considerations) data - 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](https://enterprise.arcgis.com/en/server/latest/manage-data/windows/enterprise-geodatabases-and-arcgis-enterprise.htm) for storing and managing data within an ArcGIS Utility Network through a [supported relational database management system (DBMS)](https://enterprise.arcgis.com/en/server/latest/manage-data/windows/enterprise-geodatabases-and-arcgis-enterprise.htm). This is required for options 2 and 3. - Request routing and reverse proxy capabilities are provided by the [ArcGIS Web Adaptor](https://enterprise.arcgis.com/en/server/latest/install/windows/about-the-arcgis-web-adaptor.htm). Additional load balancing and reverse proxy components may be recommended or required for certain scenarios, including [high availability](https://architecture.arcgis.com/en/architectures/network-management/design-choices-and-considerations.html#reliability) 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](/en/framework/architecture-pillars/security/authentication-models-and-providers.md). - [ArcGIS License Manager](https://desktop.arcgis.com/en/license-manager/latest/welcome.htm) for configuring and managing ArcGIS Pro licenses used by desktop editors. > [!NOTE] > **Note** > 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](https://doc.arcgis.com/en/monitor/latest/get-started/windows/introduction-to-arcgis-monitor.htm) for monitoring and optimizing the system components and overall health. - [ArcGIS Online](https://www.esri.com/en-us/arcgis/products/arcgis-online/overview) 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 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](/en/framework/architecture-practices/deployment-concepts/dns-naming-and-urls.md). - 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](https://enterprise.arcgis.com/en/server/latest/manage-data/windows/database-clients.htm) 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](https://desktop.arcgis.com/en/license-manager/latest/introduction-to-license-manager-with-arcgis-enterprise-portal.htm) and [configuring ArcGIS License Manager to work through a firewall](https://desktop.arcgis.com/en/license-manager/latest/configure-the-arcgis-license-manager-to-work-through-a-firewall.htm). > [!NOTE] > **Note** > 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](https://doc.arcgis.com/en/monitor/latest/get-started/windows/introduction-to-arcgis-monitor.htm) 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](https://enterprise.arcgis.com/en/portal/latest/administer/windows/configure-arcgis-online-utility-services.htm), [configuring ArcGIS Living Atlas content](https://enterprise.arcgis.com/en/portal/latest/administer/windows/configure-living-atlas-content.htm), and [distributed collaboration](https://enterprise.arcgis.com/en/portal/latest/administer/windows/understand-collaborations.htm). 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. ## Related resources - Learn more about interactions between ArcGIS Enterprise components in the ArcGIS Enterprise on Windows and Linux [product documentation](https://enterprise.arcgis.com/en/), including a [diagram of ports](https://enterprise.arcgis.com/en/system-requirements/latest/windows/pdf/ports-enterprise-deploy-dgm.pdf) used in an ArcGIS Enterprise on Windows and Linux deployment. - Learn more about [data editing and management](/en/framework/system-patterns/data-editing-and-management/deployment-patterns/as-server-software.md) delivered through a Windows and Linux based deployment pattern.