The AppServer.properties file contains the defaults for the ArcIMS Application Server and is located at:
Windows: <ArcGIS Installation Directory>\ArcIMS\AppServer
UNIX: $AIMSHOME/Middleware/Application_Server
This file defines the following ArcIMS Application Server properties.
connectorPort=5300
The ArcIMS Application Server port on which the connector connects and communicates. Different port numbers are required if you are running more than one Application Server. For more information, see Configuring ArcIMS ports.
regPort=5353
The ArcIMS Application Server port on which the ArcIMS Monitor, ArcIMS Tasker, and ArcIMS Spatial Servers register. For more information, see Configuring ArcIMS ports.
defaultTaskerPort=5060
The default ArcIMS Tasker port on which the ArcIMS Application Server expects ArcIMS Tasker to be registered. For more information, see Configuring ArcIMS ports.
debug=False
Setting the debug value to True turns on the ArcIMS Application Server debug logging that contains all Application Server communications. Logging can be either to a console window or to file. To view in file format, you must also set the logToFile property to True. On Windows, to view the ArcIMS Application Server status in a console window, check that the ArcIMS Application Server service has the "Allow Service to Interact with Desktop" setting enabled. For more information, see Enabling full verbose logging.
logToFile=False
Setting the logToFile value to True writes the ArcIMS Application Server debug logging to a file. A log file named AppServer_XXXXXXXXX.log is written to the log directory of Application Server's working directory. For more information, see Enabling full verbose logging.
LogSize=5
Size of debug log file in megabytes. After a debug log reaches this size, it will start a new file. When log files get too large they are difficult to open, difficult to interpret, and may affect performance. The maximum log file size defaults to 5 megabytes. For more information, see Enabling full verbose logging.
connectionQueueSize=500
minConnections=20
The minimum number of connections open and active for connectors to connect to the ArcIMS Application Server. If more connections are required at run time, the ArcIMS Application Server will increase connections as required. For more information, see Setting connections to the ArcIMS Application Server.
maxConnections=2000
The maximum number of connections that can be used by connectors to connect to the Application Server. Once this limit is reached, requests for further connections are refused until previous connections are freed up. For more information, see Setting connections to the ArcIMS Application Server.
timeout=60
The time period in seconds that the ArcIMS Application Server waits on an ArcIMS Spatial Server to respond to a client request. This figure should be tuned to synchronize with the maximum response time needed for service requests. The minimum value allowed is 15 seconds. If you set a value lower than the minimum, the ArcIMS Application Server will automatically use a value of 15 seconds. For more information, see Setting timeouts.
metadataPublishTimeout=0
The time period in seconds that ArcIMS Application Server waits on an ArcIMS Spatial Server to respond to requests for publishing metadata documents or administering the metadata service. A timeout value 0 is interpreted as infinity. For more information, see Setting timeouts.
extendedTimeout=300
The time period in seconds the Application Server waits on a Spatial Server to start or refresh a service. The extendedTimeout value should be tuned to synchronize with the maximum time that the Spatial Server requires to get itself set up with the data sources and related tasks in setting up a new service. For more information, see Setting timeouts.
recoveryTimeout=300
When a timeout, extendedTimeout, or metadataPublishTimeout is reached, the Spatial Server instance where the timeout occurred is no longer available until it can be recovered. Once the Spatial Server instance is marked for recovery, the recoveryTimeout stopwatch starts. If after the specified time period the Spatial Server instance has not responded, the Application Server sends requests to reset the instance. If this is not successful, after the specified time period for recoveryTimeout, the Application Server restarts the entire Spatial Server process. Therefore, the maximum time the recovery process takes is two times the number of seconds specified for recoveryTimeout. For more information, see Setting timeouts.
serverConnectionPingInterval=1800
The time interval in seconds for when the Application Server pings the Spatial Server and its Server instances at lease once, if inactive. The value of this parameter must be set based on firewall settings to drop inactive persistent connections. A value of 0 seconds implies pinging is not required. For more information, see Setting an interval to keep firewalls open.
waitAfterInterrupt=15
When a request times out, the Application Server sends a message to interrupt the Spatial Server. By default, the Application Server waits 15 seconds after the request times out. For more information, see Setting timeouts.
waitAfterReconnect=5
When the Application Server sends a message to the Spatial Server to interrupt a request, only the instance the request is running on gets restarted. If the instance cannot be reconnected, the Application Server will send a message to restart the entire Spatial Server process. For more information, see Setting timeouts.
networkDipReconnectWait=30
When the Application Server detects a network dip, ArcIMS Monitor waits for this time interval before reconnecting Spatial Servers. A network dip occurs when the network goes down for a small period of time and comes back up. ArcIMS Monitor periodically pings the Application Server. A dip is detected when a ping succeeds after failed ping(s) and in the meantime the Application Server has not restarted. Following a network dip and the networkDipReconnectWait time period, ArcIMS Monitor starts the reconnection process. Reconnection is done to repair bad network connections between the Application Server and Spatial Servers and to avoid replacement of Spatial Servers, which takes more time. For more information, see Setting timeouts.
workingDirectory
Location of the directory where the ArcIMS Application Server reads and writes serialized files. By default, this location is the same directory where the AppServer.properties file resides. You can change this location to another directory on your system.
Windows: workingDirectory=C/:Program Files/ArcGIS/ArcIMS/AppServer
UNIX and Linux: workingDirectory=/<ArcGIS Installation Directory>\ArcIMS/Middleware/Application_Server
|
preferenceFile
Used to store site preferences for the ArcIMS Service Administrator. By default, this location is the same directory where the AppServer.properties file resides. You can change this location to another directory on your system. For more information, see Setting site properties.
Windows: preferenceDirectory=C/:Program Files/ArcGIS/ArcIMS/AppServer/preferenceFile=sitePreferences.properties
UNIX and Linux: preferenceDirectory=/<ArcGIS Installation Directory>\ArcIMS/Middleware/Application_Server/sitePreferences.properties
|
startup.recyclableServers=ImageServer:ArcMap
Used to specify which Virtual Servers you would like ArcIMS to recycle. By default, only ArcMap Image Virtual Servers are recylced. List the types of Virtual Servers you would like recycled in a comma-separated list. Valid values are ImageServer:ArcMap, ImageServer, FeatureServer, QueryServer, GeocodeServer, ExtractServer, MetadataServer. For more information, see Managing Spatial Server recycling.
The following example specifies the ArcMap Image, Image, and Query Virtual Server types should be activated for recycling:
|
startup.recyclableServers=ImageServer:ArcMap,ImageServer,QueryServer
|
startup.singleThreadedServers=ImageServer:ArcMap
Used to specify a comma-separated list of Virtual Server types that use a single instance per Spatial Server. By default, only ArcMapServer is set as single-threaded. You can set other Virtual Server types to be single-threaded as well. It is recommended you set only ArcMap Server as a single-threaded server. Valid values are ImageServer:ArcMap, ImageServer, FeatureServer, QueryServer, GeocodeServer, ExtractServer, MetadataServer.
The following example specifies the ArcMap Image and Image Spatial Server types should be set as single-threaded:
|
startup.recyclableServers=ImageServer:ArcMap,ImageServer
|
