GIS Product Architecture (CPT Design Demos) 42nd Edition

Arc17CapacityPlanning0301 release

This chapter shows how to configure the CPT Design tab to complete an ArcGIS Enterprise system architecture design. The CPT completes a system architecture design analysis based on the configured business requirements and solution architecture.

The CPT Design system design solution can be identified using a generic or detailed system architecture design analysis.
 * Generic architecture. The generic architecture CPT analysis assigns business workflow processing loads to four generic platform tiers (WTS, Web, GIS, and DBMS).
 * Detailed architecture. The detailed architecture CPT analysis assigns business workflow processing loads to separate platform tier for each server environment (based on established workflow separation requirements).

The CPT Design architecture discussion will be divided into the following five sections. "Best practice: A generic architecture CPT Design analysis can provide the correct platform solution when the total number of machines per tier are properly identified"
 * 1) Traditional ArcGIS Enterprise Design with ArcGIS Desktop (ArcMap) workflows. Most organizations today use ArcMap for their professional ArcGIS Desktop workflows with ArcGIS Server custom web services.
 * 2) ArcGIS Enterprise initial operational capability (IOC). Initial migration of traditional ArcGIS Enterprise to include ArcGIS Pro viewers and ArcGIS Enterprise system of engagement (Portal for ArcGIS).
 * 3) Pro ArcGIS Enterprise Design with ArcGIS Pro editors. Full benefits of ArcGIS Enterprise operations are realized with final migration from ArcMap to ArcGIS Pro workflows.
 * 4) Detailed Pro ArcGIS Enterprise system architecture design. This demonstration will show a complete system architecture design analysis using a detailed architecture configuration. The detailed CPT Design configurations are much more complex than the generic configurations, while both approaches can provide the same platform solution.
 * 5) ArcGIS Enterprise server licensing roles system architecture design. GIS Server roles are included in the final system architecture design to demonstration a complete ArcGIS Enterprise solution.

Traditional ArcGIS Enterprise business requirements
Figure A1-9b.1 shows GIS business requirements with ArcMap editors and ArcMap viewers.

Local Area Network (1000 Mbps bandwidth) Wide Area Network (310 Mbps bandwidth) Internet (90 Mbps bandwidth) 
 * ArcMap editors = 10 users
 * ArcMap viewers = 20 users
 * Web local clients = 55 users
 * Web imagery clients = 10 users
 * ArcMap editors = 10 users
 * ArcMap viewers = 70 users
 * Web local clients = 20 users
 * Web imagery clients = 5 users
 * Web local clients = 10 users
 * Web public clients = 73,000 TPH

Traditional ArcMap ArcGIS Enterprise platform technical architecture
Figure A1-9b.2 shows the traditional ArcGIS Enterprise platform architecture with remote ArcMap clients supported on a central host server farm. The platform technical architecture provides a framework for supporting the data center platform configuration. This initial section will configure the CPT Design to complete a generic ArcGIS Enterprise capacity planning analysis with remote ArcMap clients.

The generic capacity planning analysis will configure the platform architecture on four platform tier.
 * Terminal server tier. Host remote ArcGIS Desktop (ArcMap) terminal clients.
 * Web Server tier. Host internal and public Web and Portal server machines.
 * GIS Server tier. Host internal and public ArcGIS Server machines and Server Roles.
 * DBMS tier. Host internal and public Database and Data Store machines.

"Best practice: An estimate of the total number of machines for each tier can be identified from the platform technical architecture drawing." 

Traditional ArcMap ArcGIS Enterprise project workflows
Figure A1-9b.3 shows CPT Workflow tab configured to support ArcGIS Enterprise business requirements with legacy ArcMap workflows.

ArcMap Wkstn Workflows ArcMap Citrix Workflows Server Workflows 
 * DeskMapEdit. Local ArcMap Editors accessing Enterprise Geodatabase data source.
 * DeskMapView. Local ArcMap Viewers accessing Enterprise Geodatabase data source.
 * CitrixMapEdit. Remote Editors accessing central hosted ArcMap applications with Enterprise Geodatabase data source.
 * CitrixMapView. Remote Viewers accessing central hosted ArcMap applications with Enterprise Geodatabase data source.
 * WebLocalHvy. Internal clients accessing Web services with central Enterprise Geodatabase data source.
 * WebPublicHvyOps. Public clients accessing Web services with central Enterprise Geodatabase data source.
 * WebImage: ArcGIS Server image services with imagery data source.

Traditional ArcMap ArcGIS Enterprise design requirements and network suitability analysis
Figure A1-9b.4 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with legacy ArcMap workflows.

Project workflows for each user location are selected in column B. Peak concurrent workflow loads are identified in terms of users (Column C) or throughput (Column D) for each business workflow at each location.

LAN Local clients WAN remote clients Internet remote clients
 * DeskMapEdit. 10 users. (supports local ArcMap editors)
 * DeskMapView. 20 users. (supports local ArcMap viewers)
 * WebLocalHvy. 55 clients. (supports local Web clients)
 * WebImage. 10 clients. (supports local Imagery service clients
 * CitrixMapEdit: 10 users (supports remote ArcMap WAN editors)
 * CitrixMapView: 70 users (supports remote ArcMap WAN viewers)
 * WebLocalHvy 20 clients. (supports remote WAN internal Web clients)
 * WebImage. 5 clients. (supports remote WAN internal Imagery service clients)
 * WebLocalHvy 20 clients. (supports remote internal Internet Web clients)
 * WebPublicHvyOps 73,000 TPH. (supports remote public Internet Web clients)

Bandwidth for each network location is entered in column H. GREY network rows represent central Data Center gateways and GREEN network rows represent remote site gateways. While the project workflows are configured and the network bandwidth is entered, the CPT completes the network suitability analysis. Bandwidth utilization is shown in column I for each network gateway.

"Best practice: Business requirements were selected to demonstrate how to configure the various ArcGIS project workflow patterns on the CPT Design tab." 

Generic Traditional ArcMap ArcGIS Enterprise Platform Configuration
Figure A1-9b.5 shows CPT Design tab general Platform Tier configuration to support ArcGIS Enterprise business requirements with legacy ArcMap workflows.

Generic Platform tier configuration
 * WTS tier. Provides platform tier for remote ArcGIS Desktop (ArcMap) clients.
 * Web tier. Provides platform tier for web server components (Web servers, Portal for ArcGIS servers).
 * GIS tier. Provides platform tier for internal and public ArcGIS Server components (GIS Server, Hosting Server, Image Server).
 * DBMS tier. Provides platform tier for internal and public data source components (tabular DBMS, Production Enterprise Geodatabase, Relational Data Store, Publishing Enterprise Geodatabase).

"Best practice: Platform selection for each tier is identified in column B." 

Generic Traditional ArcMap ArcGIS Enterprise Software Configuration
Figure A1-9b.6 shows CPT Design tab general project workflow software configuration to support ArcGIS Enterprise business requirements with legacy ArcMap workflows.

Generic platform assignments can be identified in row 5 for all workflow software components. Proper Data Source must be selected for each workflow (Column R) Mosaic Dataset host platform tier.
 * Client component = Client. Client load for all project workflows.
 * Citrix component = WTS. Remote app or desktop loads on WTS platform tier.
 * Web component = Web. Web server loads on Web tier.
 * Portal component = Web. Portal for ArcGIS loads on Web tier.
 * SOC component = GIS. ArcGIS Server SOC loads on GIS tier.
 * DS/MDS = Direct Connect. Direct Connect assigns the SDE processing load to the client application (only supported option).
 * DBMS = DBMS. All database loads are assigned to the DBMS tier.
 * Small File GDB. Appropriate selection for DeskMapFile, CitrixMapFile, and AGSFile workflows.
 * TIFF uncompressed. Appropriate selection for AGSImage workflow.
 * DB_DBMS. Appropriate selection for all workflows with DBMS data source.
 * For imagery workflows, the selection in column O assigns the mosaic dataset to the hosting server tier (options are FGDB or a selected Enterprise GDB platform). Imagery MDS load must be assigned for the AGSImage row (Cell O9 and O15) when the mosaic dataset it is not located on the client application.

The CPT Software Configuration module assigns workflow component software processing loads to the configured platform tier. Proper configuration of this model supports the system architecture design capacity planning analysis. 

Generic Traditional ArcMap ArcGIS Enterprise platform solutions
There are three different ArcMap ArcGIS Enterprise platform solutions.
 * ArcMap App Sessions ArcGIS Enterprise physical platform solution.
 * ArcMap App Sessions ArcGIS Enterprise virtual platform solution.
 * ArcMap VDI (Virtual Desktop Infrastructure) ArcGIS Enterprise virtual platform solution.

Generic Traditional ArcMap App Sessions ArcGIS Enterprise physical platform solution
Figure A1-9b.7 shows CPT Design tab general ArcGIS Enterprise minimum physical platform solution with legacy ArcMap workflows.

Once the CPT Design requirements analysis, network suitability, platform configuration, and software configuration modules are properly configured, Excel completes the system architecture design. The Platform Solution module (Figure A1-9a.26 Cells V30:AE93) shows the generic platform solution.

Platform solution will depend on the platform server selections (Column B).
 * Xeon Gold 5122 4 core (1 chip) 3600 MHz for all platform tier.

Platform tier High Avail selection (Column H) generates platform solution to satisfy high availability requirements.

"Best practice: Platform tier 80% rollover setting (Column H) adds an additional platform node when utilization exceeds set value."

The Platform Solution module shows the number of server nodes required to support each platform tier.
 * WTS tier = 3 platform nodes.
 * Web tier = 2 platform nodes.
 * GIS tier = 2 platform nodes.
 * DBMS tier = 1 platform node with failover server for DBMS tier.

A total of 9 Xeon Gold 5122 4 core (1 chip) 3600 MHz servers are required to support the minimum physical platform solution. Estimated hardware cost is $91,360 (Cell Y93).

"Warning: The minimum configuration shows all server components deployed together on the same nodes for each platform tier."

"Best practice: Workflow Separation. ArcGIS Enterprise platform components (with different server roles) should be deployed on separate platform sites to reduce contention and simplify system administration." 

Generic Traditional ArcMap App Sessions ArcGIS Enterprise physical platform solution (Workflow Separation)
Figure A1-9b.8 shows CPT Design tab general ArcGIS Enterprise physical platform solution with legacy ArcMap workflows applying workflow separation best practices. IT best practices dictate that the best data center design deploys different server environments on dedicated server machines. Each of the different ArcMap Enterprise server environments are identified in the ArcMap Platform Architecture diagram shown in Figure A1-9b.2.

ArcMap Platform Architecture diagram
 * Terminal server (WTS) tier. Host remote ArcGIS Desktop (ArcMap) terminal clients (one server environment).
 * Web Server tier. Internal and public Web machines (2 server environments).
 * GIS Server tier. Internal and public ArcGIS Server machines and Image Server Role (3 server environments).
 * DBMS tier. Production and Publishing Database machines (2 server environments).

Each server environment must be configured for high availability, which means we need a minimum of two machine nodes for each server environment. This would double the number of servers identified in the ArcMap Platform Architecture shown above.

The minimum physical platform solution in Figure A1-9b.8 identifies the average server utilization for each tier, but it does not show how the load is distributed for the different server environments (limitation of the generic design approach). The WTS tier nodes will be identified with the generic design, but we will need to identify the total number of nodes for the Web, GIS, and DBMS tier required for a workflow separation solution.

Platform tier nodes required for workflow separation.
 * Web tier = 4 nodes, two for each server environment.
 * GIS tier = 6 nodes, minimum of two for each server environment.
 * DBMS tier = 4 nodes, two for each server environment.

Enter the total server nodes required for workflow separation in column H for the Web, GIS, and DBMS platform tier. A total of 17 Xeon Xeon Gold 5122 4 core (1 chip) 3600 MHz servers are required to support the final workflow separation platform solution. Estimated hardware cost is $168,493 (Cell Y93).

Most of the physical server platforms in this design solution have minimum processing loads and are not well utilized. This CPT Design demonstrates the typical activity for an enterprise data center supported by physical server platforms (poor utilization of available platform resources).

"Best practice: Data center virtualization simplifies server administration (workflow separation) and reduces cost (server consolidation)." 

Generic Traditional ArcMap App Sessions ArcGIS Enterprise virtual server platform solution
Figure A1-9b.9 shows CPT Design tab general ArcGIS Enterprise minimum virtual server platform solution with legacy ArcMap workflows. The data center platform architecture is deployed in two physical server environments (Citrix and Server virtual host platform tier).

"Best practice: Data center virtualization separates the server machines from the underlying physical hardware, deploying a full platform architecture in a consolidated environment supported by a virtual server host platform tier."

Virtual Server host platform tier
 * Citrix tier. Host the Citrix XenApp (application sessions) on the WTS tier.
 * Server tier. Hosts the virtual server machines deployed on the Web, GIS, and DBMS tier.

The virtual server configuration shows the virtual platform architecture. The virtual server configuration is identified for each platform tier (Column I) selecting the virtual server host machine (Citrix or Server), the number of virtual server core/node, and the virtual server designation (Vserver). The Platform Solution module shows the number of server nodes required to support each platform tier.

Virtual Server platform tier
 * WTS tier = Five 2-core virtual server platform nodes assigned to the Citrix virtual host.
 * Web tier = Two 2-core virtual server platform nodes assigned to the Server virtual host.
 * GIS tier = Three 2-core virtual server platform nodes assigned to the Server virtual host.
 * DBMS tier = One 4-core virtual server platform node with failover server for DBMS tier assigned to the Server virtual host.

The optimum virtual host server platform tier configuration is selected to minimize the overall hardware cost (Cell Y93). Following platforms were selected to support the virtual server host platform tier.
 * Citrix tier. 2x Xeon Gold 6128 12 core (2 chip) 3400 MHz servers, each with 172 GB RAM (Cell C95).
 * Server tier. 2x Xeon Gold 5122 8 core (2 chip) 3600 MHz servers, each with 112 GB RAM (Cell C98).

The Xeon Gold 6128 12 core (2 chip) 3400 MHz platform provided the lowest cost Citrix hardware solution and the Xeon Gold 5122 8 core (2 chip) 3600 MHz platform provided the lowest cost Server hardware solution, based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $107,984 (Cell Y93).

"Warning: The minimum configuration shows all server components deployed together on the same nodes for each platform tier."

"Best practice: Workflow Separation. ArcGIS Enterprise platform components (with different server roles) should be deployed on separate platform sites to reduce contention and simplify system administration." 

Generic Traditional ArcMap App Sessions with ArcGIS Enterprise virtual server platform solution (Workflow Separation)
Figure A1-9b.10 shows CPT Design tab general ArcGIS Enterprise virtual server platform solution with legacy ArcMap workflows applying workflow separation best practices.

Platform tier nodes required for workflow separation.
 * Web tier = Four (4) 2-core nodes, two for each server environment.
 * GIS tier = Six (6) 2-core nodes, minimum of two for each server environment.
 * DBMS tier = Four (4) 2-core nodes, two for each server environment.

Enter the total server nodes required for workflow separation in column H for the Web, GIS, and DBMS virtual server platform tier.

The optimum virtual host server platform tier configuration is selected to minimize the overall hardware cost (Cell Y93). Following platforms were selected to support the virtual server host platform tier.
 * Citrix tier. 2x Xeon Gold 6128 12 core (2 chip) 3400 MHz servers, each with 172 GB RAM (Cell C95).
 * Server tier. 2 x Xeon Gold 5122 8 core (2 chip) 3600 MHz servers, each with 216 GB RAM (Cell C98).

Notice that the Virtual Server host platform tier solution remains very close to the minimum virtual server platform solution, other than the additional memory requirements for the Server tier servers.

The Xeon Gold 6128 12 core (2 chip) 3400 MHz platforms (Citrix host) and Xeon Gold 5122 8 core (2 chip) 3600 MHz (Server host) again provided the lowest cost hardware solution, based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $114,654 (Cell Y93), slightly higher cost due to additional Server tier platform memory requirements.

"Best practice: Data center virtualization simplifies server administration (workflow separation) and reduces cost (server consolidation)." 

Generic Traditional ArcMap Virtual Desktop Infrastructure (VDI) with ArcGIS Enterprise virtual server platform solution (Workflow Separation)
Figure A1-9b.11 shows CPT Design tab general ArcGIS Enterprise virtual server platform solution with legacy ArcMap workflows applying workflow separation best practices. The ArcMap VDI architecture supports remote ArcMap client desktops (not only the application session) on the CitrixMap VDI host machine. Each VDI session includes a full desktop operating system.

The optimum virtual host server platform tier configuration is selected to minimize the overall hardware cost (Cell Y93). Following platforms were selected to support the virtual server host platform tier.
 * Citrix tier. 2x Xeon Gold 6128 12 core (2 chip) 3400 MHz servers, each with 732 GB RAM (Cell C95).
 * Server tier. 2x Xeon Gold 5122 8 core (2 chip) 3600 MHz servers, each with 216 GB RAM (Cell C98).

Notice that the WTS host platform tier platform selection has changed. The VDI architecture increases the load on the WTS host platform tier.

The Xeon Gold 6128 12 core (2 chip) 3400 MHz platforms provide the optimum WTS hardware solution, while the Xeon Gold 5122 8 core (2 chip) 3600 MHz platforms provided the lowest cost Server tier solution. Pricing is based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $144,669 (Cell Y93), slightly higher cost due to additional loads and memory requirements on the WTS tier. 

ArcGIS Enterprise Initial Operational Capability (IOC) business requirements
The initial migration from traditional ArcGIS Server architecture to ArcGIS Enterprise with Portal for ArcGIS deploys system of engagement with minimum cost and operational risk. Existing user licenses are used to support deployment of the ArcGIS Enterprise system of engagement. Additional feature services support system of engagement collaboration and sharing services. Desktop editors will continue to use ArcMap with traditional system of record workflows. Desktop viewers will migrate to the more powerful ArcGIS Pro environment.

Figure A1-9b.12 shows ArcGIS Enterprise GIS business requirements with ArcMap editors and ArcGIS Pro viewers.

Local Area Network (1000 Mbps bandwidth) Wide Area Network (310 Mbps bandwidth) Internet (90 Mbps bandwidth) 
 * ArcMap editors = 10 users
 * ArcGIS Pro viewers = 20 users
 * ArcGIS Pro Portal feature services (system of engagement) = 720 TPH
 * Web local clients = 55 users
 * Web imagery clients = 10 users
 * Web local Portal feature services (system of engagement) = 1,980 TPH
 * ArcMap editors = 10 users
 * ArcGIS Pro viewers = 70 users
 * ArcGIS Pro Portal feature services (system of engagement) = 2,520 TPH
 * Web local clients = 20 users
 * Web imagery clients = 5 users
 * Web local Portal feature services (system of engagement) = 720 TPH
 * Web local clients = 10 users
 * Web public Portal feature services (system of engagement) = 7,660 TPH
 * Web public clients = 73,000 TPH

ArcGIS Enterprise IOC platform technical architecture
Figure A1-9b.13 shows the IOC ArcGIS Enterprise platform architecture with remote ArcMap Editor clients supported on a central host server farm.

The generic capacity planning analysis will configure the platform architecture on four platform tier.
 * Terminal server tier. Host remote DeskEdit (ArcMap) terminal clients.
 * Web Server tier. Host internal and public Web and Portal server machines.
 * GIS Server tier. Host internal and public ArcGIS Server machines and Server Roles.
 * DBMS tier. Host internal and public Database and Data Store machines.

"Best practice: An estimate of the total number of machines for each tier can be identified from the platform technical architecture drawing." 

ArcGIS Enterprise IOC project workflows (ArcMap editors and ArcGIS Pro viewers)
Figure A1-9b.14 shows CPT Workflow tab configured to support ArcGIS Enterprise business requirements with legacy ArcMap Editor workflows. Remote ArcGIS Pro viewers will access registered feature services and leverage client feature caching (workflow assumes 80% of the features are cached on the ArcGIS Pro client).

ArcMap Wkstn Workflows ArcGIS Pro Wkstn Workflows DeskProView. Local ArcGIS Pro Viewers accessing Enterprise Geodatabase data source. DeskProFSvcView. Remote ArcGIS Pro Viewers accessing registered Portal feature services leveraging 80% client feature cache. DeskProFsvc20%. Remote ArcGIS Pro Viewers accessing 20% dynamic Web map services with basemap cache. ArcMap Citrix Workflows Server Workflows 
 * DeskMapEdit. Local ArcMap Editors accessing Enterprise Geodatabase data source.
 * CitrixMapEdit. Remote Editors accessing central hosted ArcMap applications with Enterprise Geodatabase data source.
 * WebLocalHvy. Internal clients accessing Web services with central Enterprise Geodatabase data source.
 * WebPublicHvyOps. Public clients accessing Web services with central Enterprise Geodatabase data source.
 * WebImage. ArcGIS Server image services with imagery data source.
 * PortalFSvc20%. Internet clients accessing 20% dynamic Web map services with basemap cache.

ArcGIS Enterprise IOC design requirements and network suitability analysis
Figure A1-9b.15 shows CPT Design tab requirements section configured to support IOC ArcGIS Enterprise business requirements with legacy ArcMap Editor workflows.

Project workflows for each user location are selected in column B. Peak concurrent workflow loads are identified in terms of users (Column C) or throughput (Column D) for each business workflow at each location.

LAN Local clients WAN remote clients Internet remote clients
 * DeskMapEdit. 10 users. (supports local ArcMap editors)
 * DeskProView. 20 users. (supports local ArcMap viewers)
 * DeskProFsvc20%. 720 TPH. (supports local desktop named user portal collaboration)
 * WebLocalHvy. 55 clients. (supports local Web clients)
 * WebImage. 10 clients. (supports local Imagery service clients
 * PortalFsvc20%. 1,980 TPH. (supports local Web client named user portal collaboration)
 * CitrixMapEdit. 10 users (supports remote ArcMap WAN editors)
 * DeskProView. 70 users (supports remote ArcGIS Pro WAN viewers)
 * DeskProFsvc20%. 2,520 TPH. (supports WAN desktop named user portal collaboration)
 * WebLocalHvy 20 clients. (supports remote WAN internal Web clients)
 * WebImage. 5 clients. (supports remote WAN internal Imagery service clients)
 * PortalFsvc20%. 720 TPH. (supports WAN Web client named user portal collaboration)
 * WebLocalHvy 20 clients. (supports remote internal Internet Web clients)
 * PortalFsvc20%. 7,660 TPH. (supports Internet Web map published Portal services)
 * WebPublicHvyOps 73,000 TPH. (supports remote public Internet Web clients)

Bandwidth for each network location is entered in column H. GREY network rows represent central Data Center gateways and GREEN network rows represent remote site gateways. While the project workflows are configured and the network bandwidth is entered, the CPT completes the network suitability analysis. Bandwidth utilization is shown in column I for each network gateway.

"Best practice: Business requirements were selected to demonstrate how to configure the various ArcGIS project workflow patterns on the CPT Design tab." 

Generic ArcGIS Enterprise IOC Platform Configuration with ArcMap Editors
Figure A1-9b.16 shows CPT Design tab generic Platform Tier configuration to support IOC ArcGIS Enterprise business requirements with legacy ArcMap Editor workflows.

Generic Platform tier configuration
 * WTS tier. Provides platform tier for remote ArcMap Editors.
 * Web tier. Provides platform tier for web server components (Web servers, Portal for ArcGIS servers).
 * GIS tier. Provides platform tier for internal and public ArcGIS Server components (GIS Server, Hosting Server, Image Server).
 * DBMS tier. Provides platform tier for internal and public data source components (Production Enterprise Geodatabase, Relational Data Store, Publishing Enterprise Geodatabase).

"Best practice: Platform selection for each tier is identified in column B." 

Generic ArcGIS Enterprise IOC Software Configuration
Figure A1-9b.17 shows CPT Design tab generic software configuration to support IOC ArcGIS Enterprise business requirements with legacy ArcMap Editor workflows.

Generic platform assignments can be identified in row 5 for all workflow software components. Proper Data Source must be selected for each workflow (Column R) Mosaic Dataset host platform tier.
 * Client component = Client. Client load for all project workflows.
 * Citrix component = WTS. Remote app or desktop loads on WTS platform tier.
 * Web component = Web. Web server loads on Web tier.
 * Portal component = Web. Portal for ArcGIS loads on Web tier.
 * SOC component = GIS. ArcGIS Server SOC loads on GIS tier.
 * DS/MDS = Direct Connect. Direct Connect assigns the SDE processing load to the client application (only supported option).
 * DBMS = DBMS. All database loads are assigned to the DBMS tier.
 * Small File GDB. Appropriate selection for DeskMapFile, CitrixMapFile, and AGSFile workflows.
 * TIFF uncompressed. Appropriate selection for AGSImage workflow.
 * DB_DBMS. Appropriate selection for all workflows with DBMS data source.
 * For imagery workflows, the selection in column O assigns the mosaic dataset to the hosting server tier (options are FGDB or a selected Enterprise GDB platform). Imagery MDS load must be assigned for the AGSImage row (Cell O9 and O15) when the mosaic dataset it is not located on the client application.

The CPT Software Configuration module assigns workflow component software processing loads to the configured platform tier. Proper configuration of this model supports the system architecture design capacity planning analysis. <br style="clear: both" />

Generic ArcGIS Enterprise IOC platform solutions
There are three different ArcMap ArcGIS Enterprise platform solutions.
 * ArcMap App Sessions ArcGIS Enterprise physical platform solution.
 * ArcMap App Sessions ArcGIS Enterprise virtual platform solution.
 * ArcMap VDI (Virtual Desktop Infrastructure) ArcGIS Enterprise virtual platform solution.

Generic ArcMap App Sessions ArcGIS Enterprise IOC physical platform solution
Figure A1-9b.18 shows CPT Design tab general ArcGIS Enterprise minimum physical platform solution with legacy ArcMap workflows.

Once the CPT Design requirements analysis, network suitability, platform configuration, and software configuration modules are properly configured, Excel completes the system architecture design. The Platform Solution module (Figure A1-9.26 Cells V30:AE93) shows the generic platform solution.

Platform solution will depend on the platform server selections (Column B).
 * Xeon Gold 5122 4 core (1 chip) 3600 MHz for all platform tier.

Platform tier High Avail selection (Column H) generates platform solution to satisfy high availability requirements.

"Best practice: Platform tier 80% rollover setting (Column H) adds an additional platform node when utilization exceeds set value."

The Platform Solution module shows the number of server nodes required to support each platform tier.
 * WTS tier = 2 platform nodes.
 * Web tier = 2 platform nodes.
 * GIS tier = 2 platform nodes.
 * DBMS tier = 1 platform node with failover server for DBMS tier.

A total of 8 Xeon Gold 5122 4 core (1 chip) 3600 MHz servers are required to support the minimum physical platform solution. Estimated hardware cost is $80,468 (Cell Y93).

"Warning: The minimum configuration shows all server components deployed together on the same nodes for each platform tier."

"Best practice: Workflow Separation. ArcGIS Enterprise platform components (with different server roles) should be deployed on separate platform sites to reduce contention and simplify system administration." <br style="clear: both" />

Generic ArcMap App Sessions ArcGIS Enterprise IOC physical platform solution (Workflow Separation)
Figure A1-9b.19 shows CPT Design tab general ArcGIS Enterprise physical platform solution with legacy ArcMap workflows applying workflow separation best practices.

IT best practices dictate that the best data center design deploys different server environments on dedicated server machines. Each of the different ArcMap Enterprise server environments are identified in the ArcMap Platform Architecture diagram shown in Figure A1-9b.13.

ArcMap Platform Architecture diagram
 * Terminal server (WTS) tier. Host remote ArcGIS Desktop (ArcMap) terminal clients (one server environment).
 * Web Server tier. Internal and public Web and Portal machines (4 server environments).
 * GIS Server tier. Internal and public ArcGIS Server machines, Internal and Public Portal ArcGIS Server host machines, and Image Server Role (5 server environments).
 * DBMS tier. Production and Publishing Database machines with additional internal and public relational data store (4 server environments).

Each server environment must be configured for high availability, which means we need a minimum of two machine nodes for each server environment. This would double the number of servers identified in the ArcMap Platform Architecture shown above.

The minimum physical platform solution in Figure A1-9b.19 identifies the average server utilization for each tier, but it does not show how the load is distributed for the different server environments (limitation of the generic design approach). The WTS tier nodes will be identified with the generic design, but we will need to identify the total number of nodes for the Web, GIS, and DBMS tier required for a workflow separation solution.

Platform tier nodes required for workflow separation.
 * Web tier = 8 nodes, two for each server environment.
 * GIS tier = 10 nodes, minimum of two for each server environment.
 * DBMS tier = 8 nodes, two for each server environment.

Enter the total server nodes required for workflow separation in column H for the Web, GIS, and DBMS platform tier. A total of 26 Xeon Gold 5122 4 core (1 chip) 3600 MHz servers are required to support the final workflow separation platform solution. Estimated hardware cost is $274,968 (Cell Y93).

Most of the physical server platforms in this design solution have minimum processing loads and are not well utilized. This CPT Design demonstrates the typical activity for an enterprise data center supported by physical server platforms (poor utilization of available platform resources).

"Best practice: Data center virtualization simplifies server administration (workflow separation) and reduces cost (server consolidation)." <br style="clear: both" />

Generic ArcMap App Sessions ArcGIS Enterprise IOC virtual server platform solution
Figure A1-9b.20 shows CPT Design tab general ArcGIS Enterprise minimum virtual server platform solution with legacy ArcMap Editor workflows. The data center platform architecture is deployed in two physical server environments (Citrix and Server virtual host platform tier).

"Best practice: Data center virtualization separates the server machines from the underlying physical hardware, deploying a full platform architecture in a consolidated environment supported by a virtual server host platform tier."

Virtual Server host platform tier
 * Citrix tier. Host the Citrix XenApp (application sessions) on the WTS tier.
 * Server tier. Hosts the virtual server machines deployed on the Web, GIS, and DBMS tier.

The virtual server configuration shows the virtual platform architecture. The virtual server configuration is identified for each platform tier (Column I) selecting the virtual server host machine (Citrix or Server), the number of virtual server core/node, and the virtual server designation (Vserver). The Platform Solution module shows the number of server nodes required to support each platform tier.

Virtual Server platform tier
 * WTS tier = Two 2-core virtual server platform nodes assigned to the Citrix virtual host.
 * Web tier = Two 2-core virtual server platform nodes assigned to the Server virtual host.
 * GIS tier = Two 2-core virtual server platform nodes assigned to the Server virtual host.
 * DBMS tier = One 2-core virtual server platform node with failover server for DBMS tier assigned to the Server virtual host.

The optimum virtual host server platform tier configuration is selected to minimize the overall hardware cost (Cell Y93). Following platforms were selected to support the virtual server host platform tier.
 * Citrix tier. 2x Xeon Gold 5122 8 core (2 chip) 3600 MHz servers, each with 72 GB RAM (Cell C95).
 * Server tier. 2x Xeon Gold 6128 12 core (2 chip) 3400 MHz servers, each with 124 GB RAM (Cell C98).

The Xeon Gold 5122 8 core (2 chip) 3600 MHz platform provided the lowest cost Citrix hardware solution and the Xeon Gold 6128 12 core (2 chip) 3400 MHz platform provided the lowest cost Server hardware solution, based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $106,317. (Cell Y93).

"Warning: The minimum configuration shows all server components deployed together on the same nodes for each platform tier."

"Best practice: Workflow Separation. ArcGIS Enterprise platform components (with different server roles) should be deployed on separate platform sites to reduce contention and simplify system administration." <br style="clear: both" />

Generic ArcMap App Sessions with ArcGIS Enterprise IOC virtual server platform solution (Workflow Separation)
Figure A1-9b.21 shows CPT Design tab general ArcGIS Enterprise virtual server platform solution with legacy ArcMap Editor workflows applying workflow separation best practices.

Platform tier nodes required for workflow separation.
 * Web tier = Eight 2-core nodes, two for each server environment.
 * GIS tier = Ten 2-core nodes, minimum of two for each server environment.
 * DBMS tier = Eight 2-core nodes, two for each server environment.

Enter the total server nodes required for workflow separation in column H for the Web, GIS, and DBMS virtual server platform tier.

The optimum virtual host server platform tier configuration is selected to minimize the overall hardware cost (Cell Y93). Following platforms were selected to support the virtual server host platform tier.
 * Citrix tier. 2x Xeon Gold 5122 8 core (2 chip) 3600 MHz servers, each with 72 GB RAM (Cell C95).
 * Server tier. 2 x Xeon Gold 6128 12 core (2 chip) 3400 MHz servers, each with 412 GB RAM (Cell C98).

Notice that the Virtual Server host platform tier solution remains very close to the minimum virtual server platform solution, other than the additional memory requirements for the Server tier servers.

The XXeon Gold 5122 8 core (2 chip) 3600 MHz platforms (Citrix host) and Xeon Gold 6128 12 core (2 chip) 3400 MHz platforms (Server host) again provided the lowest cost hardware solution, based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $119,657 (Cell Y93), slightly higher cost due to additional Server tier platform memory requirements.

"Best practice: Data center virtualization simplifies server administration (workflow separation) and reduces cost (server consolidation)." <br style="clear: both" />

Generic ArcMap Virtual Desktop Infrastructure (VDI) with ArcGIS Enterprise IOC virtual server platform solution (Workflow Separation)
Figure A1-9b.22 shows CPT Design tab general ArcGIS Enterprise virtual server platform solution with legacy ArcMap Editor workflows applying workflow separation best practices. The ArcMap VDI architecture supports remote ArcMap Editor client desktops (not only the application session) on the Citrix VDI host machine. Each VDI session includes a full desktop operating system.

The optimum virtual host server platform tier configuration is selected to minimize the overall hardware cost (Cell Y93). Following platforms were selected to support the virtual server host platform tier.
 * Citrix tier. 2x Xeon Gold 5122 8 core (2 chip) 3600 MHz servers, each with 98 GB RAM (Cell C95).
 * Server tier. 2 x Xeon Gold 6128 12 core (2 chip) 3400 MHz servers, each with 412 GB RAM (Cell C98).

Notice that the WTS host platform tier platform selection has changed. The VDI architecture increases the load on the WTS host platform tier.

The Xeon Gold 5122 8 core (2 chip) 3600 MHz platforms provide the optimum WTS hardware solution, while the Xeon Gold 6128 12 core (2 chip) 3400 MHz platforms provided the lowest cost Server tier solution. Pricing is based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $121,324 (Cell Y93), slightly higher cost due to additional loads and memory requirements on the WTS tier. <br style="clear: both" />

Pro ArcGIS Enterprise business requirements
The final ArcGIS Enterprise migration will support Desktop editors with the more powerful ArcGIS Pro client.

Figure A1-9b.23 shows ArcGIS Enterprise GIS business requirements with ArcGIS Pro editors and viewers.

Local Area Network (1000 Mbps bandwidth) Wide Area Network (310 Mbps bandwidth) Internet (90 Mbps bandwidth) <br style="clear: both" />
 * ArcGIS Pro editors = 10 users
 * ArcGIS Pro viewers = 20 users
 * ArcGIS Pro Portal feature services (system of engagement) = 720 TPH
 * Web local clients = 55 users
 * Web imagery clients = 10 users
 * Web local Portal feature services (system of engagement) = 1,980 TPH
 * ArcGIS Pro editors = 10 users
 * ArcGIS Pro viewers = 70 users
 * ArcGIS Pro Portal feature services (system of engagement) = 2,520 TPH
 * Web local clients = 20 users
 * Web imagery clients = 5 users
 * Web local Portal feature services (system of engagement) = 720 TPH
 * Web local clients = 10 users
 * Web public Portal feature services (system of engagement) = 7,660 TPH
 * Web public clients = 73,000 TPH

Generic Pro ArcGIS Enterprise platform technical architecture
Figure A1-9b.24 shows an overview of the ArcGIS Enterprise platform architecture with remote ArcMap and ArcGIS Pro clients supported on a central host server farm. The platform technical architecture provides a framework for supporting the data center platform configuration.

This first part of this section will focus on upgrading the Terminal server tier to support remote ArcGIS Pro clients.

Capacity planning analysis for the ArcGIS Pro VDI deployment will support the data center platform architecture on four virtual platform tiers.
 * Terminal server tier. Host remote ArcGIS Pro terminal clients.
 * Web Server tier. Host internal and public Web and Portal server machines.
 * GIS Server tier. Host internal and public ArcGIS Server machines and Server Roles.
 * DBMS tier. Host internal and public Database and Data Store machines.

Two alternative remote ArcGIS Pro desktop client deployment patterns will be discussed to complete the ArcGIS Pro Enterprise architecture discussion.
 * Remote Pro workstation Enterprise Geodatabase connections.
 * Remote Pro workstation Web GIS Portal feature service connections.

Capacity planning analysis for remote ArcGIS Pro client deployment patterns will support the data center platform architecture on three virtual platform tiers (no terminal server tier). <br style="clear: both" />
 * Web Server tier. Host internal and public Web and Portal server machines.
 * GIS Server tier. Host internal and public ArcGIS Server machines and Server Roles.
 * DBMS tier. Host internal and public Database and Data Store machines.

Pro ArcGIS Enterprise project workflows
Figure A1-9b.25 shows CPT Workflow tab configured to support ArcGIS Enterprise business requirements with ArcGIS Pro desktop workflows.

ArcGIS Pro workstation workflows (Local ArcMap clients)
 * DeskProEdit. ArcGIS Pro workstation editor clients with Enterprise Geodatabase data source.
 * DeskProView. ArcGIS Pro workstation viewer clients with Enterprise Geodatabase data source.
 * DeskPro$FSvcEdit20%. ArcGIS Pro Web GIS editor clients with 20% local feature cache.
 * DeskPro$FSvcView20%. ArcGIS Pro Web GIS viewer clients with 80% local feature cache.
 * DeskProFsvc20%. Web GIS clients with Portal hosted data source.

ArcGIS Pro Citrix workflows (ArcGIS Pro deployed on host Citrix tier)
 * CitrixProEdit. ArcGIS Pro remote VDI editor clients with Enterprise Geodatabase data source.
 * CitrixProView. ArcGIS Pro remote VDI viewer clients with Enterprise Geodatabase data source.
 * CitrixProFSvc20%. ArcGIS Pro remote VDI clients accessing Portal Web map services (20% dynamic with basemap).
 * CitrixProBatch. ArcGIS Pro geoprocessing services executed on the host Citrix server tier.

ArcGIS Server workflows are the same as identified in the ArcMap ArcGIS Enterprise architecture. <br style="clear: both" />

Pro VDI ArcGIS Enterprise design requirements and network suitability
Figure A1-9b.26 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with ArcGIS Pro VDI workflows.

Project workflows for each user location are selected in column B. Peak concurrent workflow loads are identified in terms of users (Column C) or throughput (Column D) for each business workflow at each location.

LAN,WAN, and Internet Web client workflows are the same as discussed in the ArcMap deployment.

ArcGIS Desktop ArcMap workflows will be replaced with ArcGIS Pro.
 * DeskProEdit workflow replaces the DeskArcMapEdit workflow for LAN clients.
 * CitrixProEdit workflow replaces the CitrixArcMapEdit workflows for remote editor clients.
 * CitrixProView workflow replaces the CitrixArcMapView workflows for remote viewer clients.

Network Bandwidth for each network location is entered in column H. GREY network rows represent central Data Center gateways and the GREEN network rows represent the remote site gateways. While the project workflows are configured and the network bandwidth is entered, the CPT completes the network suitability analysis. Bandwidth utilization is shown in column I for each network gateway. <br style="clear: both" />

Generic ArcGIS Pro VDI host platform configuration
Figure A1-9b.27 shows CPT Design tab functions and process for configuring the ArcGIS Pro VDI host platform.

The total number of ArcGIS Pro virtual desktops supported on the VDI host tier are limited by the capacity of the host platform NVIDIA graphics card. Following steps can be used to identify the proper VDI host platform configuration.
 * Select the Citrix VDI host platform (Column B). Esri recommends the Xeon Gold 6132 28 core (2 chip) 2600 MHz platform for hosting ArcGIS Pro VDI desktops.  Actual platform solution will depend on business workflow requirements (number of concurrent ArcGIS Pro background geoprocessing jobs will determine required number of server platform core).
 * Enter the total number of concurrent ArcGIS Pro virtual desktops in the WTS tier fixed nodes (Cell H76). Total assigned VDI sessions can be identified in Column A (Cell A74).
 * After entering WTS tier fixed nodes, CPT will calculate required number of host VDI server nodes (WTS tier Column AF). Total of 4 host Citrix platform nodes would be required to support 80 concurrent ArcGIS Pro remote desktop sessions. A minimum configuration would require 4 host VDI platform nodes (NVIDIA Tesla P40 graphics license supports up to 25 concurrent virtual desktops per host server node).
 * Enter the required total platform nodes (4) in the Citrix VDI host fixed nodes cell (Column H). Citrix tier will then estimate the peak number of supported background batch jobs (Column AF).

The Xeon Gold 6132 28 core (2 chip) 2600 MHz platform supports the Esri recommended ArcGIS Pro VDI hardware solution. <br style="clear: both" />

Generic Pro VDI with ArcGIS Enterprise virtual platform solution (Workflow Separation)
Figure A1-9b.28 shows CPT Design tab general ArcGIS Enterprise virtual server platform solution with ArcGIS Pro workflows applying workflow separation best practices. The VDI host is supporting 60 concurrent ArcGIS Pro geoprocessing services.

The ArcGIS Pro VDI architecture supports remote ArcMap and ArcGIS Pro client desktops on the CitrixPro VDI host machine. Each VDI session includes a full desktop operating system.

The Xeon Gold 6132 28 core (2 chip) 2600 MHz platforms provides the recommended VDI hardware solution, while the Xeon Gold 6128 12 core (2 chip) 3400 MHz platforms provide the lowest cost Server tier solution. Pricing is based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $284,231 (Cell Y94), higher cost due to the high capacity VDI host platform tier. An additional NVIDIA Graphic cost of $80,000 is required to support Citrix host platform solution (Column AF). <br style="clear: both" />

Design requirements and network suitability for remote Pro workstation Enterprise Geodatabase connections
Figure A1-9b.29 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with ArcGIS Pro desktop workflows with Enterprise Geodatabase connections.

Project workflows for each user location are selected in column B. Peak concurrent workflow loads are identified in terms of users (Column C) or throughput (Column D) for each business workflow at each location. For this solution, the remote ArcGIS Pro Citrix workflows are replaced with ArcGIS Pro workstation workflows.

WAN remote ArcGIS Desktop clients (total of 100 desktop clients)
 * CitrixProEdit is replaced with DeskProEdit 100% dynamic workflow.
 * CitrixProView is replace with DeskProView 100% dynamic workflow.

WAN remote server clients (remote internal web services) and Internet public server client (remote Internet web services) are the same as discussed in the ArcMap deployment.

Network Bandwidth for each network location is entered in column H. GREY network rows represent central Data Center gateways and the GREEN network rows represent the remote site gateways. While the project workflows are configured and the network bandwidth is entered, the CPT completes the network suitability analysis.

Bandwidth utilization is shown in column I for each network gateway. ArcGIS Pro 100% dynamic client workflows accessing a remote Enterprise Geodatabase saturate the available network bandwidth. Network bandwidth must be increased to support this design solution. <br style="clear: both" />

ArcGIS Enterprise virtual platform solution (Workflow Separation) for remote Pro workstation Enterprise Geodatabase connections
Figure A1-9b.30 shows CPT Design tab generic ArcGIS Enterprise virtual server platform solution with remote Pro workstation Enterprise Geodatabase connections. The WAN network bandwidth has been upgraded to support the heavier remote ArcGIS Pro direct connect traffic loads.

The final design solution, even after upgrading the network bandwidth, provides degraded remote ArcGIS Pro workflow performance. The additional network bandwidth cost and reduced user productivity would likely make this solution unacceptable.

Traditional system design best practices would recommend deploying ArcGIS Pro on centralized VDI host platform with direct connections to a local Enterprise Geodatabase data source to resolve remote client network and display performance issues.

There are some new architecture options in work to deploy ArcGIS Pro as a Web GIS client, with data connections through Portal Web services rather than direct connections to the Enterprise Geodatabase. ArcGIS Pro is designed as a Web GIS client, supporting new workflows that maintain and view data sources through Web GIS Portal feature service connections (registered map and feature services) rather than direct connections to the data management systems. <br style="clear: both" />

Design requirements and network suitability for remote Pro workstation Web GIS Portal feature service connections
Figure A1-9b.31 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with ArcGIS Pro Web GIS (Portal feature service) workflows.

Project workflows for each user location are selected in column B. Peak concurrent workflow loads are identified in terms of users (Column C) or throughput (Column D) for each business workflow at each location. For this solution, the remote ArcGIS Pro desktop workflows are replaced with ArcGIS Pro Web GIS (Portal feature service) workflows.

WAN remote ArcGIS Desktop clients (total of 100 desktop clients)
 * DeskProEdit is replace with DeskPro$FSvcEdit20% dynamic workflow (client feature cache enabled along with branch versioning).
 * DeskProView is replace with DeskPro$FSvcView20% dynamic workflow (client feature cache enabled)

WAN remote server clients (remote internal web services) and Internet public server client (remote Internet web services) are the same as discussed in the ArcMap deployment.

Network Bandwidth for each network location is entered in column H. GREY network rows represent central Data Center gateways and the GREEN network rows represent the remote site gateways. While the project workflows are configured and the network bandwidth is entered, the CPT completes the network suitability analysis. Bandwidth utilization is shown in column I for each network gateway. <br style="clear: both" />

ArcGIS Enterprise virtual platform solution (Workflow Separation) for remote Pro workstation Web GIS Portal feature service connections
Figure A1-9b.32 shows CPT Design tab general ArcGIS Enterprise virtual server platform solution with remote Pro workstation Web GIS Portal feature service connections.

The Xeon Gold 6128 12 core (2 chip) 3400 MHz platforms provide the lowest cost Server tier solution. Pricing is based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $74,028 (Cell Y94), significantly less cost than the VDI solution. Network bandwidth requirements are also reduced due to benefits provided by local client feature caching.

The remote ArcGIS Desktop Web GIS client architecture provides many benefits over traditional direct connect architecture patterns. ArcGIS technology is changing in many areas to promote more effective distributed operations.
 * Enterprise Geodatabase versioning (traditional or new ArcGIS 10.6+ branch versioning).
 * ArcGIS Desktop feature cache.
 * Portal Web map based services architecture.
 * Enterprise GeoDatabase replication services.
 * Portal collaboration and sharing services.
 * Expanding ArcGIS Server roles for server based analysis and geoprocessing.

Selecting the right ArcGIS Desktop remote client architecture solution depends heavily on your business requirements and supporting workflows. <br style="clear: both" />

Detailed Pro ArcGIS Enterprise platform technical architecture
This demonstration shows a complete system architecture design analysis using a detailed architecture configuration. The detailed CPT Design configurations are much more complex than the generic configurations, while both approaches can provide the same platform solution.


 * Detailed Pro ArcGIS Enterprise platform technical architecture demonstration

"Best practice: A generic architecture CPT Design analysis can provide the correct platform solution when the total number of machines per tier are properly identified"

CPT Design ArcGIS Enterprise server licensing roles
The following sections will demonstrate CPT Design configurations for the ArcGIS Enterprise server roles.
 * ArcGIS Enterprise server role platform technical architecture
 * ArcGIS Enterprise server role Project Workflows
 * ArcGIS Enterprise server role requirements
 * ArcGIS Enterprise server role Selected Platform tier configuration
 * ArcGIS Enterprise server role Software Configuration
 * ArcGIS Enterprise server role Platform Solution

Business Requirements to include additional ArcGIS Enterprise server roles
Figure A1-9b.33 shows GIS business requirements for expanding ArcGIS Enterprise to include the ArcGIS Server roles.

The following additional business needs were identified for the GIS Server role deployment.

ArcGIS Server role requirements
 * Business Analysis server. 20 concurrent users.
 * Image Raster Analytics server. 4 max geoprocessing instances.
 * Geoanalytics server. 4 max geoprocessing instances.
 * GeoEvent Server. 1,000 events per second.

ArcGIS Enterprise design will be expanded to include the above GIS Server role business requirements. <br style="clear: both" />

CPT ArcGIS Enterprise server role platform technical architecture
Figure A1-9b.34 shows the ArcGIS Enterprise server role platform technical architecture used to demonstrate the CPT Design ArcGIS Enterprise server role configurations.

The ArcGIS server role technical architecture is supported by the following components:


 * Standard Generic server tier architecture
 * Web Server tier. Host internal and public Web and Portal server machines - total of 8 virtual machines.
 * GIS Server tier. Host internal and public ArcGIS Server machines and transnational Server Roles (Business Analyst and dynamic Image Services) - total of 12 virtual machines.
 * DBMS tier. Host internal and public Database and Data Store machines (Spatiotemporal Big Data Store will require three machines for high availability) - total of 11 virtual machines.


 * Special GIS Server licensing roles will be configured on separate dedicated virtual server tier.
 * ArcGIS Image Server (raster analytics). ArcGIS Image Server supports a variety of raster analytics services.
 * ArcGIS GeoAnalytics Server. ArcGIS GeoAnalytics Server supports a variety of geoprocessing services.
 * ArcGIS GeoEvent Server. ArcGIS GeoEvent Server supports a variety of real time ingestion and streaming services.

Geoprocessing output from special GIS Server licensing roles is stored in the ArcGIS Data Stores and appear as a reference layer as Portal user content. Content layer can be shared through Portal hosted services. <br style="clear: both" />

CPT ArcGIS Enterprise server role Project Workflows
Figure A1-9b.35 shows the CPT Project Workflows used to demonstrate the CPT Design ArcGIS Server role configurations.

"Best practice. GIS and Image dynamic services registered with Portal for ArcGIS will generate a light Portal load for each transaction." "Best practice. Geoprocessing service instances are batch processes with Min Think Time = 0 (Cell L9)." "Best practice. A single transaction delivers output to portal content and appropriate ArcGIS Data Store following the geoprocessing job, and the resulting Portal, SOC, and Data Store loads are negligible and can be ignored for planning purposes."
 * ArcGIS Enterprise server role Project Workflows
 * BusAnal. The ArcGIS Enterprise GIS Server supports a variety of web mapping services and feature services.
 * WebImage. The ArcGIS Enterprise Image Server supports a variety of dynamic image services.
 * RasterAnalysis. The ArcGIS Enterprise Image Server also supports a variety of raster analytics geoprocessing services.
 * GeoAnalytics. The ArcGIS Enterprise GeoAnalytics Server supports a variety of geoprocessing services.
 * GeoEvent. The ArcGIS Enterprise GeoEvent Server supports a variety of GeoEvent ingestion services. Each GeoEvent client transmits 60 events per minute (Cell M11), Min Think Time = 0.01 (Cell L11).

"Warning. GeoEvent streaming services traffic can cause network contention.''" <br style="clear: both" />
 * GeoEvent Server supports two different service capabilities.
 * GeoEvent Ingestion. Event inbound traffic and processing loads on GeoEvent Server.
 * GeoEvent streaming services. Event traffic sent to client displays.

CPT Design ArcGIS Enterprise server role Requirements Analysis
Figure A1-9b.36 shows the CPT Design peak concurrent Requirements Analysis used to demonstrate the CPT Design ArcGIS Enterprise server role configurations.

The ArcGIS Enterprise server role sites are deployed in the data center with the following peak loads.

"Best practice. Raster and GeoAnalytics geoprocessing max instance = number of platform core for optimum server utilization." <br style="clear: both" />
 * LAN Local Clients
 * BusAnal. GIS Server role (heavy workflow) with 20 peak concurrent users.
 * WebImage. Image Server role with 10 local and 6 remote concurrent users accessing image services.
 * RasterAnalysis. Image Server role with 4 concurrent batch instances supporting raster analysis geoprocessing (plan to deploy two (2) 2-core virtual servers).
 * GeoAnalytics. GeoAnalytics Server role with 4 concurrent batch instances supporting GeoAnalytics geoprocessing (plan to deploy two (2) 2-core virtual servers).
 * Internet Public clients
 * GeoEvent. GeoEvent Server role ingesting 60,000 events per minute (cell F28) from 1000 concurrent vehicles (Internet clients) each transmitting at 60 events per minute. Total Data Center Internet network traffic = 58.1 Mbps (Cell G14).  Data Center Internet bandwidth of 90 Mbps should be adequate to support workflow performance.

CPT Design ArcGIS Enterprise server role Selected Platform tier configuration
Figure A1-9b.38 shows the CPT Design Selected Platform tier configuration used to demonstrate the CPT Design ArcGIS Enterprise server role configurations.

"Workflow separation best practice: The optimum strategy is to configure a dedicated ArcGIS Server site for each ArcGIS Enterprise licensed server role."


 * Standard ArcGIS Server license roles can be configured on generic platform tier.
 * WebPortal tier. Web server and Portal for ArcGIS Server.
 * GIS tier. Internal and external GIS Server, internal and external Hosted GIS Server, Business Analyst server, and Image Server (image services).
 * Database tier. Production Geodatabase, Publication Geodatabase, internal and public Relational Data Store, and Spatiotemporal Data Store.

"Best practice: CPT Calculator can be used to validate capacity of individual ArcGIS Server license roles deployed on a generic platform tier."

<br style="clear: both" />
 * Special ArcGIS Server license roles should be configured on dedicated platform tier.
 * GeoEvent. ArcGIS GeoEvent Server site, configured as three 2-core virtual server nodes.
 * GeoAnal. ArcGIS GeoAnalytics Server site, configured as two 2-core virtual server nodes.
 * ImageRA. ArcGIS Image Server site for raster analytics, configured as two 2-core virtual server nodes.

CPT Design ArcGIS Enterprise server role Software Configuration
Figure A1-9b.39 shows the CPT Design Software Configuration used to demonstrate the CPT Design ArcGIS Enterprise server role configurations.


 * Generic software configuration is provided on Row 5.
 * Client=Client
 * Web=Web
 * Portal=Web
 * SOC=GIS
 * DBMS=DBMS

<br style="clear: both" />
 * Special software configuration items.
 * ImageSvc. MDS=FGDB, Data Source=TIFF_uncompressed.
 * RasterAnalysis. SOC=ImageRA, MDS=FGDB, Data Source=Tiff_uncompressed.
 * GeoAnalytics. SOC=GeoAnal
 * GeoEvent. SOC=GeoEvent

CPT Design ArcGIS Enterprise Server Role Platform Solution
Figure A1-9b.40 shows the CPT Design Platform Solution used to demonstrate the CPT Design ArcGIS Enterprise Server Role configuration.

Once the CPT Design tab configuration is complete, CPT generates the selected Platform Solution. Server is selected as the Host Platform tier for all the virtual server tier (Column I). The virtual server tier platform selections (Column B) can be soft linked to the Server host platform selection (Host and Virtual tier platform selections must be the same).

For high availability and workflow separate best practices, include the total number of nodes for the Web, GIS, and DBMS virtual tier.
 * Web tier includes eight 2-core nodes. Supports internal and external Web and Portal servers in a high available configuration.
 * GIS tier includes 12 2-core nodes. Supports internal and external federated GIS Server (system of record) and Portal hosted GIS servers each in high available configurations.  Also supports Image server(for image services) and Business Analysis server roles in high available configurations.
 * DBMS tier includes 11 2-core nodes. Includes Production and Publishing geodatabase, internal and external Relational data store, and Spatiotemporal big data store.  Each data server site configured with failover (HA configuration), with 3 machines for the Spatiotemporal data store HA configuration.

Final Platform Selection can be made to minimize total hardware cost (Cell Y87). <br style="clear: both" />
 * Three (3) Xeon Gold 5115 20 core (2 chip) 2400 MHz virtual server host platforms (Cell B90), each with 255 GB RAM (Cell C89), provide the optimum platform solution for this CPT Design.

Concluding Remarks
There are several factors that should be considered when establishing your enterprise data center architecture. Many of these factors are determined based on business needs and standard IT operating procedures.

The primary focus for Esri system architecture design services is to identify hardware and infrastructure resources that satisfy user productivity needs during peak GIS system loads. This effort focuses on the primary production hardware and available network infrastructure bandwidth required to support GIS operations.



Other factors contribute to the final system configuration. These factors include provisions for system maintenance, updates, configuration control, software licensing, and security. System requirements often include hardware provisions for application development, system test, production staging, background processing (i.e. map cache maintenance and replication services), system backup, and security. System migration will normally include continued support for legacy operations while introducing new technology, often on separate hardware environments.

The CPT Design tab provides a framework for modeling enterprise operations. Figure A-9b.41 provides an overview of the adaptive CPT Design platform module.
 * Up to 10 unique platform tier available for software assignment
 * Each platform tier can scale to any required number of nodes (platforms)
 * A different platform technology can be selected for each tier.
 * Platform rollover setting automates platform sizing (fixed node option also available)
 * Selected hardware can be native (physical server) or Virtual Server platform tier
 * Platform names can be assigned to personalize the IT environment
 * Software components can be installed on any platform tier
 * Three additional Host platform tier are included at the bottom for Virtual Server platform assignment.

An Enterprise GIS design includes business, application, data, and technical architecture requirements. The Capacity Planning Tool provides a framework that models enterprise GIS performance and scalability, integrating the full range of Enterprise system design requirements into a solution that represents your GIS production needs.

CPT Capacity Planning videos
Chapter 9 Capacity Planning Video will show how to configure the CPT to represent your data center platform architecture selection.

Page Footer Specific license terms for this content System Design Strategies 26th edition - An Esri ® Technical Reference Document • 2009 (final PDF release)