= OpenSHA Tomcat Configuration =

OpenSHA uses [http://tomcat.apache.org/ Apache Tomcat] as it's [http://www.oracle.com/technetwork/java/index-jsp-135475.html Java Servlet] container.

== Configuration File ==

The Tomcat configuration file can be found in the repository at [source:trunk/conf/web.xml conf/web.xml]. Note: edits to this file won't be automatically reflected...you must replace the existing web.xml file with conf/web.xml when making changes!

For example:
{{{
[8:opensha] /usr/local/tomcat/default/webapps/OpenSHA/WEB-INF: svn up
At revision 6959.
[8:opensha] /usr/local/tomcat/default/webapps/OpenSHA/WEB-INF: cp conf/web.xml web.xml
}}}

== Parallel !Dev/Production Setup ==
OpenSHA is in constant development. To provide stability for released applications, while still allowing us to develop the project, there are two parallel Tomcat contexts.

Applications use the [source:trunk/src/org/opensha/commons/util/ServerPrefs.java ServerPrefs] and [source:trunk/src/org/opensha/commons/util/ServerPrefUtils.java ServerPrefUtils] classes to determine which URLs to use.

Each context also runs RMI services on different ports.

=== Production Context ===
The production context uses themost recent release branch.
* URL: http://opensha.usc.edu:8080/OpenSHA
* path: opensha.usc.edu:/usr/local/tomcat/default/webapps/OpenSHA/WEB-INF
* RMI port: 1099

=== Development Context ===
The development context uses the trunk.
* URL: http://opensha.usc.edu:8080/OpenSHA_dev
* path: opensha.usc.edu:/usr/local/tomcat/default/webapps/OpenSHA_dev/WEB-INF
* RMI port: 1098
This gets updated automatically every night as part of the nightly build process.