ArcGIS Server Web Server Web Applications WWW. Applications. ArcGIS Server Manager. GIS Server. Data. Desktop GIS. ArcGIS Desktop (content author) SOM

Transcription

1 ArcGIS Server on Linux and Unix Architecture and Deployment Recommendations Peter D Souza and Ravi Narayanan Developer Summit

2 Our Assumptions Familiarity with ArcGIS Server Familiarity with Solaris and Linux Developer Summit

3 Agenda I. Components Overview and Architecture II. III. IV. Pre-Install requirements Installation Overview Administration and Usage Server Management Troubleshooting V. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

4 I. ArcGIS Server Components Overview ArcGIS Server Web Server Web Applications WWW GIS Server ArcGIS Server Manager SOM Data ArcCatalog Administrator Desktop GIS Applications ArcGIS Desktop (content author) Developer Summit

5 ArcGIS Server - Communications DCOM SOM Client HTTP Web Services Web Apps Web Tier TCP/IP D A T A Developer Summit

6 Server Object Manager (SOM) Architecture SOM Request Response In nterop Identity Server Directory server Role agsadmin or agsusers User Password Group U1 P1 agsadmin U2 P2 agsusers U3 P3 agsusers U4 P4 agsadmin Developer Summit

7 Agenda Components Overview and Architecture Pre-Install Requirements Installation Overview Administration and Usage Server Management Troubleshooting I. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

8 II. Pre-Install Requirements Ensure clean uninstall of previous versions including any zombie processes Refer Knowledge Base Article ID Install will check that /etc/hosts contains valid entry for server IP localhost machinename machine.example.com Supported version of Open GL Ports 135, 2099, 3774, 8099, 8399 and are free No other multi-user user ArcGIS Installation exists on the machine No other ArcGIS Installation exists in the same account Developer Summit

9 Agenda Components Overview and Architecture Pre-Install Requirements Installation Overview Administration and Usage Server Management Troubleshooting I. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

10 III. Installation Overview Simple single workflow for installation in 9.2 Installation checks for pre-requisites requisites Required OS user accounts are added by the install No post-installation Login as user admin at the end of install Recommendations: Create ArcGIS Server owner account prior to installation ti Do not use agsadmin or agsuser as owner account Ensure sufficient space in temp directory (~1 GB) When using Red Hat 4 systems for remote install use ssh X X Developer Summit

11 Agenda Components Overview and Architecture Pre-Install Requirements Installation Overview Administration and Usage Server Management Troubleshooting I. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

12 IV. Administration and Usage: Server Management User Management Managing Host () Machines Server Directories Configuring Services Web Applications Data Command Line Manager Developer Summit

13 Server Management User Management (Cont..) OS level root nobody group Owner* agsuser agsadmin Do not delete agsuser and agsadmin OS user accounts agsuser and agsadmin OS accounts created in /arcgis/.home Owner account, if created by the setup, resides under /arcgis/servercore/.server/<username> * Owner stands for the account owning the ArcGIS Server Developer Summit

14 Server Management User Management ArcGIS Server level other Owner* agsadmin group agsadmin admin agsusers group agsuser other All users except agsuser and agsadmin are virtual users Only members of agsadmin group can log into Manager admin, agsuser and agsadmin cannot be deleted * Owner stands for the account owning the ArcGIS Server Developer Summit

15 Server Management User Management (Cont..) Every SOM s identity server should contain the owner of SOM as well as the owner of all machines that are added to it. In a multiple SOM scenario all users should be replicated on all SOM servers SOM User Password Group SOM SOM U1 U1 U2 P1 P2 agsadmi n agsuser SOM Load Balancing U2 U3 U4 U3 U4 P3 P4 agsuser agsuser Developer Summit

16 Server Management User Management (Cont..) Super user account does not need to exist in this database Recommendation: ONLY make a user a member of the agsadmin group when absolutely necessary Developer Summit

17 Server Management - Hosts Local machine added to HOSTS by default Add SOM/ owners to the user list before adding remote HOSTS machine dropped from HOSTS if it is down when SOM is restarted All machines should have the same license level Recommendation: Use fully qualified name or IP address for remote HOST SOM HOST1 HOST 2 HOST 3 Developer Summit

18 Server Management Hosts (Cont..) Adjust the host capacity to effectively manage server load Recommendation: Recommended capacity is 2 to 4 instances per CPU Developer Summit

19 Server Management - Server Directories Directory Type SOM Share Access(r/w) Access(r/w) Directory Create Virtual Directory Add to Server Directory List Server Cache Server Jobs Server Output Server Log Set as Log directory in Manager Data Developer Summit

20 Server Directories (Cont ) Map Cache directories are referenced by Service names Each Geodata service must use a separate output folder Recommendation: Avoid using filesystems mounted through automount unless necessary Developer Summit

21 Server Management Configuring Services ArcGIS Server can host Map, Globe, Geodata or locator services. Know the available capabilities for a resource Eg: Mapping, Query, Geodata access for Map Documents Expose only the required capabilities Service configuration files (/arcgis/server/user/cfg/) g can be edited to fine tune additional parameters Eg: MaxImageWidth, MaxImageHeight, MaxBufferCount, MaxRecordCount Developer Summit

22 Configuring Services (Cont..) Service Minimum Instances Maximum Instances Service Service Service Total 8 20 Example: Pooled, High-Isolation service A. Single machine Configuration: 20 instances B. Multiple machine (N): 20 instances distributed across N machines Developer Summit

23 Server Management Web Applications Using Internal Web Server not recommended for production environments Configuring SOM Failover or Round Robin For local ArcGIS Server connections only Custom setting in faces-config.xmlconfig.xml ESRI or Custom Fonts should reside in the system fonts folder Knowledge Base Article ID Note: Read ArcGIS Server Help topic Deploying the application to a production environment Developer Summit

24 Server Management Data Always use lower case directory names for data paths Do not use special characters or spaces in file/directory names Ensure data is accessible from all machines Note: Use File Geodatabase as an alternative to Personal Geodatabase on Solaris and Linux Developer Summit

25 Server Management Data (Cont..) Author map documents using Unix Ready data When possible, choose relative path to data Use Set Data Source to update absolute data paths in MXD/PMF Useful ArcGIS Help topics ( Creating Interactive maps Thinking about maps in web-enabled enabled GIS applications An overview of authoring and publishing services Developer Summit

26 Server Management Data (Cont..) Globe services 3D Vector data (non-rasterized) and elevation data should be fully cached before serving Geoprocessing Services Ensure data referenced by the toolbox is relative to the toolbox Set the relative paths option of the toolbox to true Developer Summit

27 Server Management - Command Line Manager Useful when using a headless environment Invoked via command java -jar arcgis/java/manager/cli/arcgis_climanager.jar Supports Manager operations for Services Server Directories Host Machines Scripting support for Python and JavaScript ascript ArcGIS>executescriptfile listconfigs.py Developer Summit

28 Agenda Components Overview and Architecture Pre-Install Requirements Installation Overview Administration and Usage Server Management Troubleshooting I. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

29 V. Troubleshooting Installation log files System requirements check /$ROOTHOME/ArcGIS_MWSysReq.log Actions performed during install /$ROOTHOME/ArcGISServer_InstallLog.log List of installed features /$ROOTHOME/ArcGISServer_InstalledFeatures.log Server configuration log /arcgis/servercore/.server/configuration.log Note: $ROOTHOME refers to the home directory of root account Developer Summit

30 Troubleshooting (Cont..) Runtime Logs Server startup and shutdown log /arcgis/servercore/.server/agsserver.log Authentication log /arcgis/servercore/agsidsvr/bin/remotesa.log Manager output and error logs /arcgis/java/manager/service/logs/manager_stdout.txt or manager_stderr.txt ArcGIS Server usage logs (viewable through Manager) /arcgis/server/user/log Diagnostic tool > /arcgis/scripts/server_diag_tool Developer Summit

31 Troubleshooting (Cont..) List of Processes Server Object Manager and Server Object Container arcsom.exe arcsoc.exe Internal Webservers 2 Tomcat processes Virtual X Server Xvfb or Xsun Sun Java System Directory Server ns-slapdslapd Identity server remotesa Enterprise Core Services (Interop) Watchdog, mwrpcss and regss Developer Summit

32 Agenda I. Components Overview and Architecture II. III. Pre-Install Requirements Installation Overview IV. Administration i ti and Usage Server Management Troubleshooting V. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

33 V. Configuration Scenarios High Availability Redundancy for all components (Webserver, SOM,, Data) Network Load Balancer Web Server Web App failover Web Server SOM SOM SOM Load Balancing Data Developer Summit

34 Agenda I. Components Overview and Architecture II. III. Pre-Install Requirements Installation Overview IV. Administration i ti and Usage Server Management Troubleshooting V. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

35 Configuration Scenarios Scalability Adding more computing power Client WS SOM. Remember to add all SOM and owners to users list Knowledge Base Article ID Developer Summit

36 Agenda I. Components Overview and Architecture II. III. IV. Pre-Install Requirements Installation Overview Administration and Usage Server Management Troubleshooting V. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

37 Configuration Scenarios Performance Possible performance bottlenecks Web Server (Transmission time) SOM (Wait time) (Usage time) Data (Search and retrieval time) Other bottlenecks Pooling model CPU Dynamic Services Static Services Memory I/O Network Developer Summit

38 Performance Pooling To ensure service availability, use pooled instances Maximum throughput occurs between 2 to 4 instances per CPU Developer Summit

39 Performance CPU Dynamic services Show relevant information Apply scale dependencies Additional tips available at p_service.htm Static services Use cached data Command line cache generation available /arcgis/java/tools/generatemapcache Additional tips available at _map_caches.htm Developer Summit

40 Performance (Cont..) Reducing Memory bottleneck Additional memory Configure Capacity for each host machine Beyond this limit, least recently used instances get replaced I/O bottleneck Using RAID 3 or 4 for optimized storage and protection of data Avoid using data mounted via automount Developer Summit

41 Performance Caching The Java Server offers 2 scripts for the generation of Map and Globe caches The following properties can be set - Origin of the tiling scheme in map co-ordinatesordinates Tile size (default is 512x512) The display resolution in DPI (default is 96) Number of scales The tile size, DPI and scales control the pixel resolution in map units at each scale level Developer Summit

42 Agenda I. Components Overview and Architecture II. III. IV. Pre-Install Requirements Installation Overview Administration and Usage Server Management Troubleshooting V. Configuration Scenarios High Availability Scalability Performance Security Developer Summit

43 Configuration Scenarios - Security Ports to remember 135 RPC Port 3774 Authentication Listener Directory Server 8099 Internal Web Server 8399 Internal Web Server 6600 Internal X-Server 2099 Manager service Developer Summit

44 Security Communications DCOM SOM Client HTTP Web Services Web Apps TCP/IP D A T Web Tier A Application - Basic HTTP, - Digest HTTP, - Digital Certificate Authentication Network - Firewall - IPSec Application - Impersonation Network -Firewall - IPSec - Intrusion Detection OS - Data File Encryption - Intrusion Detection Application Developer Summit

45 Security - Firewalls Simplest solution Not considered secure by many organizations Client WS SOM Data Secure Network Developer Summit

46 Security - Firewalls All components inside DMZ Most secure solution Data must be replicated Internal Data Server Client WS SOM Data Data DMZ Secure Network Developer Summit

47 Firewalls (Cont..) Distribution across DMZ and Secure Network Output folder must be shared (one-way) across the firewall Not considered a good solution for ArcGIS Server Client WS SOM Data DMZ Secure Network Developer Summit

48 Firewalls (Cont..) WebServer and SOM inside the DMZ Not recommended for the ArcGIS Server Client WS SOM Data DMZ Secure Network Developer Summit

49 Firewalls (Cont..) Preferred setup with Reverse Proxy Acts on behalf of HTTP server, brokering requests to internal servers KB ID Client Reverse Proxy WS SOM Data DMZ Secure Network Developer Summit

50 Summary I. Architecture II. Difference of 9.2 from 9.1 III. IV. Installation Overview Tasks possible through the Manager V. Troubleshooting tips and tricks VI. Configuration Scenarios Developer Summit

51 Presentation materials PowerPoint presentation and code are posted on the conference web site EDN downloads and videos Developer Summit

52 Further questions? TECH-TALK TALK AREAS What: Further opportunity to discuss questions and concerns with presenters Where: Tech Talk Area 4 When: during the next 30 minutes ESRI Developers Network (EDN) website Developer Summit