Important locations

Tomcat is set up to run on several of the Glast unix servers. The following directories are used:

Symbolic links are used to point between different directories. Code is distributed among the following file systems:

All of the permanent code on AFS also exists in CVS module tomcat for configuration control and emergency recovery purposes. If any of this code is modified it should be committed back to CVS with a suitable comment. Since symbolic links can not be stored in CVS a special convention of using a SYMLINKS file in each directory has been adopted. Running the script ~/tomcat/scripts/symlinks will create/delete symlinks based on the contents of the SYMLINKS files. By default the symlinks script works on any directories at or below the current working directory.

Starting and Stopping servers

The tomcat servers are normally started automatically when the machine boots via cron jobs running under the glast account. The tomcat servers run under the control of the java service wrapper, which will automatically restart servers if they fail.

If it is necessary to manually restart a server, log in to the relevant machine as user glast, then issue the following command:

~/tomcat/scripts/tomcat restart

Checking Server Status

A glast monitoring application is used to check the status of the tomcat servers. It can be accessed from:

http://glast-ground.slac.stanford.edu/ServerMonitoring

Web Application Location

All production web applications are accessed via the glast-ground web site. If there is a problem with a web application you will need to know which tomcat server the application is running on. This information is stored in a oracle database under the GLASTGEN account. The easiest way to find out which server a particular application is (or should) be running on is to use the http://glast-ground.slac.stanford.edu/ServerMonitoring application.