I just thought I'd share my experience installing IPT into a Tomcat (5.5 - but experience suggests 6 or 7 wouldn't have helped) installed from Ubuntu packages.<div><br></div><div>In a nutshell: don't try it!</div>
<div><br></div><div>Ubuntu's packages (and I imagine Debian or any Debian-based system, though I haven't confirmed that) block the normal logging available from the stock Apache versions of Tomcat. What logging there is, gets diverted to the system log (where it is both poorly formatted - no newlines - and truncated). More logging becomes available if you edit 03catalina.policy:</div>
<div><br clear="all"></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><div><font face="'courier new', monospace" size="1">// These permissions apply to JULI</font></div></div></div><div>
<div><div><font face="'courier new', monospace" size="1">grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {</font></div></div></div><div><div><div><font face="'courier new', monospace" size="1"> permission java.security.AllPermission;</font></div>
</div></div><div><div><div><font face="'courier new', monospace" size="1">};</font></div></div></div></blockquote><div><br></div>but in itself that isn't enough to get logging for IPT, and the IPT install fails, but is unable to log the cause of the failure (which I think is the inability to write to the log, but never managed to prove).<div>
<br></div><div>The simple solution is to:</div><div>- download Tomcat 6 from Apache (<a href="http://tomcat.apache.org/download-60.cgi" target="_blank">http://tomcat.apache.org/download-60.cgi</a> - the tar.gz Binary version), </div>
<div>
- untar it anywhere (I put it in /opt),</div><div>- optionally create a symbolic link from /opt/tomcat to the /opt/apache-tomcat* directory you have just created</div><div>- stop your existing tomcat ,</div><div>- copy all .war files from /var/lib/tomcat*/webapps to the /opt/tomcat/webapps (you may want to copy the subdirectories from there too, if you have applications that store data in them)</div>
<div>- start your new server with /opt/tomcat/bin/startup.sh (setting the environment variable JAVA_OPTS first, with any values that must be passed - for instance, our GeoServer app requires "-D GEOSERVER_DATA_DIR=/opt/geoserver/data")</div>
<div><br></div><div>Don't forget to replace /etc/init.d/tomcat* with an appropriate script to start/stop the new tomcat using /opt/tomcat/bin/startup.sh & shutdown.sh<br>
<div>-- <br>derek broughton<br>
<div>Pointerstop Consulting (for OBIS Canada)</div><div><br></div></div></div>