ArcGIS for Server Reference Implementations. An ArcGIS Server s architecture tour

Transcription

1 ArcGIS for Server Reference Implementations An Arc s architecture tour

2 Basic Single Machine Site Advantages Easy to setup Fast performance (keep file resources local) Client Manager Data (Files) Uses: Development Intranets 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

3 Single Machine Site with Proxy Client Firewall Firewall DMZ Proxy Hides your machine, and ports Block your admin end-points Forces all access to your Through your Proxy Administration through 6080 Manager Data (Files) Data (DBs)

4 Single Machine Site with Proxy Client Firewall Proxy Manager Uses: Intranets / Internet access Advantages Fast performance (keep file resources local) Enhanced security To keep in mind No HA Token authentication only Data (Files) Data (DBs)

5 The ArcGIS Web Adaptor Client Firewall Web Server Web Adaptor Manager 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

6 ArcGIS site with Multiple Web Adaptors Client Client Web Adaptor configured to block anonymous access (Users can see private and public services) Firewall Web Adaptor (Private) Web Adaptor (Public) Web Adaptor configured to allow anonymous access (Users can see public services) Manager Data (Files) Data (DBs)

7 Multi-Machine Sites Basic Concepts Two or more machines sharing single config-store server directories Pool of machines using ports 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

8 Multi-Machine Site With Load Balancer Client Load Balancer Typical configuration to support applications Firewall Load balancer fronts a pool of s 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

9 Multi-Machine Site With Web Adaptor Client Web Adaptor A variation of the previous configuration Firewall Supports Web Tier Authentication 4000

10 Multi-Machine Site 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

11 Arc components Single Machine Sites Basic With Proxy With Web Adaptor Multi Machine Sites Concepts Basic (without a load balancer) With Load Balancer With Web Adaptor With redundant Web Adaptors Load Balanced Sites Concepts Active-Passive Fail Over Active-Active

12 Load balanced Concepts aka Siloed Architecture Load-Balancer/Proxy or Web Adaptor Client Proxy/Load Balancer Load-Balancer/Proxy or Web Adaptor Use Cases: High Availability High Capacity Keep in mind: Sites are not aware of each other You must keep Data, Security and Services in sync Must leverage third party load balancers

13 Arc components Single Machine Sites Basic With Proxy With Web Adaptor Multi Machine Sites Concepts Basic (without a load balancer) With Load Balancer With Web Adaptor With redundant Web Adaptors Load Balanced Sites Concepts Active-Passive Fail Over Active-Active

14 Load Balanced s Active-Active Client Proxy/Load Balancer Use Cases: High Availability High Capacity Load-Balancer/Proxy or Web Adaptor Load-Balancer/Proxy or Web Adaptor Notes: Supports distribution of sites across separate data centers Must keep Sites in sync! Active Active

15 Arc components Single Machine Sites Basic With Proxy With Web Adaptor Multi Machine Sites Concepts Basic (without a load balancer) With Load Balancer With Web Adaptor With redundant Web Adaptors Load Balanced Sites Concepts Active-Passive Fail Over Active-Active

16 Load Balanced s Active-Passive Fail-Over Client Use Cases: High Availability with Fail-Over Licensing Load-Balancer/Proxy or Web Adaptor Proxy/Load Balancer Load-Balancer/Proxy or Web Adaptor Notes: No additional licensing cost for Fail-Over sites Supports distribution of sites across separate data centers Must keep Sites in sync! Active Stand-by

17 Questions

18

19 Concept: Clusters Cluster A Cluster B Site In Arc, a cluster is a logical group of machines within a site that run the same services

20 Concept: Clusters Cluster A Cluster B Site Total instances (assuming 2 per GIS server) 4 4 2

21 Moving machines from cluster to cluster Cluster A Cluster B Site Total instances (assuming 2 per GIS server) 2 2 4

22 Moving services from cluster to cluster Cluster A Cluster B Site Total instances (assuming 2 per GIS server) 2 4 4

23 Questions

24 Arc components Single Machine Sites Basic With Proxy With Web Adaptor Multi Machine Sites Concepts Basic (without a load balancer) With Load Balancer With Web Adaptor With redundant Web Adaptors Other Reference Implementations Active-Passive Fail Over Load Balanced Sites (aka Siloed architecture)