On Wed, Oct 20, 2004 at 10:02:57AM -0400, Kyle Adams wrote:
: I'd like to do the same thing with Tomcat using CATALINA_BASE, like
: so:
:
: CATALINA_HOME -> */apps/tomcat
: CATALINA_BASE -> */data/tomcat/${service.name}
: [snip]
: Would there be
: times when you'd want more than one <Service> defined in a server.xml?
None that I can think of. (Is that even permitted?)
: Any thoughts on this directory structure in general?
Yes: separate CATALINA_HOME from CATALINA_BASE. You'll have a cleaner
upgrade and management path that way, not to mention your directory
structure as-is implies the webapps are bound to Tomcat (which isn't
necessarily true). There are other benefits, too.
I use something along these lines:
## Tomcat binaries
/opt/...../tomcat-<version>
## latest Tomcat, symlink to tomcat-<version>;
## referenced by per-instance scripts as CATALINA_HOME
/opt/...../tomcat
## per-app dir, aka CATALINA_BASE. Each of these gets its own
## server.xml, work dir, etc.
/somewhere/else/webapps/app1/
/somewhere/else/webapps/app1/bin ## management scripts
/somewhere/else/webapps/app1/webapps ## web apps
/somewhere/else/webapps/app1/ .... ## etc, etc, etc
This structure lets me migrate between several Tomcat versions without
touching the app itself, except perhaps the definition of CATALINA_HOME
in the start script.
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
