Operational Management

This chapter contains a short listing of recommendations for operational management.

•Adjust the count of your ArcGIS Server service instances to the count of requests on your system. See chapter: Optimizing Performance - Impact of Minimum and Maximum Number of Instances.

•Review and set the recycling periods of your map services. Consider that the map service for dynamic printing needs different settings depending on the count of print requests. See chapter: Optimizing Performance - Impact of Minimum and Maximum Number of Instances and Dynamic Printing Setup

•Restart your servlet engine (Apache Tomcat) each day using batch processing.

•Check if a SOM restart in combination with the Tomcat restart using batch processing might be useful. For the restart of your Server Object Manager, be sure to use tools or scripts that guarantee a clean startup in the right order. Some links that might be helpful are: http://arcscripts.esri.com/details.asp?dbid=16293 and http://arcscripts.esri.com/details.asp?dbid=15439

•Monitor your ArcGIS Server services and WebOffice 10 R3 projects. See chapter: Monitoring WebOffice Projects and http://arcscripts.esri.com/details.asp?dbid=15335 for details.

•Secure your application. See chapter: Security for details.

•Update your OS and other components influencing the application manually. Deactivate automatic update functions See chapter: Windows Update.

For high-end systems we can recommend the following settings to stabilize your web applications:

•Define the timeout to avoid uncontrolled growth of ArcObjects threads. See chapter: Tomcat COM Settings.

•Set the PermGen Max Memory to 1024MB. See chapter: Tomcat Memory Settings.

•Deactivate session persisting. See chapter How to deactivate persisting of Sessions.

•Set the Tomcat memory to initially 4GB and maximum 12GB (requires an appropriate server). See chapter: Tomcat Memory Settings.