Changes between Initial Version and Version 1 of TomcatConfig


Ignore:
Timestamp:
Aug 11, 2010, 2:46:05 PM (14 years ago)
Author:
Kevin Milner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TomcatConfig

    v1 v1  
     1= OpenSHA Tomcat Configuration =
     2
     3OpenSHA uses [http://tomcat.apache.org/ Apache Tomcat] as it's [http://www.oracle.com/technetwork/java/index-jsp-135475.html Java Servlet] container.
     4
     5== Configuration File ==
     6
     7The 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!
     8
     9For example:
     10{{{
     11[8:opensha] /usr/local/tomcat/default/webapps/OpenSHA/WEB-INF: svn up
     12At revision 6959.
     13[8:opensha] /usr/local/tomcat/default/webapps/OpenSHA/WEB-INF: cp conf/web.xml web.xml
     14}}}
     15
     16== Parallel !Dev/Production Setup ==
     17OpenSHA is in constant development. To provide stability for released applications, while still allowing us to develop the project, there are two parallel Tomcat contexts.
     18
     19Applications 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.
     20
     21Each context also runs RMI services on different ports.
     22
     23=== Production Context ===
     24The production context uses themost recent release branch.
     25* URL: http://opensha.usc.edu:8080/OpenSHA
     26* path: opensha.usc.edu:/usr/local/tomcat/default/webapps/OpenSHA/WEB-INF
     27* RMI port: 1099
     28
     29=== Development Context ===
     30The development context uses the trunk.
     31* URL: http://opensha.usc.edu:8080/OpenSHA_dev
     32* path: opensha.usc.edu:/usr/local/tomcat/default/webapps/OpenSHA_dev/WEB-INF
     33* RMI port: 1098
     34This gets updated automatically every night as part of the nightly build process.