5.3.1 Deployment Consideration

ArcGIS Platform Conceptual Reference Architecture*

*Diagram included in the latest Esri white paper Architecting the ArcGIS Platform: Best Practices available at https://www.esri.com/content/dam/esrisites/en-us/media/pdf/architecting-thearcgis-platform.pdf

5.3.1 Deployment Consideration It is recommended that the IT Department upgrade to the full implementation of ArcGIS Enterprise. This environment would be accessible throughout the City and leverage Portal for access control and organization through User, Groups, and Roles.

ArcGIS Enterprise

At the release of ArcGIS version 10.5 in 2017, Esri made a name change to its products. What used to be ArcGIS for Server is now ArcGIS Enterprise and comes with 4 default components:

• Web Adaptor is an application that runs in your existing website and forwards requests to the machine hosting Portal and/or ArcGIS Server components. The Web

Adaptor is required for using Integrated Windows Authentication with your portal. • Portal plays a central role in organizing and sharing information within your ArcGIS system. The Portal provides a user-friendly, searchable repository for your maps and apps. It also helps you create and share new maps and apps to Portal authenticated users. To fully understand the tools for managing users, groups and content visit the

Esri site for Managing access to your portal.

Esri has implemented a new User Type licensing model at 10.8 for ArcGIS Enterprise users. With user types, an organization can match workflows and license users to any one of the five general-purpose types: Viewer, Data Editor, Field Worker, Creator and GIS Professional. The following graphic represents the 5 types.

Esri also released two additional specialized user types: Insights and Storyteller. Special functions such as the Utility Network Management, included as a recommendation for Utilities, are licensed as an extension for these user types.

• ArcGIS Server makes your geographic information available to others in your organization and optionally anyone with an Internet connection. This is accomplished through web services. • Data Store is an application that lets you easily configure data storage for hosting and federated servers used with your Portal. If you are not a database expert, ArcGIS Data

Store provides you with a convenient setup and configuration experience that creates the following different types of data stores.

o Relational data store - Stores your Portal's hosted feature layer data, including hosted feature layers created as output from spatial analysis tools run in the Portal. o Tile cache data store - Stores caches for your Portal's hosted scene layers. o Spatiotemporal big data store - Archives real-time observational data that you can use with an ArcGIS Server running ArcGIS GeoEvent Server that is federated with your Portal; also stores the results generated using ArcGIS

GeoAnalytics Server tools.

These components constitute the base deployment of, now, ArcGIS Enterprise. Along with this change, Esri also enhanced and renamed what used to be extensions to what is now referred to as Server Roles. This graphic illustrates the change with GeoAnalytics as the new server role addition to ArcGIS Enterprise starting at 10.5.

o GeoEvent Server tracks dynamic assets that are constantly changing location such as vehicles, aircraft, and vessels or stationary assets such as weather and environmental monitoring sensors. In addition, it provides real-time situational awareness for coordinated field activities. o Image Server provides a fast and efficient way to process, analyze and share large collections of imagery and rasters. Raster analytics quickly extracts information from large images or image collections. o Business Analyst Server provides analytic geointelligence tools that can be used in a number of business-centric situations and comes bundled with a set of business-related databases that contain information about business locations, competitors, and customer data to generate and deliver powerful spatial analyses. o GeoAnalytics Server provides distributed computing to vector-based feature data and can be used to analyze big data or accelerate traditional desktop analysis workflows.

The City may not need to deploy additional server roles at present but should consider this during the infrastructure configuration and deployment process. This section points out areas where new server roles might be considered.

High Level Deployment Pattern:

✓ Deploy ArcGIS Enterprise Advanced ✓ Deploy and configure ArcGIS Online for public maps, applications, and services ✓ Configure one-way replication of critical features to ArcGIS Online/Portal ✓ Insure adequate Ethernet access to departmental workstations

Security for outside access would be controlled by ArcGIS Online through built-in users, groups, and roles. Security for City users will be controlled by Active Directory Federation

Services configured within ArcGIS Enterprise to give the City users a single sign-on experience.

The design can be modified to fit the needs of the IT departments virtualization requirements. The following represents a suggested deployment pattern and infrastructure design for ArcGIS Enterprise consisting of:

• 1- 64-bit Windows Web Server located in the DMZ hosting IIS and Esri’s Web

Adaptors for Portal and ArcGIS. This server will use ports 80 and 443 for communication to internal systems and will host any Web applications or Web

AppBuilder solutions. • 1- 64-bit internal Windows system hosting Esri’s Portal component. This server will communicate to the DMZ Web Server on ports 7080 and 7443. • 1- 64-bit internal Windows system hosting Esri’s ArcGIS Server component. This server will communicate to the Portal server through ports 6080 and 6443. • 1- 64-bit internal Windows system hosting PostgreSQL, Esri’s EGDB Schema and the Data Store for Portal. This system will communicate on port 5432 for

PostgreSQL and ports 2443 and 9876 to Portal and ArcGIS Server. The Relational

Data Store for Portal can be hosted on a common or separate server as desired.

The Data Stores (Relational, Tile Cache) and RDBMS could reside on the same system. However, when significant load such as 3D activities are expected, the Tile Cache Data Store should be separated from the RDBMS. The Data Store components would consist of the EGDB schema and the Managed data storage for use in Portal. Also, as the need arises the GIS Technical team will be able to implement the appropriate ArcGIS Server Roles, such as Image Server and GeoEvent Server for real-time tracking and event monitoring. These machines can be added later to expand as needed.

The ArcGIS platform is designed to be scalable and can accommodate both small and large deployments. As the number of users increases, the City will need to review infrastructure capacity to determine the appropriate time to also increase the deployment size and the number of GIS servers. The ArcGIS platform supports a variety of load balancing techniques and technologies to accommodate this growth efficiently and effectively. In its simplest configuration, a multiple machine site is configured by setting up a pool of two or more GIS servers fronted by the ArcGIS Web Adaptor running on a web application server. In more complex configurations, third-party load balancers may be deployed in front of multiple GIS servers.

Implementing system health monitoring with a tool such as ArcGIS Monitor or PRTG Network Monitor should be considered to observe performance and alert about potential low resources. For this environment, GISinc recommends a hybrid approach using primarily Cloud-provided tools and services supplemented with other tools as desired.

It is important to note that this is the configuration guidelines for a production environment. Due to license constraints GIS previously had no staging environment but should now consider re-architecting a Staging and Development environment to better support the deployment best practices. These environments need to adequately represent and test functionality, though can be built to lower specifications or capacity. System changes are inevitable. It is a recommended practice to manage these changes in