| 1 | = OpenSHA Tomcat Configuration = |
| 2 | |
| 3 | OpenSHA 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 | |
| 7 | 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! |
| 8 | |
| 9 | For example: |
| 10 | {{{ |
| 11 | [8:opensha] /usr/local/tomcat/default/webapps/OpenSHA/WEB-INF: svn up |
| 12 | At 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 == |
| 17 | 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. |
| 18 | |
| 19 | 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. |
| 20 | |
| 21 | Each context also runs RMI services on different ports. |
| 22 | |
| 23 | === Production Context === |
| 24 | The 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 === |
| 30 | The 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 |
| 34 | This gets updated automatically every night as part of the nightly build process. |