ArcGIS for Server Deployment Scenarios An Arc s architecture tour Ismael Chivite Product Manager at Esri
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Arc is a pure GIS Web Services Server. All communication for using and administering occurs via http Core Concepts This is the user that can administer Arc. Not a Windows/Linux user (unless you want to) s live within an : a logical grouping of servers that simplifies administration Manager ArcGIS Primary Site Administrator Arc Account Web browser based management console. You do not need a separate web server to run this Arc processes run under this user Two folders that store key information needed for your server to run. Make sure the Arc user has Read/Write access and that folders can be accessed from all s
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Basic Single Machine Configuration Client Manager Data (Files) Keep them local Best performance Typically dedicated machine Data (DBs) Keep your files local Best performance
Basic Single Machine Configuration Client Uses: Development Intranets Advantages Easy to setup Fast performance (keep file resources local) Manager Data (Files) To keep in mind No HA No http standard ports used Security Admin end-points exposed to clients (Consider restricting IPs) Only Esri s token based authentication
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Single Machine Configuration with Proxy Client http:80 Proxy Hides your machine, and ports Firewall Block your admin end-points Forces all access to your Through your Proxy Administration through 6080 Manager http://acme.com/context/admin http://acme.com/context/manager Data (Files) Data (DBs)
Single Machine Configuration with Proxy Client Firewall Proxy Manager http:80 Uses: Intranets / Public access Advantages Fast performance (keep file resources local) Enhanced security To keep in mind No HA Token authentication only unless a Web Adaptor is used Data (Files) Data (DBs)
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
The ArcGIS Web Adaptor Client Firewall Web Server Web Adaptor Manager http:80 An Esri proxy implementation for Arc Runs on your web server IIS, Java Helps you leverage your third party web server security features Including Web Tier Authentication Automatically handles s in your site* Data (Files) Data (DBs) * Will see later
Single Machine Configuration with Web Adaptor\s Client Client Web Adaptor configured to block anonymous access (Users can see private and public services) http:80 Web Adaptor (Private) Firewall http:80 Web Adaptor (Public) Web Adaptor configured to allow anonymous access (Users can see public services) Manager Data (Files) Data (DBs)
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Single Machine Configuration (Fail-over) All requests forwarded to the active site Standby site not used until failure in active node is detected Client Proxy\Load Balancer Manager Manager Active Stand-by Each has its own Config-store and Server directories
Single Machine Configuration (Fail-over) With Replicated Data Tier Client Proxy\Load Balancer Manager Manager Data (Files) Data (Files) Active Stand-by Database Replication Database
Single Machine Configuration (Fail-over) HA variation of a single machine deployment Relies on an external load balancer Must pay attention to data tier HA strategy Must keep stand-by Server in sync License for standby server provided at no additional cost Duplicate shared token key across sites if using tokens
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Load balanced Single Machine Configuration (Active-Active) aka Siloed Architecture Client Proxy\Load Balancer Manager Manager Active Active
Load balanced Single Machine Configuration (Active-Active) With Data Tier Client Proxy\Load Balancer Manager Manager Active Data (Files) Data (Files) Active Database and/or Network Share
Load balanced Single Machine Configuration (Active-Active) High Capacity variation of a single machine deployment Relies on an external load balancer Must keep all s in sync! Manually Scripting Virtualization Duplicate shared token key across sites if using tokens If performance is key: keep file-based data and caches locally Ideal for serving map tiles (High capacity/ha)
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Multi-Machine Configurations Basic Concepts Two or more machines sharing single config-store server directories Pool of machines using ports 4000-4005+ Internall use only. Clients cannot use All s kept in sync for you update one all other nodes in the pool updated* 4000 Data strategies: As usual. Keep local if you can Note: Map caches can t be local If you share, share for all * Unless using Clusters. We will see later
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Basic Multi-Machine Configuration (without a load balancer) Adds capacity to a single machine deployment Without a load balancer, single point of failure for applications Only practical for batch processing (Map caching) 4000
Desktop Edit Desktop Basic Multi-Machine Configuration (Map Caching Workflow Example) Multi-user Geodatabase Changes FileGDB One Way replica FileGDB FileGDB
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Multi-Machine Configuration With Load Balancer Client Load Balancer Typical configuration to support applications Firewall Load balancer fronts a pool of s Note: How load balancing works? For High Capacity or HA with simplified administration 4000 Typically Load Balancer acts as or is complemented by a proxy + firewall If not using Web Adaptor, can t use Web Tier authentication
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Multi-Machine Configuration With Web Adaptor Client Web Adaptor A variation of the previous configuration Firewall Supports Web Tier Authentication Does not require overhead of managing a a third party load balancer 4000 Use redundant Web Adaptors for HA (see next)
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Multi-Machine Configuration With Redundant Web Adaptors Client Web Adaptor Web Adaptor A HA variation of the previous configuration Firewall Requires third party load balancer or web farm clustering 4000 As in all HA configurations: Must consider HA implications for, Config-Store and Data tier
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Concept: Clusters Cluster A Cluster B 4000 4000 +1 Site In Arc, a cluster is a logical group of machines within a site that run the same services
Concept: Clusters Cluster A Cluster B 4000 4000 +1 Site Total instances (assuming 2 per GIS server) 4 4 2
Moving machines from cluster to cluster Cluster A Cluster B 4000 4000 +1 Site Total instances (assuming 2 per GIS server) 2 2 4
Moving services from cluster to cluster Cluster A Cluster B 4000 4000 +1 Site Total instances (assuming 2 per GIS server) 2 4 4
Concepts Single Machine Configurations Basic Basic with Proxy Fail-Over Load Balanced or Siloed Multi Machine Configurations Concepts Basic (without a load balancer) With Load Balancer With redundant Web Adaptors Cluster Concepts
Questions