GIS Product Architecture (CPT Design Demos) 40th Edition

Arc17CapacityPlanning0701 release

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

The CPT Design system design analysis can be completed using a generic or detailed architecture solution.
 * Generic architecture. The generic architecture CPT analysis assigns business workflow processing loads to four generic platform tier (Terminal, 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 three sections.
 * Generic Enterprise Design with ArcGIS Desktop (ArcMap) and ArcGIS Enterprise workflows. Most organizations today use ArcMap for their professional ArcGIS Desktop workflows.
 * Generic Enterprise Design with ArcGIS Pro and ArcGIS Enterprise workflows. ArcGIS Pro is replacing ArcMap as the primary professional ArcGIS Desktop application over the next couple of years.
 * Detailed Enterprise Design with ArcGIS Pro and ArcGIS Enterprise workflows. 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.

"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"

Generic ArcMap ArcGIS Enterprise platform technical architecture
Figure A1-9.21 shows the 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." 

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

ArcMap workstation workflows (Local ArcMap clients)
 * DeskMapFile. ArcGIS Desktop ArcMap workstation clients with file data source.
 * DeskMapEGDB. ArcGIS Desktop ArcMap workstation clients with Enterprise Geodatabase data source.
 * DeskMapTabDB. ArcGIS Desktop ArcMap workstation clients with tabular DBMS data source.

ArcGIS Pro workstation workflows (local and remote ArcGIS Pro clients)
 * DeskProFSvc20%. ArcGIS Pro accessing a Portal for ArcGIS hosted feature service with relational data store data source.  ArcGIS Desktop workstation clients are licensed for ArcGIS Pro.  ArcGIS Pro is an optimum professional client choice for working with Portal feature services.

"Warning: ArcGIS Pro applications are not supported by traditional ArcMap terminal service host platform configurations."

ArcMap Citrix workflows (ArcMap deployed on host terminal server tier)
 * CitrixMapFile. Remote ArcGIS Desktop ArcMap clients with central file data source.
 * CitrixMapEGDB. Remote ArcGIS Desktop ArcMap clients with central Enterprise Geodatabase data source.
 * CitrixMapTabDB. Remote ArcGIS Desktop ArcMap clients with central tabular DBMS data source.

ArcGIS Server workflows (Web map services) 
 * AGSFile. ArcGIS Server map services with file data source.
 * AGSPGDB. ArcGIS Server map services with Enterprise Geodatabase data source registered with Portal for ArcGIS.
 * AGSOps. ArcGIS Server map services with 40% dynamic business layers with Enterprise Geodatabase data source over basemap tile cache.
 * AGSFSvc. ArcGIS Server feature services with 20% dynamic feature layers with relational data store data source over basemap tile cache.
 * AGSImage_ ArcGIS Server image services with imagery data source.

ArcMap ArcGIS Enterprise design requirements and network suitability analysis
Figure A1-9.23 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with legacy ArcMap workflows. The design requirements analysis includes sections for local clients over the LAN, remote desktop clients and remote web services clients over the WAN, and public web services shared to internet clients.

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 desktop clients (total of 100 desktop clients)
 * DeskMapFile. 15 users. (supports local ArcMap clients)
 * DeskMapEGDB. 50 users. (supports local ArcMap clients)
 * DeskMapTabDB. 10 clients. (supports local ArcMap clients)
 * DeskProFSvc20%. 25 clients. (supports local ArcMap clients)

WAN remote desktop clients (total of 100 desktop clients)
 * CitrixMapFile. 15 users (supports remote ArcMap clients)
 * CitrixMapEGDB. 50 users. (supports remote ArcMap clients)
 * CitrixMapTabDB. 10 clients. (supports remote ArcMap clients)
 * DeskProFSvc20%. 25 clients (ArcGIS Pro not supported on terminal service tier)

WAN remote server clients (remote internal web services)
 * AGSFile. 10 users, 3,600 transactions per hour (TPH) (internal Web services)
 * AGSPGDB. 20 users, 7,200 TPH (internal map services registered with Portal for ArcGIS)
 * AGSOps. 50 users, 18,000 TPH (Internal web services)
 * AGSFSvc. 20 users, 7,200 TPH (supports internal remote edit operations)
 * AGSImage. 50 users, 18,000 TPH (supports internal imagery services)

Internet public server clients (remote internet web services)
 * AGSOps. 300,000 TPH (supports public web services)
 * AGSFSvc. 100 users, 36,000 TPH (supports external remote edit operations)

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.

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

Generic ArcMap ArcGIS Enterprise Platform Configuration
Figure A1-9.24 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 ArcMap ArcGIS Enterprise Software Configuration
Figure A1-9.25 shows CPT Design tab general project workflow software configuration to support ArcGIS Enterprise business requirements with legacy ArcMap workflows.

Proper Data Source must be selected for each workflow (Column R)
 * 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.

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 platform assignments can be identified in row 5 for all workflow software components. 
 * 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).  For imagery workflows, the selection in this column 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 O21) when the mosaic dataset it is not located on the client application.
 * DBMS = DBMS. All database loads are assigned to the DBMS tier.

Generic 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 ArcMap App Sessions ArcGIS Enterprise physical platform solution
Figure A1-9.26 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 E5-2637v4 4 core (1 chip) 3500 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 = 4 platform nodes.
 * Web tier = 2 platform nodes.
 * GIS tier = 3 platform nodes.
 * DBMS tier = 1 platform node with failover server for DBMS tier.

A total of 11 Xeon E5-2637v4 4 core (1 chip) 3500 MHz servers are required to support the minimum physical platform solution. Estimated hardware cost is $102,030 (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 ArcMap App Sessions ArcGIS Enterprise physical platform solution (Workflow Separation)
Figure A1-9.27 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-9.xx.

ArcMap Platform Architecture diagram
 * Terminal server (WTS) tier. Host remote ArcGIS Desktop (ArcMap) terminal clients (single server environment).
 * Web Server tier. Host internal and public Web and Portal server machines (4 server environments).
 * GIS Server tier. Host internal and public ArcGIS Server machines and Server Roles (5 server environments).
 * DBMS tier. Host internal and public Database and Data Store machines (5 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-9.27 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 = 11 nodes, minimum of two for each server environment. The public AGSOps web services (300,000 TPH) will require 3 server nodes to satisfy capacity requirements.
 * DBMS tier = 10 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 33 Xeon E5-2637v4 4 core (1 chip) 3500 MHz servers are required to support the final workflow separation platform solution. Estimated hardware cost is $302,706 (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 ArcMap App Sessions ArcGIS Enterprise virtual server platform solution
Figure A1-9.28 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 (CitrixMap and Server virtual server 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
 * CitrixMap 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 (CitrixMap 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 = Four 4-core virtual server platform nodes assigned to the CitrixMap virtual host.
 * Web tier = Two 2-core virtual server platform nodes assigned to the Server virtual host.
 * GIS tier = four 4-tier virtual server platform nodes assigned to the Server virtual host.
 * DBMS tier = One 4-tier 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.
 * CitrixMap tier. 2x Xeon E5-2667v4 16 core (2 chip) 3200 MHz servers, each with 228 GB RAM (Cell C95).
 * Server tier. 3x Xeon E5-2667v4 16 core (2 chip) 3200 MHz servers, each with 109 GB RAM (Cell C98).

The Xeon E5-2667v4 16 core (2 chip) 3200 MHz platform provided the lowest cost hardware solution, based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $149,192 (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 ArcMap App Sessions with ArcGIS Enterprise virtual server platform solution (Workflow Separation)
Figure A1-9.29 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 = 8 nodes, two for each server environment.
 * GIS tier = 11 nodes, minimum of two for each server environment. The public AGSOps web services (300,000 TPH) will require 3 server nodes to satisfy capacity requirements.
 * DBMS tier = 10 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.
 * CitrixMap tier. 2x Xeon E5-2667v4 16 core (2 chip) 3200 MHz servers, each with 228 GB RAM (Cell C95).
 * Server tier. 3x Xeon E5-2667v4 16 core (2 chip) 3200 MHz servers, each with 235 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 E5-2667v4 16 core (2 chip) 3200 MHz platforms again provided the lowest cost hardware solution, based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $159,620 (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 ArcMap Virtual Desktop Infrastructure (VDI) with ArcGIS Enterprise virtual server platform solution (Workflow Separation)
Figure A1-9.30 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.
 * CitrixMap tier. 2x Xeon E5-2689v4 20 core (2 chip) 3100 MHz servers, each with 1145 GB RAM (Cell C95).
 * Server tier. 3x Xeon E5-2667v4 16 core (2 chip) 3200 MHz servers, each with 235 GB RAM (Cell C98).

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

The Xeon E5-2689v4 20 core (2 chip) 3100 MHz platforms provide the optimum VDI hardware solution, while the Xeon E5-2667v4 16 core (2 chip) 3200 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 $193,988 (Cell Y93), slightly higher cost due to additional loads on the VDI tier. 

Generic Pro ArcGIS Enterprise platform technical architecture
Figure A1-9.31 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 section will configure the CPT Design to complete a generic ArcGIS Enterprise capacity planning analysis supporting both remote ArcMap and ArcGIS Pro clients.

The generic capacity planning analysis will configure the platform architecture on four platform tier.
 * 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.

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

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

ArcGIS Pro workstation workflows (Local ArcMap clients)
 * DeskProFile. ArcGIS Pro workstation clients with file data source.
 * DeskProEGDB. ArcGIS Pro workstation clients with Enterprise Geodatabase data source.
 * DeskProTabDB. ArcGIS Pro workstation clients with tabular DBMS data source.
 * DeskProFSvc20%. ArcGIS Pro workstation clients accessing a Portal for ArcGIS hosted feature service with relational data store data source.

ArcMap Citrix workflows (ArcMap deployed on host terminal server tier)
 * CitrixProFile. Remote ArcGIS Pro clients with central file data source.
 * CitrixProEGDB. Remote ArcGIS Pro clients with central Enterprise Geodatabase data source.
 * CitrixProTabDB. Remote ArcGIS Pro clients with central tabular DBMS data source.
 * CitrixProFSvc20%. Remote ArcGIS Pro clients accessing a Portal for ArcGIS hosted feature service with relational data store data source.
 * CitrixProBatch. Remote ArcGIS Pro geoprocessing jobs executed on the VDI host platform.

ArcGIS Server workflows are the same as identified in the ArcMap architecture. 

Pro ArcGIS Enterprise design requirements and network suitability
Figure A1-9.33 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with ArcGIS Pro desktop workflows. The design requirements analysis includes sections for local clients over the LAN, remote desktop clients and remote web services clients over the WAN, and public web services shared to internet clients.

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 desktop clients (total of 100 desktop clients)
 * DeskProFile. 15 users. (supports local ArcMap clients)
 * DeskProEGDB. 50 users. (supports local ArcMap clients)
 * DeskProTabDB. 10 clients. (supports local ArcMap clients)
 * DeskProFSvc20%. 25 clients. (supports local ArcMap clients)

WAN remote desktop clients (total of 100 desktop clients)
 * CitrixProFile. 15 users (supports remote ArcGIS Pro clients)
 * CitrixProEGDB. 50 users. (supports remote ArcGIS Pro clients)
 * CitrixProTabDB. 10 clients. (supports remote ArcGIS Pro clients)
 * CitrixProFSvc20%. 25 clients (supports remote ArcGIS Pro clients)

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. 

Generic Pro ArcGIS Enterprise platform solutions
The generic software configuration requirements are the same as discussed for ArcMap.

This section will show how to configure the ArcGIS Pro host VDI platform, and then shares the Generic Pro VDI ArcGIS Enterprise virtual platform solution with Workflow Separation.

Generic Pro VDI host platform configuration
Figure A1-9.34 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 CitrixPro VDI host platform (Column B). Esri recommends the Xeon E5-2690v4 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 5 host VDI platform nodes would be required to support 100 concurrent ArcGIS Pro remote VDI sessions in a high availability mode. A minimum configuration would require 4 host VDI platform nodes (NVIDIA Tesla M60 graphics license supports up to 25 concurrent virtual desktops per host server node).
 * Enter the required total platform nodes (4) in the CitrixPro VDI host fixed nodes cell (Column H). CitrixPro tier will then estimate the peak number of supported background batch jobs (Column AF).

The Xeon E5-2690v4 28 core (2 chip) 2600 MHz platforms provides the optimum VDI hardware solution, while the Xeon E5-2667v4 16 core (2 chip) 3200 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 $298,636 (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 CitrixPro host platform solution (Column AF). 

Generic Pro VDI with ArcGIS Enterprise virtual platform solution (Workflow Separation)
Figure A1-9.35 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 47 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 E5-2690v4 28 core (2 chip) 2600 MHz platforms provides the optimum VDI hardware solution, while the Xeon E5-2667v4 16 core (2 chip) 3200 MHz platforms provides the lowest cost Server tier solution. Pricing is based on estimated hardware costs identified in the CPT HWPricing tab. Estimated hardware cost is $298,636 (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 CitrixPro host platform solution (Column AF). 

Detailed Pro VDI ArcGIS Enterprise platform technical architecture
This section shows the detailed configuration approach for completing the CPT Design solution. Each platform environment is configured on its own platform tier, and the workflow software components are assigned to their specific platform tier to complete the design analysis. The detailed design approach is more accurate, although the generic approach gives the same platform solution with much less effort and can be used to support much more complex design solutions.

Figure A1-9.36 shows the ArcGIS Enterprise platform architecture with remote 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 section will configure the CPT Design to complete a detailed ArcGIS Enterprise capacity planning analysis supporting the ArcGIS Pro clients. The ArcGIS Pro solution will also support ArcMap clients (ArcMap clients consume less server resources than ArcGIS Pro clients).

The detailed capacity planning analysis will configure the platform architecture with each unique server component on a separate platform tier. 
 * Terminal server tier will support the remote ArcGIS Pro terminal clients.
 * Web Server components will include the internal and public Web and Portal server machines each on separate platform tier.
 * GIS Server components will include the internal, internal hosted, public, and public hosted ArcGIS Server machines and the Image Server each on separate platform tier.
 * DBMS components will include the tabular DBMS, Production Geodatabase, Publishing Geodatabase, internal and public Relational Data Store each on separate platform tier.

Detailed Pro VDI ArcGIS Enterprise platform tier configuration
Detailed platform tier configuration is divided into four sections for display purposes.
 * Detailed Pro VDI ArcGIS Enterprise Web platform tier configuration
 * Detailed ArcGIS Enterprise GIS platform tier configuration
 * Detailed ArcGIS Enterprise DBMS platform tier configuration
 * Detailed ArcGIS Enterprise virtual server host platform tier configuration

Detailed Pro VDI ArcGIS Enterprise Web platform tier configuration
Figure A1-9.37 shows CPT Design tab detailed configuration for the ArcGIS Pro VDI platform tier and the four (4) Web platform tier.

Detailed Pro VDI and Web Platform tier configuration <br style="clear: both" />
 * WTS. Provides VDI platform tier for remote ArcGIS Pro and ArcMap clients.
 * WebIn. Provides platform tier for internal Web virtual servers.
 * WebPub. Provides platform tier public Web virtual servers.
 * PortalIn. Provides platform tier for internal Portal for ArcGIS virtual servers.
 * PortalPub. Provides platform tier for public Portal for ArcGIS virtual servers.

Detailed ArcGIS Enterprise GIS Server platform tier configuration
Figure A1-9.38 shows CPT Design tab detailed configuration for the five (5) GIS platform tier.

Detailed GIS Platform tier configuration <br style="clear: both" />
 * GISIn. Provides platform tier for the internal GIS Server site.
 * GISPub. Provides platform tier for the public GIS Server site.
 * GISHostIn. Provides platform tier for the internal Portal Hosted GIS Server site.
 * GISHostPub. Provides platform tier for the public Portal Hosted GIS Server site.
 * Image. Provides platform tier for the GIS Image Server site.

Detailed ArcGIS Enterprise database platform tier configuration
Figure A1-9.39 shows CPT Design tab detailed configuration for the five (5) database platform tier.

Detailed database Platform tier configuration <br style="clear: both" />
 * TabDB. Provides platform tier for the internal tabular DBMS servers.
 * ProdGDB. Provides platform tier for the Production Geodatabase servers.
 * PubGDB. Provides platform tier for the Publication Geodatabase servers.
 * RelDSin. Provides platform tier for the internal Relational Data Store servers.
 * RelDSout. Provides platform tier for the public Relational Data Store servers.

Detailed Pro ArcGIS Enterprise Virtual Server Host platform tier configuration
Figure A1-9.40 shows CPT Design tab detailed configuration for the two Virtual Server Host platform tier.

Detailed Virtual Server Host Platform tier configuration
 * CitrixPro. Provides host platform tier for the ArcGIS Pro VDI platform tier.
 * Server. Provides host platform tier for the four (4) Web, five (5) GIS, and five (5) DBMS virtual server platform tier.

"Warning: Virtual Server Host platform tier hardware selection must match the platform selection for each assigned virtual server platform tier."

"Best practice: Use Excel to soft link Virtual Server Host Platform selection to the assigned Virtual Server tier platform selections (Column B)" <br style="clear: both" />

Detailed Pro ArcGIS Enterprise Software Configuration
Figure A1-9.41 shows CPT Design tab detailed project workflow software configuration to support ArcGIS Enterprise business requirements with ArcGIS Pro and ArcGIS Server workflows.

Proper Data Source must be selected for each workflow (Column R)
 * Small File GDB. Appropriate selection for DeskProFile, CitrixProFile, and AGSFile workflows.
 * TIFF uncompressed. Appropriate selection for AGSImage workflow.
 * DB_DBMS. Appropriate selection for all workflows with DBMS data source.

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.

Default selections are assigned in ROW 5 for each software component.
 * Client component = Client. Client load for all project workflows.
 * Citrix component = WTS. Remote app or desktop loads on WTS platform tier.
 * Web component = WebIn. Internal Web server loads are the most common.
 * Portal component = PortalIn. Internal Portal for ArcGIS loads are the most common.
 * SOC component = GISIn. Internal ArcGIS Server SOC loads are the most common.
 * DS/MDS = Direct Connect. Direct Connect assigns the SDE processing load to the client application (only supported option).  For imagery workflows, the selection in this column 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 O22) when the mosaic dataset it is not located on the client application.
 * DBMS = PubGDB. Majority of user workflows access the Publication Geodatabase.

"Best practice: Each workflow software assignment must be reviewed to ensure proper platform tier assignment"

LAN local client workflows
 * DeskProEGDB DBMS software assigned to ProdGDB.
 * DeskProTabDB DBMS software assigned to TabDB.
 * DeskProFSvc20% SOC software assigned to GISHostIn and DBMS software assigned to RelDSin.

WAN Remote Desktop workflows
 * CitrixProEGDB. DBMS software assigned to ProdGDB.
 * CitrixProTabDB. DBMS software assigned to TabDB.
 * CitrixProFSvc20%. SOC software assigned to GISHostIn and DBMS software assigned to RelDSin.

WAN Remote Server workflows
 * AGSFSvc. SOC software assigned to GISHostIn and DBMS software assigned to RelDSin.
 * AGSImage. SOC software assigned to Image and MDS assigned to FGDB.

Internet Services
 * AGSOps. Web software assigned to WebPub and SOC software assigned to GISPub.
 * AGSFSvc. Web software assigned to WebPub, Portal software assigned to PortalPub, SOC software assigned to GISHostPub, and DBMS software assigned to RelDSout.

Once the CPT Design workflow software loads are assigned to the proper platform tier, Excel completes the system architecture design and generates the detailed platform solution. <br style="clear: both" />

Detailed Pro ArcGIS Enterprise platform solution
Detailed Pro ArcGIS Enterprise platform solution is divided into four sections for display purposes.
 * Detailed Pro VDI ArcGIS Enterprise Web virtual server solution.
 * Detailed ArcGIS Enterprise GIS virtual server solution.
 * Detailed ArcGIS Enterprise DBMS virtual server solution.
 * Detailed ArcGIS Enterprise virtual server host platform tier solution.

Detailed Pro VDI and ArcGIS Enterprise Web virtual server solution
Figure A1-9.42 shows the CPT Design tab detailed platform solution for the ArcGIS Pro VDI platform tier and the four (4) Web platform tier.

ArcGIS Pro Virtual Desktops
 * WTS. 100 virtual ArcGIS Pro desktops assigned to the CitrixPro host platform tier.

Four (4) Web tier with total of 8 virtual server machines <br style="clear: both" />
 * WebIn. Two 2-core virtual server machines assigned to the Server host platform tier.
 * WebPub. Two 2-core virtual server machines assigned to the Server host platform tier.
 * PortalIn. Two 2-core virtual server machines assigned to the Server host platform tier.
 * PortalPub. Two 2-core virtual server machines assigned to the Server host platform tier.

Detailed ArcGIS Enterprise GIS Server platform solution
Figure A1-9.43 shows CPT Design tab detailed platform solution for the five (5) GIS platform tier.

Five (5) GIS tier with total of 13 virtual server machines.
 * GISIn. Two (2)  2-core virtual server machines assigned to the Server host platform tier.
 * GISPub. Five (5) 2-core virtual server machines assigned to the Server host platform tier.
 * GISHostIn. Two (2) 2-core virtual server machines assigned to the Server host platform tier.
 * GISHostPub. Two (2) 2-core virtual server machines assigned to the Server host platform tier.
 * Image. Two (2) 2-core virtual server machines assigned to the Server host platform tier.

"Warning: Capacity requirements for the AGSOps public web services require a total of five (5) 2-core virtual machines." <br style="clear: both" />

Detailed ArcGIS Enterprise database platform solution
Figure A1-9.44 shows CPT Design tab detailed platform solution for the five (5) database platform tier.

Detailed database Platform tier configuration <br style="clear: both" />
 * TabDB. Two (2) 2-core virtual server machines assigned to the Server host platform tier.
 * ProdGDB. Two (2) 2-core virtual server machines assigned to the Server host platform tier.
 * PubGDB. Two (2) 2-core virtual server machines assigned to the Server host platform tier.
 * RelDSin. Two (2) 2-core virtual server machines assigned to the Server host platform tier.
 * RelDSout. Two (2) 2-core virtual server machines assigned to the Server host platform tier.

Detailed Pro ArcGIS Enterprise Virtual Server Host platform solution
Figure A1-9.45 shows CPT Design tab detailed platform solution for the two Virtual Server Host platform tier.

Detailed Virtual Server Host Platform tier configuration
 * CitrixPro. Four (4) Xeon E5-2690v4 28 core (2 chip) 2600 MHz platforms, 553 GB RAM, 77.7 percent average utilization.
 * Server. Three (3) Xeon E5-2667v4 16 core (2 chip) 3200 MHz platforms, 235 GB RAM, 44.5 percent average platform utilization.

The Xeon E5-2690v4 28 core (2 chip) 2600 MHz platforms provides the optimum VDI hardware solution, supporting up to 47 concurrent ArcGIS Pro geoprocessing jobs along with the 100 concurrent virtual desktop workflows. The Xeon E5-2667v4 16 core (2 chip) 3200 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 $298,636 (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 CitrixPro host platform solution (Column AF).


 * Generic system architecture design analysis provides the same platform solution as the detailed system architecture design analysis, with much less effort and attention to detail.

"Best practice: Generic system architecture design analysis can provide the most efficient CPT Design analysis for complex system solutions" <br style="clear: both" />

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

CPT ArcGIS Enterprise server role platform technical architecture
Figure A1-9.46 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:


 * Web Server tier
 * Web Server. Host for Web Servers and Web Adaptors that provide reverse proxy and load balancing to the ArcGIS Server sites.
 * Portal for ArcGIS Server. Provides user role content management and security for ArcGIS Enterprise federated servers.


 * GIS Server tier (Web services)
 * GIS Server. The ArcGIS Enterprise GIS Server supports a variety of dynamic web mapping services and feature services.
 * Hosted GIS Server. The Hosted GIS Server supports dynamic web mapping and feature services published through Portal for ArcGIS.
 * ArcGIS Image Server (Services). The Image Server supports a variety of dynamic web mapping services and feature services.


 * Database tier
 * Publication Geodatabase. Enterprise Geodatabase for sharing system of record data source.
 * Relational Data Store. ArcGIS Data Store for managing relational data source.
 * Tile Cache Data Store. ArcGIS Data Store for managing raster and 3D data source.
 * Spatiotemporal Big Data Store. ArcGIS Data Store for managing temporal relational big data sources.  Minimum configuration requires three machines.


 * Special GIS Server licencing roles.
 * 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 licencing 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-9.47 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 negligable and can be ignored for planning purposes."
 * ArcGIS Enterprise server role Project Workflows
 * AGSSvc. The ArcGIS Enterprise GIS Server supports a variety of web mapping services and feature services.
 * ImageSvc. 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-9.48 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
 * AGSSvc. GIS Server role with 20 peak concurrent users.
 * ImageSvc. Image Server role with 5 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 8 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 E16) from 1000 concurrent vehicles (Internet clients) each transmitting at 60 events per minute. Data center Internet network traffic = 40 Mbps (Cell F14).

CPT Design ArcGIS Enterprise server role Selected Platform tier configuration
Figure A1-9.49 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 licence roles can be configured on generic platform tier.
 * WebPortal tier. Web server and Portal for ArcGIS Server. Four (4) 2-core virtual servers for HA configuration.
 * GIS tier. GIS Server, Hosted GIS Server, and Image Server (image services). Six (6) 2-core virtual servers for HA configuration.
 * Database tier. Enterprise Geodatabase, Relational Data Store, Tile Cache Data Store, and Spatiotemporal Data Store. Nine (9) 2-core virtual servers for HA configuration.

"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, initially configured as one (1) 4-core virtual server node.
 * GeoAnal. ArcGIS GeoAnalytics Server site, configured as two (2) 2-core virtual server nodes.
 * ImageRA. ArcGIS Image Server site for raster analytics, configured as two (2) 2-core virtual server nodes.

CPT Design ArcGIS Enterprise server role Software Configuration
Figure A1-9.50 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=WebPortal
 * Portal=WebPortal
 * SOC=GIS
 * DBMS=DBMS

<br style="clear: both" />
 * Special software configuration items.
 * ImageSvc. MDS=FBDB, 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-9.51 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. Host01 is selected as the Host Platform tier for all of the virtual server tier (Column I). The virtual server tier platform selections (Column B) can be soft linked to the Host01 platform selection (Host and Virtual tier platform selections must be the same).

Final Platform Selection can be made to minimize total hardware cost (Cell Y87). <br style="clear: both" />
 * Three (3) Xeon E5-2643v4 12 core (2 chip) 3400 MHz virtual server host platforms (Cell B90), each with 202 GB RAM (Cell C89), provided 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-7.38 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 7 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) - AP.