Configuring, Tuning and Managing ArcGIS Server. Dan O Leary James Cardona Owen Evans

Transcription

1 Configuring, Tuning and Managing ArcGIS Server Dan O Leary James Cardona Owen Evans

2 Introductions and Overview Welcome and Thanks for Attending Approach of this Session Share Best Practices and Techniques Demonstrations Discussion / Q&A at End of Session Topical Outline of Session Planning GIS Services and Applications Publishing GIS Services Optimizing GIS Services Administering, Testing and Monitoring GIS Services and Applications Configuring Distributed GIS Server Deployments Providing Protected GIS Services and Applications Please Silence Cell Phones Complete a Session Survey 2

3 PLANNING GIS SERVER SERVICES AND APPLICATI0NS 3

4 Roles and Resources for Planning GIS Server Solutions Planning is Critical Best Practice: Get Participation and Buy-in Business Participants CTO / CEO Vision and Buy-in Mission Manager End Users IT Management Technical Participants GIS Analysts Business Analysts Solutions Architects IT Staff Development Server / System / Network Administration (Including GIS Server) 4

5 Roles and Resources for Planning GIS Server Solutions Resources Available to Assist in Planning GIS Solutions Online Resources ArcGIS Online Help System ArcGIS Resource Centers System Design Strategies Whitepaper ESRI Online Support Other Resources ESRI Professional Services Enterprise Consulting Many Business Partners with Strong GIS Practices 5

6 PUBLISHING GIS SERVICES 6

7 Publishing GIS Services Object Pooling and Instances Process Isolation Best Practices for Geoprocessing Services 7

8 Publishing GIS Services Object Pooling Non-Pooled Services Pooled Services Typically holds reference to the service for duration of session State information maintained in web server/ browser E.g., current extent, layer visibility, etc. Recommended, when appropriate (scales better) Required for Editing Task Computationally expensive New instance started for each session Number of users cannot be more than number of instances 8

9 Publishing GIS Services Object Pooling Define Minimum and Maximum number of instances Minimum is the number that start up immediately Instances are distributed across all host servers 9

10 Publishing GIS Services Process Isolation HIGH ISOLATION LOW ISOLATION Each service instance runs as a single thread in a dedicated ArcSOC.exe process Many service instances run as separate threads in each ArcSOC.exe process. Recommended: A failed instance is isolated to one ArcSOC.exe process Max threads per process: At 9.2, max is four. At 9.3, default is eight and is adjustable. ArcSOC.exe ArcSOC.exe Thread Thread Thread Thread ArcSOC.exe Thread ArcSOC.exe Thread 10

11 PUBLISHING SERVICES DEMO 11

12 Geoprocessing Services Best Practices Use in-memory workspace for intermediate datasets Pre-compute unchanging intermediate datasets Use synchronous unless model takes a long time If using asynchronous, set an appropriate interval to check for results. For complex models, always use high isolation If using 9.2 multi-user geodatabases, patch to SP4 12

13 Geoprocessing Services Considerations GP services are powerful and flexible; however, always ask yourself, Do I really need a geoprocessing service? Is it possible to identify a finite number of answers that address most anticipated questions? If so, pre-compute results for those situations and provide them as map services and design your application to present them in a simple way EXAMPLE: Floodplain analysis compute model results for every 3-inch rise in water level from 0-10 feet, and in the application provide a slider bar to switch between the model results for different heights. 13

14 OPTIMIZING SERVICES 14

15 What impacts Map Rendering Performance? Hardware Rendering map images is a server resource intensive process ArcGIS Server Configuration Number of SOC s available to a web application to minimize queuing. ArcMap Document (MXD) What and how to Render the spatial data is defined by the ArcMap Document (MXD) 2008 EGUG Conference 15

16 ArcMap Document Performance ArcMap Server Performance can be significantly impacted by: Scale Constraints 2008 EGUG Conference 16

17 ArcMap Document Performance ArcMap Server Performance can be significantly impacted by: Scale Constraints Labels 2008 EGUG Conference 17

18 ArcMap Document Performance ArcMap Server Performance can be significantly impacted by: Scale Constraints Labels Symbology 2008 EGUG Conference 18

19 ArcMap Document Performance ArcMap Server Performance can be significantly impacted by: Scale Constraints Labels Symbology Building_operational_map_layers 2008 EGUG Conference 19

20 Tool for Tuning an MXD Tool: MXDPERFSTAT ArcEngine application Provides Analysis of MXD Requires an ArcGIS Desktop license (Arcview, ArcEditor, ArcInfo) Free download from ESRI s Arcscripts web site: EGUG Conference 20

21 Interpreting Output Results Goal: Sub second redraw times for all map displays Footer Reference 21

22 Interpreting Output Results Goal: Less then 0.10 second refresh time for an individual layer Refresh Time: Geography Phase: Graphics Phase Cursor Phase Total Time to fetch and draw layer features Time to fetch and render geometries Time to fetch and render Labels and Graphics Time to fetch data from the Data Source Footer Reference 22

23 Demo: Using MXDPERFSTAT Tool and Viewing output Identified location (x,y coordinate) that contains a dense area of infrastructure x,y coords for center of map display: , Based on learned user patterns identified commonly used map display scales Map Displays: 2400, 8000 Run MXDPERFSTAT tool against MXD to get baseline results. mxdperfstat.exe -mxd D:\Projects\FedUC_09\DynamicMaps\WashingtonMetroArea_fixme. mxd -scale 24000,8000 -xy , EGUG Conference 23

24 Conclusions 9.3 and previous releases 1. Aggressively apply Scale Constraints to limit the amount of data displayed at any time 2. Avoid ESRI s advanced Cartography capabilities. a. Do not use Halos or masks for labels or point features. Use simple marker symbols. b. Do not use the advanced line symbology options to Merge or Join line symbols. Use simple line symbols. c. Do not use bitmap or cartographic fill patterns. Use simple fill patterns. 3. Avoid labeling of crowded features that require extra processing to define where to place the label. Use annotation instead, if possible EGUG Conference 24

25 9.3.1 A sneak peek ahead 25

26 Overview At ArcGIS Server includes high performance Map Services The publishing workflow has been extended to include analysis of the map before publishing Author Analyze Publish Use Use a high performance graphics engine Map services published via the Map Service Publishing toolbar take advantage of the new mapping engine These services are called optimized map services in administration tools

27 9.3.1 OPTIMIZING DEMO 27

28 ADMINISTERING, MONITORING AND TESTING 28

29 ArcGIS Server Administration ArcGIS Desktop Tool ArcCatalog Administer, Consume, Publish Services Server and Service Statistics Service Create, Wait and Use Time ArcGIS Server Web Tool ArcGIS Server Manager Administer Services Publish Services Create Web Applications Review Server Logs Secure Web Applications and Services Log Enhancements Verbose level more informative 29

30 System Testing and Monitoring Testing and Monitoring Systems Testing is critical throughout development Monitoring is critical throughout operations Best Practices in Testing and Monitoring GIS Applications Workflows and User Think Time GIS Services System Components Performance, Capacity and Health Hardware Processes Storage Subsystem and Disk Activity Network Utilization 30

31 System Testing and Monitoring Tools System Level Tools PERFMON, DSTAT, IOSTAT, etc. Used for monitoring, testing and managing system components Web Application and Service Level Tools Jakarta JMeter Fiddler, Firebug, Other HTTP Conversation Monitors Visual Studio Team Test Edition Tools integrated into IDE Combines System Level and Service Level Tools 31

32 MONITORING AND TESTING DEMO 32

33 CONFIGURING DISTRIBUTED GIS SERVER DEPLOYMENTS 33

34 Distributed Deployments Why Move To Distributed Deployments Common Architectures Configuring a Distributed System Data issues Fail-over 34

35 Why Distribute? Increase Capacity Increase Reliability 35

36 Deployment Architectures Adding Capacity Web Tier SOM Web Tier SOM SOC ArcSDE Web Tier SOM SOC ArcSDE SOC ArcSDE DBMS DBMS DBMS Single Machine Scenario Multiple Machine Scenario 36

37 Deployment Architectures Adding Additional Servers 37

38 THE END? I Still Feel Lost and have lots of questions!! 1. What do I do different when configuring a system with multiple machines 2. Where should data and maps and tools go for optimal performance? 3. What is offered natively for fail-over? 38

39 Checklist for installing a distributed configuration In Server Help: Under Administering the Server Æ Configuring a Multiple Machine Deployment. Web help: 39

40 Distributed Configuration A quick look at what is different Output directories Log file path Configuration xml file to use for applying same properties to all machines during post-installs Windows Services started on different machines 40

41 Where Should Maps Go? Put on the same machine where the SOC is installed for fastest access and for redundancy Web Tier SOM SOC Data Src MXD SOC Data Src MXD Need same directory structure on each machine. Also need to make sure map documents stay in synch 41

42 Where Should Data Go? General Accessing data from geodatabase in SDE is most scalable option Accessing data from File Geodatabase on SOC machine is fastest Avoid accessing data using UNC paths 42

43 Service Specific Data Issues? Geocoding Specific Single address geocoding ArcSDE address locators for single address geocoding Batch address geocoding File-based address locators for batch geocoding Use local locator files instead of UNC All geocoding Take locator defaults 43

44 Some Possible Ways of Managing Data Web Tier SOM SOC File GDB SOC File GDB SOC File GDB One Way Replication DBMS Data Warehouse 44

45 Some Possible Ways of Managing Data Web Tier SOM Data Editors and Managers SOC ArcSDE DBMS Production Database One Way Replication SOC ArcSDE DBMS Data Warehouse 45

46 Service Specific Data Issues? Geoprocessing Specific Reading and writing data to UNC paths is slower Geoprocessing tools are slower with UNC paths. Considerations for authoring and publishing models overview_of_geoprocessing_with_arcgis_server 46

47 Service Specific Data Issues? Geoprocessing Specific Write output to a local staging directory This is a flag in the service s cfg file Located in <ArcGIS Server install directory\server\user\cfg <Properties>. <LocalJobsDirectory>C:\temp\SocialVulnerability</LocalJobsDirectory>. </Properties> 47

48 Service Specific Data Issues? Geoprocessing Specific Web Tier SOM Without Tag With Tag UNC Path Jobs Directory SOC File GDB GP Service Each output written using UNC Path as it is created UNC Path When Local Model Temp Done- All Directory Outputs Each output written written locally as it is created SOC File GDB GP Service 48

49 Demonstration Geoprocessing Service 49

50 What about fail-over? Built-in SOC fail-over SOM machine is constantly monitoring SOC machines registered to it to make sure they are alive. If a SOC machine fails, other SOC machines registered with the SOM will spool up instances of GIS Services to get to minimum number specified in config file or to handle current load. When SOC machine is added or brought back on line, GIS Services will be redistributed to take advantage of the new SOC. 50

51 Demonstration SOC fail-over 51

52 What about fail-over? SOM fail-over Can configure a pool of Connections to use for trying to make a connection to SOM. (IConnectionManager) When Connection Manager is used to connect, it will use pool and will go to next server in pool if the connection fails for one. 52

53 Demonstration SOM fail-over 53

54 CONFIGURING FOR PROTECTED ACCESS 54

55 Deployment Architectures Firewall Best Practice ESRI does not recommend firewalls between ArcGIS Server components Best practice is the use of a Reverse Proxy for securing access to Trusted systems Internal Users External Users Internet Non-Trusted systems DMZ Reverse Proxy Intranet Trusted systems ArcGIS Server (Web Tier, SOM, SOC, ArcSDE)

56 Deploying Protected GIS Resources Non-Trusted Systems External Users DMZ Trusted Systems Network Device Reverse Proxy Options: Network Device Configure Web Server (Apache) Network Appliances Microsoft ISA Citrix Netscaler Others Internal Users 56

57 CONFIGURING FOR PROTECTED ACCESS DEMO 57

58 Questions and Discussion Complete Session Survey 58

59 Thank You and Enjoy the Conference! ESRI Developer Summit