Page History

Configure Tomcat 7

1. Configure tomcat-users.xml
   Open ${CATALINA_HOME}/conf/tomcat-users.xml with a text editor.  Create the following 2 uses:

   Code Block
   <role rolename="manager-script"/> <role rolename="manager-gui"/> <user username="script" password="XXXXXXXX" roles="manager-script,admin"/> <user username="gui" password="YYYYYYYY" roles="manager-gui,admin"/>

   • The script user will be used to deploy your application to the Tomcat server.
   • The gui user will be used to access the Tomcat Manager.
   Be sure to change the passwords to passwords of your choice.
   When you are satisified that everything is correct, save your changes.
2. Install the ojdbc14ojdbc6-1011.2.0.53.jar
   Install the ojdbc14ojdbc6-1011.2.0.53.jar in either the ${CATALINA_HOME}/lib or the ${CATALINA_HOME}/common/lib directory.  The ojdbc14ojdbc6-1011.2.0.53.jar has to go into only one directory.  If   
   
   If you do not have the ojdbc14ojdbc6-1011.2.0.53.jar, you can download the ojdbc14ojdbc6-1011.2.0.53.jar now and save it to your workstation.
   

   Anchor
   Configure context.xml Configure context.xml

3. Configure context.xml
   Open ${CATALINA_HOME}/conf/context.xml with a text editor.  
   1. For non-Windows systems, change the <context> tag to the following:

      Code Block
      <Context crossContext="true" useHttpOnly="false">

      For Windows systems, change the <context> tag to the following"

      Code Block
      <Context antiResourceLocking="true" crossContext="true" useHttpOnly="false">

      Note

      By setting antiResourceLocking to true, Tomcat will prevent any file locking. This will significantly impact startup time of applications, but allows full webapp hot deploy and undeploy on platforms or configurations where file locking can occur. If not specified, the default value is false. Please note that setting this to true has some side effects, including the disabling of JSP reloading in a running server: see Bugzilla 37668. Please note that setting this flag to true in applications that are outside the appBase for the Host (the webapps directory by default) will cause the application to be deleted on Tomcat shutdown. You probably don't want to do this, so think twice before setting antiResourceLocking=true on a webapp that's outside the appBase for its Host.

      Note

      By default, Tomcat 7 sets HttpOnly to false on all session cookies.  Since, by default, the HttpOnly flag will be set on session cookies, all client side scripts will be prevented   This prevents any client side script from accessing the session ID. DWR uses the session cookie (and the session ID) to protect against cross site scripting attacks.  With HTTPOnly set to false, DWR will start popping up “CSRF Security Error” dialogs. To prevent DWR from popping up “CSRF Security Error” dialogs, useHttpOnly must be set to true.

      Anchor
      add a resource definition add a resource definition

   2. Add the following Resource Definition anywhere beteen between the <context> and </context> tags:

      Code Block

      <Resource name="jdbc/MitsisDsMitsisDS" auth="Container" type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver" url="jdbc:oracle:thin:@//earth-vault-2.mit.edu:1523/sundev2sundev11" username="XXXXXXXX" password="YYYYYYYY" maxActive="20" maxIdle="10" maxWait="-1" removeAbandoned="true" removeAbandonedTimeout="3060" logAbandoned="true" /> <ResourceLink global="jdbc/MitsisDS" name="jdbc/MitsisDS" type="javax.sql.DataSource"/>

      If your project's JNDI name is something other than MitsisDS, then you must change MitsisDS in the above to your project's JNDI name.  If you don't know what JNDI name to use, your team leader can get it for you.
      Be sure to change the username and password.

      Note
      You can have more than 1 Resource Definition in your context.xml.  The only restriction is that each Resource Definition must have a unique name.  Also, for each new Resource Definition, you should also add a corresponding ResourceLink.  At the bottom of this page is an example of a context that contains multiple Resource Definitions.

      
      When you are satisified that everything is correct, save the changes.
4. Configure setenv.bat (setenv.bat is for Windows system.)
   For non-Windows systems use setenv.sh and convert the code below using the appropriate replacement for set.
   1. Open ${CATALINA_HOME}/bin/setenv.bat with a text editor.  If the setenv.bat file does not exist, create it.
   2. Add the following to setenv.bat:

      Code Block

      set CSFDIR=/usr/local/etc/csf set JAVA_HOME=/path/to/Java/jdk1.6.0_27 set PATH="%PATH%;/path/to/maven/apache-maven-2.2.1/bin" set MAVEN_OPTS=-Djavax.net.ssl.trustStore=/path/to/keystores/serverTrustStore.jks -Djavax.net.ssl.trustStorePassword=changeit" set CATALINA_OPTS=-Djavax.net.ssl.trustStorePassword=changeit -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/path/to/keystores/serverTrustStore.jks -Djavax.net.ssl.keyStore=/path/to/keystores/registrar.jks -Dlogs.dir=${user.home} set JAVA_OPTS=-server -Xmx1024m -Xms1024m -XX:MaxPermSize=1024m -DCSFDIR=%CSFDIR% echo MAVEN_OPTS=%MAVEN_OPTS% echo CATALINA_OPTS=%CATALINA_OPTS% echo JAVA_OPTS=%JAVA_OPTS% echo CSFDIR=%CSFDIR%

      Be sure to change the following:
      • /path/to/Java - the path to your Java JDK installation.
      • /path/to/maven - the path to your maven installation.
      • /path/to/keystores - the path to your truststore JKS and/or keystore JKS.
5. Test the Tomcat installation
   1. Open a cmd window, cd to ${CATALINA_HOME}/bin and start the tomcat server.
   2. Open a browse and go to the URL: http://localhost:8080/manager/html^{Image Removed}.
   3. When prompted for the username and password, use gui for the user name and enter the password that you choose in Step 1 above.
      If everything was done correctly, you will have the following page displayed:
      

Configure Tomcat 7 is now complete