---
title: Reference Architecture for a Land Information Management System
description: Land Information Management System reference architecture introduction
source_url: "https://architecture.arcgis.com/en/architectures/parcel-management/logical-reference-architecture.html"
md_url: "https://architecture.arcgis.com/en/architectures/parcel-management/logical-reference-architecture.md"
---
# Logical reference architecture
This logical view of the reference architecture defines individual software components, how they are separated or combined, and key interactions between them.
 
![PMSLogical-Arch.png](https://architecture.arcgis.com/assets/images/architectures/PMSLogical-Arch.png "Logical Reference Architecture for a Land Information Management System")

_Download a [Microsoft Visio file](/assets/diagrams/parcel-management-system-wl.vsdx) of this 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](intended-workflows.md) and [capabilities](introduction.md#capabilities).
## Software components
This diagram represents a variety of software components that contribute to the overall system design, including: 
- Apps to provide end-users with access to system capabilities. The primary apps used in Land Information Management Systems 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 apps and app 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), consisting of four 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 persisting [ArcGIS-managed](/en/overview/introduction-to-arcgis/arcgis-architecture/data.md#storage-considerations) data
 - [ArcGIS Web Adaptor](https://enterprise.arcgis.com/en/server/latest/install/windows/about-the-arcgis-web-adaptor.htm) to provide load balancing and reverse proxy capabilities. Additional load balancing and reverse proxy components may be recommended or required for certain scenarios, including [high availability](/en/architectures/parcel-management/design-choices-and-considerations.md#reliability) deployments.
- An additional ArcGIS Server site configured with the GIS Server role and used to deliver branch versioning and parcel fabric editing services.
- An [enterprise geodatabase](https://enterprise.arcgis.com/en/server/latest/manage-data/windows/enterprise-geodatabases-and-arcgis-enterprise.htm) to store and manage an ArcGIS Parcel Fabric through a [supported relational database management system](https://enterprise.arcgis.com/en/server/latest/manage-data/windows/enterprise-geodatabases-and-arcgis-enterprise.htm) (DBMS).
- An enterprise identity provider. Though not strictly required, this component is recommended to provide users with a single sign-on (SSO) experience when using ArcGIS Enterprise. 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) to [configure and manage ArcGIS Pro licenses](https://enterprise.arcgis.com/en/portal/latest/administer/windows/configure-arcgis-pro-licenses.htm) used by desktop editors. This component is no longer required for deployments of ArcGIS Enterprise 11.4 or newer.
- [ArcGIS Monitor](https://doc.arcgis.com/en/monitor/latest/get-started/windows/introduction-to-arcgis-monitor.htm) to monitor and optimize the system components and overall health.
- [ArcGIS Online](https://www.esri.com/en-us/arcgis/products/arcgis-online/overview), providing 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 and 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 Portal](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).
- ArcGIS Monitor communicates with a variety of ArcGIS and IT components, such as RDBMSs, using a variety of patterns and protocols. See [ArcGIS Monitor documentation](https://doc.arcgis.com/en/monitor/latest/get-started/windows/introduction-to-arcgis-monitor.htm) for more information.
- 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](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.