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.

Download a Microsoft Visio file of this architecture.
Learn more about diagramming resources for ArcGIS systems.

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 Parcel Management Systems are:
  • ArcGIS Pro - a professional GIS desktop application used by editors
  • Configurable apps and app builders - used by general users and editors
• An ArcGIS Enterprise base deployment, consisting of four components:
  • Portal for ArcGIS
  • ArcGIS Server configured as a hosting server
  • ArcGIS Data Store configured as a relational store for persisting ArcGIS-managed data
  • ArcGIS Web Adaptor 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 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 to store and manage an ArcGIS Parcel Fabric through a supported relational database management system (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.
• ArcGIS License Manager to configure and manage ArcGIS Pro licenses used by desktop editors. This component is no longer required for deployments of ArcGIS Enterprise 11.4 or newer.
• ArcGIS Monitor to monitor and optimize the system components and overall health.
• ArcGIS Online, 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.
• 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 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 components, such as RDBMSs, using a variety of patterns and protocols. See ArcGIS Monitor documentation 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, 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.