ESOE Installation Additions - Debian

Peter Schober
Bradley Beddoes

Applicable versions
Beta 2

Applicable Debian Versions
Debian 4.0 "Etch"


The ESOE project team thanks Peter Schober from the University of Vienna for his time in forming this documentation.


The tomcat environment that comes as a default install with Debian has some quirks with how its setup. This document is to be read in addition to the standard ESOE installation guide.


It is assumed you're using tomcat5.5, and tomcat5.5-admin as packages via apt management. You may have tomcat5.5-webapps installed though this may cause you some issues with respect to update, if you can remove this package. We currently require you to DISABLE TOMCAT SECURITY in /etc/init.d/tomcat5.5

Directory Ownership

Ensure that the directories you have configured for and are owned by the user Tomcat55 before running esoestartup. This permission should remain for running the actual ESOE installation itself.

Special jar requirements

Due to the Jar layout on debian systems your database jar files for Oracle or Mysql must reside in $TOMCAT/common/lib you must also place a copy of log4j.jar in this location

Deployment of war files

Tomcat on Debian uses pre-exploded war files and context files by default so to try and simply deploy war files in the Debian Tomcat container will cause you a lot of grief, instead follow the instructions below (shutdown tomcat first).

ESOE Startup

  1. Copy esoestartup.war to /var/lib/tomcat5.5/webapps
  2. Create the file /usr/share/tomcat5.5/conf/Catalina/localhost/esoestartup.xml
  3. Edit esoestartup.xml as below:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/esoestartup" docBase="/var/lib/tomcat5.5/webapps/esoestartup.war" debug="0" privileged="true" allowLinking="true">

You should now run ESOE Startup as normal, once the process is complete shutdown tomcat.

ESOE Deployment

  1. If you have installed tomcat5.5-webapps remove the symlink for ROOT.xml in /usr/share/tomcat5.5./conf/Catalina/localhost - This will ensure no conflicts on restart.
  2. Copy ROOT.war to /var/lib/tomcat5.5/webapps
  3. Create the file /usr/share/tomcat5.5/conf/Catalina/localhost/ROOT.xml
  4. Edit ROOT.xml as below:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/" docBase="/var/lib/tomcat5.5/webapps/ROOT.war" debug="0" privileged="true" allowLinking="true">
  1. Copy spep.war to /var/lib/tomcat5.5/webapps
  2. Create the file /usr/share/tomcat5.5/conf/Catalina/localhost/spep.xml
  3. Edit spep.xml as below:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/spep" docBase="/var/lib/tomcat5.5/webapps/spep.war" debug="0" crossContext="true" privileged="true" allowLinking="true">
  1. Copy esoemanager.war to /var/lib/tomcat5.5/webapps
  2. Create the file /usr/share/tomcat5.5/conf/Catalina/localhost/esoemanager.xml
  3. Edit esoemanager.xml as below:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/esoemanager" docBase="/var/lib/tomcat5.5/webapps/esoemanager.war" debug="0" crossContext="true" privileged="true" allowLinking="true">
  1. Copy web.war to /var/lib/tomcat5.5/webapps
  2. Create the file /usr/share/tomcat5.5/conf/Catalina/localhost/web.xml
  3. Edit web.xml as below:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/web" docBase="/var/lib/tomcat5.5/webapps/web.war" debug="0" privileged="true" allowLinking="true">

You should now restart Tomcat and all should operate as normal from this point.


We aim to continually improve this documentation set to make it as easy as possible to configure ESOE on Debian. We welcome any comments or additions you may have on the ESOE users mailing list at any time.