GIS Product Architecture - 27th Edition (Spring 2010)
GIS Product Architecture - 27th Edition (Spring 2010)
This section provides a foundation for understanding the software components and platform configuration options available to support distributed GIS operations. Understanding application architecture alternatives and associated configuration strategies provides a foundation for selecting an appropriate distributed GIS design.
Enterprise-level GIS applications support a variety of users throughout an organization, all requiring access to shared spatial and attribute data sources. System hardware and software environments for distributed GIS applications are supported by a multitier client/server or Web services architecture. A simple overview of the various architecture components is provided in Figure 7-1.
Central Data Servers: Shared spatial and tabular database management systems provide central data repositories for shared geographic data. These database management systems can be located on separate data servers or on the same central server platform. Data servers include File Servers, File and ArcSDE Geodatabase Servers, Image servers, and map cache. Additional data sources are available from ArcGIS Online and other Internet data sources.
Application Servers: GIS applications are supported within the distributed configuration by hardware platforms that execute GIS functions. In a centralized solution, Windows Terminal Server and Web application server platforms can host applications and services for a large number of concurrent GIS clients. Windows Terminal Servers host GIS desktop applications on centrally managed server farms allowing remote terminal clients to display and control applications executed on the terminal server platforms. Web application servers support a variety of Web applications and services accessed by standard browser clients or other desktop applications.
Desktop Clients: A variety of desktop clients are used within the GIS environment. Desktop workstations can host local ArcGIS Desktop applications and can connect to Web Services and other desktop applications hosted on Windows Terminal Servers.
- 1 ArcGIS System Software Architecture
- 2 ArcGIS Desktop Client/Server Configurations
- 3 ArcGIS Server Web Services Architecture
- 3.1 ArcGIS Server Component Architecture
- 3.2 Web Platform Configuration Strategies
- 3.3 ArcGIS Server Image Extension Platform Configuration
- 4 Concluding Remarks
ArcGIS System Software Architecture
ArcGIS is an integrated collection of software products for building a complete geographic information system. The ArcGIS family of software products is used to deploy GIS functionality and business logic where needed—in desktops, servers, custom applications, Web services, and mobile devices. The ArcGIS applications are supported by a common set of ArcObjects components developed using Microsoft Component Object Model (COM) programming technology.
GIS is technology used for the creation, management, integration, analysis, display, and dissemination of spatial data. Spatial data includes any information that can be associated with a location on the earth's surface or data that can be associated with a person or place that has a location. Vector data types are used to represent geographic points, lines, and areas (polygons). Other spatial data types include scanned drawings, global positioning system (GPS) coordinates, satellite imagery, survey measurements, photogrammetry, and aerial photography, all of which can be georeferenced to establish proper placement within a geographic map display. GIS technology is currently being used in business, government, public safety, defense and intelligence, health and human services, utilities and transportation, education, and natural resources to manage and understand spatial relationships.
How the spatial data is maintained and published within the organization contributes to the performance and scalability of the system design. The volume of spatial data used to support a GIS has grown exponentially over the last 10 years. Many operational GIS environments maintain and support several terabytes of active GIS data resources with megabytes of data reviewed and processed within a typical user display session. This data must be organized and managed to support effective and efficient GIS operations.
Figure 7-2 provides an outline of the system architecture design configuration strategies supporting current GIS enterprise operations.
ArcGIS Desktop can be deployed on client workstations or hosted by a Windows Terminal Server. Custom ArcGIS Engine applications include the same ArcObjects components supporting the ArcGIS Desktop commercial software and share common configuration strategies. Different configuration alternatives are available to support communications between the client application and the GIS data source.
ArcGIS Server is deployed in a scalable Web application server architecture. The Web server solutions include a software component architecture supporting application development and system performance and scalability. Recommended platform configuration strategies will be provided for both standard and high availability Web solutions.
GIS applications support an open systems architecture. The GIS enterprise architecture combines a variety of closely integrated commercial products to establish a fully supported system solution. All commercial software products must be maintained to support evolving communication interface standards. The importance of selecting well established (popular) software architecture solutions based on standard design practices cannot be overemphasized, since all parts of the distributed configuration are critical and must work together to ensure communication interfaces are properly maintained and supported.
ArcGIS Desktop Client/Server Configurations
ArcGIS Desktop software is supported on Microsoft Windows desktop and terminal server platform environments. ArcGIS Engine is a software development kit providing ArcObjects components for custom desktop application development. Visual Studio is used as the primary programming language for ArcGIS Desktop applications and Python is the primary scripting language.
ArcGIS Desktop is deployed in a client/server architecture. The client applications are tightly coupled with the GIS data source, exchanging hundreds of sequential data requests to complete each user map display transaction. A typical map display is refreshed in less than a second, requiring a very chatty protocol exchange with the connected data source. Communications between the ArcGIS Desktop application and the GIS data source should be supported over stable high-bandwidth local network environments with minimum communication latency. Remote clients should be supported using terminal access to a central Windows Terminal Server located with the GIS data source. ArcGIS Desktop maintenance includes user licensed Web access to worldwide high quality image cache basemaps (Microsoft Virtual Earth - Bing Imagery).
Figure 7-3 provides an overview of the primary software components supporting the ArcGIS Desktop application workflow.
ArcGIS Desktop software supports connection to local file data sources, DBMS data sources through an ArcSDE interface, and published Web data services. Web data services can be integrated with local data in a standard GIS map display.
Capacity Planning Design Software Configuration Module
The Capacity Planning Design includes a software install module for configuring workflow software components on the appropriate server platform environments. The design tab supports an Enterprise data center configuration with up to 10 separate platform tier. Different server platforms can be identified for each platform tier, and each platform tier can expand to include an unlimited number of server nodes (server platforms).
Figure 7-4 provides an overview of the CPT Design software configuration module.
Workflow application software components (Client, WTS Citrix, Web, ADF, SOC, SDE, DBMS) are identified in columns I through P on row 4 of the CPT Design tab. Appropriate application software components are highlighted based on the selected workflow software technology pattern. Dropdown menus are available for each software component on each workflow row, providing a list of the available platform installation selections. A default platform selection for each software column is provided in row 5 (default platform selections on the workflow rows will be installed on the default platform selection in row 5 at the top of each column). The SDE software (column N) default setting in row 4 will implement an ArcSDE direct connect configuration (SDE processing load will be assigned to the application software component). The assigned SDE processing load assignment for each workflow is indentified in column O. Data source selection for each workflow is made in column Q.
ArcSDE Direct Connect is the recommended ArcSDE DBMS configuration for most GIS environments. The following connection will provide more information on the available ArcSDE configuration alternatives.
ArcGIS Desktop Workstation Architecture
Four distributed ArcGIS Desktop client configuration alternatives are identified in Figure 7-5. These configurations include access to a network file data source, direct connect access to an ArcSDE data source, and two ArcSDE connect options to an ArcSDE data source (one connecting through a middle tier ArcGIS Server and the other connecting to ArcSDE installed on the database server).
The ArcGIS Desktop software will provide native file access to GIS data located on local disk. GIS applications can access a remote file data source by using Microsoft's CIFS or similar UNIX NFS. When mounting the remote disk, the remote file would appear as a local file share to the desktop application. Query processing for a file data source is supported by the ArcGIS Desktop application.
The CPT Design software configuration module includes a data source selection for each user workflow. Select file data source (SFG_Small FGDB, LFG_Large FGDB, SSF_Small Shape File, LSF_Large Shape File, or Img_Image) in column Q of the software configuration module for each user workflow. Workflows with a selected file data source do not show DBMS or SDE software service times (cells are black). Appropriate application query loads (Workstation/terminal server desktop application or server SOC) are adjusted based on the file data source selection.
ArcGIS Desktop software provides two options for accessing the SDE geodatabase. The direct connect option includes the ArcSDE executables as part of the direct connect API and will communicate with a database client installed on the same machine. The database client will support network communications to the database server. The ArcSDE connect option supports network communication with a remote geodatabase server (ArcSDE can be supported as an ArcGIS Server geodatabase service or installed on the DBMS server). Query requests are sent to the data server and processed by the supported DBMS software. All data is stored and maintained in the DBMS repository.
The CPT Design software configuration module includes a data source selection for each user workflow. Select SDE DBMS data source when configuring user workflow access to an SDE Geodatabase. When SDE DBMS is selected, workflow will include SDE and DBMS software that must be installed on a selected platform tier. The SDE platform selection determines the connection architecture.
Direct Connect. A default SDE selection is used to designate a Direct Connect architecture. In an ArcSDE Direct Connect configuration, the SDE processing is performed by the SDE Direct Connect API located on the platform hosting the GIS application (Workstation or Terminal Server for ArcGIS Desktop applications, and on the SOC host machines for Server workflows).
Remote Server Connect. Select the platform tier used for the remote server when configuring a three tier ArcSDE connection. SDE and the DBMS client processing loads will be assigned to the selected remote server.
ArcSDE Application Server Connect. Select the DBMS server when the SDE GSRVR will be installed on the DBMS. SDE processing loads will be assigned to the DBMS server.
Figure 7-6 shows the three CPT Calculator configuration options for and ArcGIS Desktop 931 Workstation workflow. Top left analysis shows CPT Calculator result when using a small File Geodatabase data source, middle analysis shows CPT Calculator result when using an ArcSDE connection (ASC) to a DBMS geodatabase, and the bottom right shows CPT Calculator result when using an ArcSDE Direct Connect architecture. The CPT Calculator does not support a three tier ArcSDE configuration (SDE remote server).
Figure 7-7 shows the software configuration and the Arc09 Platform Service times sections included with the CPT Design requirements module. Four ArcGIS Desktop Workstation workflows, representing each of the data source selection options (Small FGDB, SDE Direct Connect, SDE Remote Server, SDE connect), are included in each result. The top view shows the install configurations, and the bottom view shows the resulting software processing loads.
Figure 7-8 provides a full view of the CPT Design solution for the same four ArcGIS Desktop Workstation workflows. The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the selected SDE remote server and the DBMS. The file data share (row 64) shows data traffic flow (2.5 Mbps) and network interface care (NIC) bandwidth (1 Gbps) for the common file share.
Figure 7-9 shows the ArcGIS Desktop Standard ESRI Workflows provided on the CPT Workflow tab. The Standard ESRI Workflows retain the standard workflow nomenclature generated by the CPT Calculator tab.
Centralized Windows Terminal Server/Remote Desktop Services (Citrix) Architecture
The Microsoft Windows Terminal Server operating system establishes a multiuser environment on a Windows server host. A Windows terminal client provides display and control of applications executed on the Windows Terminal Server. Microsoft uses a standard remote desktop protocol (RDP) to support communication between the terminal server and the Windows client, and the Microsoft host platforms are sometimes called Remote Desktop Servers.
The Citrix Presentation Server extension product enables a more efficient independent computing architecture (ICA) communication protocol to support communication between the terminal server and client Windows platform. The ICA protocol requires less than 28 Kbps bandwidth (rendering vector data information products) to support full Windows display and control of GIS applications supported on a Windows Terminal Server. Traffic can increase to 100 Kbps bandwidth when accessing a raster data source. Presentation Server includes client software for Windows, UNIX, Macintosh, and embedded Web client applications.
Four distributed ArcGIS Desktop configuration alternatives are identified in Figure 7-10. All configurations are supported by remote terminal client access to ArcGIS Desktop applications supported on a central Windows Terminal Server. ArcGIS Desktop configuration options include access to a network file data source, direct connect access to a geodatabase, and two ArcSDE connect options to a geodatabase (one connecting through a middle tier ArcGIS Server and the other connecting to ArcSDE installed on the database server).
The Windows terminal client communicates with the Windows Terminal Server through a compressed message-oriented communication protocol. Terminal clients have a persistent connection with the Windows Terminal Server ArcGIS Desktop session; lost connections are reinstated without losing the session. The application display is provided over the network to the terminal client, requiring much less data transfer than the spatial data query chatter between the application and the data source. The terminal client display traffic requirements are very small; supporting good application performance over 28 Kbps modem dial-up connections (displays with an image backdrop may require more bandwidth).
Each ArcGIS Desktop user session hosted on the Windows Terminal Server connects to each data source the same way as a distributed client workstation session. Most current ESRI customers using Windows Terminal Server also use the Citrix Presentation Server software. The Windows Terminal Server farm is supported by commodity Windows server platforms (Intel or AMD). Client session load balancing across the terminal server farm is managed by the Citrix software. Client profiles and security options are provided to support an optimum GIS user display experience.
Figure 7-11 shows the three CPT Calculator configuration options for the ArcGIS Desktop 931 Windows Terminal Server workflow. Top left analysis shows CPT Calculator result when using a small File Geodatabase data source, middle analysis shows CPT Calculator result when using an ArcSDE connection (ASC) to a DBMS geodatabase, and the bottom right shows CPT Calculator result when using an ArcSDE Direct Connect architecture.
Figure 7-12 shows the software configuration and the Arc09 Platform Service times sections included with the CPT Design requirements module. Four ArcGIS Desktop Windows Terminal Server (Citrix) workflows, representing each of the data source selection options (Small FGDB, SDE Direct Connect, SDE Remote Server, SDE connect), are included in each result. The top view shows the install configurations, and the bottom view shows the resulting software processing loads.
Figure 7-13 provides a full view of the CPT Design solution for the same four ArcGIS Desktop Windows Terminal Server workflows. The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the selected SDE remote server and the DBMS. The file data share shows data traffic flow and network interface card (NIC) bandwidth (1 Gbps) for the common file share.
ArcGIS Server Web Services Architecture
Web mapping services provide an efficient and effective approach to serving map products and services over the Internet. The ArcGIS Desktop architecture presented earlier in this section requires tightly coupled client/server processes that demand stable high-bandwidth communications supported over relatively short distances. Web client communications are supported using a transaction-based HTTP, which supports optimum communications over long distances and less stable communication environments. Critical components associated with the Web services communication architecture are identified in Figure 7-14.
Web services are published on a Web server. Web server clients are presented with a catalog of published services when accessing the Web site. Web applications consume map services and render a client presentation layer to support the published application workflow. Client and Web servers are loosely connected in which each client communication represents a complete transaction. Transactions are processed by the appropriate Web-based GIS server and returned to the client.
ESRI Web GIS services are hosted by ArcGIS Server software. ArcGIS Server provides an ArcObjects software-based server development environment for deploying GIS server-based ArcGIS applications and services. ArcGIS Server can be deployed in a Web architecture or as a LAN/WAN network service for desktop clients. ArcGIS Server is also used to deploy "smart client" mobile GIS technology. Smart clients are loosely connected, lightweight, handheld or desktop computers that support persistent data cache and disconnected GIS client operations. Client application deployment and data synchronization are managed by ArcGIS Server parent services.
The software architecture components for ArcGIS Server include Web applications (WAS), service object manager (SOM), server object container (SOC), and data server (DS) component functions that can be deployed on different platform combinations to support scalable capacity and system availability requirements. Location of the various software components and the selected software configuration can directly impact system capacity, service reliability, and overall output performance.
ArcGIS Server Component Architecture
ArcGIS Server is a set of objects, applications, and services that make it possible to run ArcObjects components on a server platform environment. Server objects are managed and run within the GIS server. Server applications make use of server objects and may also use other ArcObjects components that are installed on the GIS server.
The Web server hosts server applications and Web services developed using the ArcGIS Server application programming interface. These Web services and Web applications can be developed using the ArcGIS Server ADF, which is available for both .NET and Java developers and supported within the associated Web application server development environments.
Figure 7-15 provides an overview of the ArcGIS Server component architecture and the associated software functional locations. The ArcGIS Server architecture includes four configuration groups of software identified as Web applications, service manager, spatial services, and data source.
The ArcGIS Server configuration groups include the following:
Web Applications: The ArcGIS Server WAS components include a commercial Web HTTP server supporting communications with the Web clients and a Web application server development environment for .NET or Java Web applications or Web service catalogs. ArcGIS Server includes a Web tier that includes a .NET and Java Application Development Framework. ArcGIS Server also includes software components for simple object access protocol (SOAP) and representational state transfer (REST) Web service application program interfaces (APIs). ArcGIS Server includes translation of mapping services to a variety of Open Geospatial Consortium APIs, including WMS (Web Mapping Service for simple map images), WFS (Web Feature Service for streaming points, lines, and polygons), WCS (Web Coverage Service for raster and image steaming), CWS (Catalog Web Services for metadata searches), and KML (Keyhole Markup Language) for integration with Google Earth clients.
Server Object Manager: A server object manager (SOM) controls service object deployment and initial application assignment to deployed server object containers. SOM performs as a parent process, controlling service load balancing and managing deployment of published service configuration instances based on active inbound service request loads.
Server Object Container: The container machines (one or more depending on peak transaction requirements) host the server object containers (SOCs) that are managed by the SOM. Each service configuration is supported by dedicated SOCs. The server objects hosted within each SOC are supported by ArcObjects components installed on the container machine.
Data Source: The data server (GIS data source) is where the GIS data is stored. An ArcSDE data source supports the query processing functions. Standard GIS image or file data sources are also represented at this level.
Services available on ArcGIS Server can be published for use by intranet LAN or WAN applications. Application service assignment can be provided with direct access to the SOM without using the Web server interface.
Web Platform Configuration Strategies
A Web site can be supported with as few as one platform or as many as six or more platforms, depending on site capacity and availability requirements. ArcGIS Server platform configuration strategy can adapt to the required system reliability, availability, and security needs. This section will address the Web software component configuration strategies. Web security requirements will be addressed in more detail in the Information Security chapter. ArcGIS Server performance metrics are discussed in the Software Performance chapter.
The Web system architecture design alternatives are grouped as single-tier, two-tier, and three-tier configurations. Simple configurations are easier to maintain and support. More complex configurations satisfy higher-capacity and system availability requirements. Production operations are normally supported with high availability configurations (configurations that will continue providing services following any single platform failure).
ArcGIS Server is designed to support a scalable Web architecture. Optimum platform environments are configured using standard commodity server platform technology. ArcGIS Server is licensed based on the number of platform processor core supporting the primary ArcGIS Server software components. Following are recommended platform configuration strategies for supporting standard GIS Web services.
Single-Tier Platform Configuration
Figure 7-16 provides an overview of single-tier platform configurations. Single-tier configurations provide one or two platforms capable of supporting all Web service components. Most initial customer deployments with a small database can be supported by a single-tier architecture.
Standard Configuration: A complete Web site can be supported on a single hardware platform. This configuration is appropriate for Web service development and testing, sites with a limited number of service requests, and initial prototype deployments. A special single chip workgroup server license bundled with a Microsoft SQL Server database is available for customer sites that can be supported by a single platform configuration.
High-Availability Configuration: Most GIS server production operations require redundant server solutions, configured so the site remains operational in the event of a single platform failure. This configuration will continue to support production operations during single platform maintenance and upgrade and while configuring and publishing new services. This configuration includes (1) network load balancing to route the traffic to each of the servers during normal operations and only to the active server if one of the servers fails, (2) service manager load balancing to distribute spatial services processing load between the two platforms to avoid having requests back up on one server when extra processing resources are available on the other server (separate SOC containers are required on each platform to support this configuration), and (3) duplicated data servers that require a complete copy of the data.
Figure 7-17 shows the ArcGIS Server single-tier software configuration and the Arc09 Platform Service times sections included with the CPT Design requirements module. Four ArcGIS Server workflows, representing each of the data source selection options (Small FGDB, SDE Direct Connect, SDE Remote Server, SDE connect), are included in each result. The top view shows the install configurations, and the bottom view shows the resulting software processing loads.
Figure 7-18 provides a full view of the CPT Design solution for the same four ArcGIS Server workflows. The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the configured server platforms.
Two-Tier Platform Configuration
A two-tier architecture provides an optimum solution for sites supported with a separate database server. The two-tier high-availability option may become the most popular and practical configuration supporting most ArcGIS Server deployments.
The two-tier architecture in Figure 7-19 includes GIS server and data server platforms. The Web server and GIS server components are located on the GIS server platform, and the data server is located on a separate data server platform. This is a popular configuration for sites with large volumes of data resources or existing data servers. A single copy of the data can support multiple server components in conjunction with other enterprise GIS data clients.
Standard Configuration: The standard configuration includes one GIS Web server platform with a separate single data server platform. The Web server is installed on the GIS Web server platform.
High-Availability Configuration: High-availability operations require redundant server solutions, configured so the site remains operational in the event of any single platform failure. This configuration includes (1) network load balancing to route the traffic to each of the GIS Web servers during normal operations and only to the active GIS Web server if one of the servers fails, (2) SOM load balancing to distribute SOC processing load between the two GIS Web server platforms to avoid having requests back up on one server when extra processing resources are available on the other server (two SOC container groups are required on each GIS Web server platform to support this configuration), and (3) two data servers that are clustered and connected to a common storage array data source. The primary data server supports query services during normal operations, and the secondary data server takes over query services when the primary server fails. Data server clustering is not required if availability requirements are satisfied with a single data server.
Figure 7-20 shows the ArcGIS Server two-tier software configuration and the Arc09 Platform Service times sections included with the CPT Design requirements module. Four ArcGIS Server workflows, representing each of the data source selection options (Small FGDB, SDE Direct Connect, SDE Remote Server, SDE connect), are included in each result. The top view shows the install configurations, and the bottom view shows the resulting software processing loads.
Figure 7-21 provides a full view of the CPT Design solution for the same four ArcGIS Server workflows. The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the configured server platforms.
Three-Tier Platform Configuration
Three-tier configurations include Web server, map server/container machine, and data server tiers. Two configuration options are provided, based on the location of the ArcGIS Server SOM.
Figure 7-22 shows a three-tier configuration with the service manager located on the Web server tier. This configuration provides the simplest three-tier architecture (network load balancing handles Web tier failover), and would likely be the most popular solution. The three-tier configuration provides a scalable architecture, where the middle tier can support two or more platforms as required to support capacity requirements.
Standard Configuration: The standard configuration includes a single Web server with a separate container machine layer and a separate data server. The container machine layer can be a single platform or can be expanded to support several platforms, depending on the required site capacity. SOM load balancing is provided by the GIS Web server service manager.
High-Availability Configuration: High-availability operations require redundant server solutions, configured so the site remains operational in the event of any single platform failure. This configuration includes (1) network load balancing to route the traffic to each of the GIS Web servers during normal operations and only to the active GIS Web server if one of the servers fails, (2) SOM load balancing to distribute SOC processing load between the two map server/container machine platforms to avoid having requests back up on one server when extra processing resources are available on the other server (separate SOC containers are required on each map server/container machine platform to support this configuration), and (3) data server configuration supporting enterprise requirements.
Figure 7-23 shows a three-tier configuration with the SOM located on the container machine tier. The Web server and SOM connectors are located on the Web server platform, and the SOM and SOC components are located on the container machine platforms. This could be a preferred configuration when supporting Java applications on Linux-based Web servers. In this configuration, all the COM-based software is located on the container machine tier. The failover scenarios are more complicated. If the SOM1 software fails, WAS1 will send maps to SOM2. SOM2 will return results to the parent WAS2 output file. Client will return to WAS1 to get results and will need a virtual disk mount to receive the result from the SOM2 output directory. It will still be necessary to configure SOM load balancing for optimum capacity during peak loads.
Standard Configuration: The standard configuration includes a single Web server with a separate container machine layer. The container machine layer can be a single platform or can be expanded to support several platforms, depending on the required site capacity. Web application traffic balancing is supported by the GIS Web server SOM connectors. The ArcGIS Server implementation can be configured in a failover mode (SOM2 would be activated only if SOM1 fails). SOM load balancing is provided by the server manager components (preferably no more than two SOM components on the container machine tier). All of the container machines can host SOM1 and SOM1 instances, so both SOM1 and SOM2 will deploy dedicated SOC instances on each host platform. Separate data server is provided as a common data source. Administration of this architecture can become increasingly complex as additional container machines are deployed - most of this complexity is managed by the SOM dispatch software.
High-Availability Operations: High-availability operations require redundant server solutions, configured so the site remains operational in the event of any single platform failure. This configuration includes (1) network load balancing to route the traffic to each of the GIS Web servers during normal operations and only to the active GIS Web server if one of the servers fails, (2) Web application traffic load balancing to distributed inbound load between the two SOM located on the container machine tier. (3) SOM load balancing to distribute SOC processing load between the container machine platforms to avoid having requests back up on one server when extra processing resources are available on the other server (dedicated SOC containers are required on each container machine platform to support this configuration, with each SOC assigned to a parent SOM), and (4) data server configuration supporting enterprise requirements. Administration of this architecture becomes increasingly complex as additional map servers/container machines are deployed - most of this complexity is managed by the SOM dispatch software.
Three-Tier Service-Oriented Platform Configuration
ArcGIS Server Web Applications can be developed and deployed supported entirely by remote Web data services.
The internal GIS Web Servers are configured as identified in the earlier configurations. Web data services can be published by the internal GIS Web Servers supporting enterprise applications deployed on a separate Web application tier. Web services can be passed through the firewall using standard HTTP service protocols.
Many of the more powerful ArcGIS Server applications benefit from a more tightly coupled DCOM communications. Each application is directly coupled to an assigned SOC to support each transaction. Results from these applications can be provided as services to more loosely coupled enterprise applications supported in a separate security zone by using standard HTTP protocols.
ArcGIS Server provides a broad range of functionality that can be used to support standard Web mapping or for more complex geospatial workflows that previously were not available through open standard Web protocols. Use of the ArcGIS 9.3.1+ optimized map document (MSD) or preprocessed cached data layers available with ArcGIS Server can improve user performance beyond what we saw with ArcIMS technology and reduce network traffic requirements. Careful attention to user requirements and proper deployment of the technology can make a difference.
Figure 7-25 shows the ArcGIS Server three-tier software configuration and the Arc09 Platform Service times sections included with the CPT Design requirements module.
Figure 7-26 provides a full view of the CPT Design solution for the same four ArcGIS Server workflows.
Figure 7-27 shows three CPT Calculator configuration options for the ArcGIS Server workflow.
Figure 7-28 shows the ArcGIS Server Standard ESRI Workflows provided on the CPT Workflow tab.
ArcGIS Server Image Extension Platform ConfigurationArcGIS Server Image Extension provides an efficient and effective approach to store and serve imagery.
Figure 7-30 provides an overview of the ArcGIS Server Image Extension platform configurations.
ArcGIS Server Image Extension will allow legacy ArcGIS Image Server clients to connect direct to the Image Server interface for the ArcGIS 9.3.1 release. Image Server and Service Provider software components will be fully integrated with ArcGIS Server SOM and SOC instances with future releases.
Figure 7-31 shows the software configuration and the Arc09 Platform Service times included with the CPT Design requirements module.
Figure 7-32 provides a full view of the CPT Design solution for the same two ArcGIS Server Image Service workflows.
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 7-33 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
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.