BACKGROUND:
We're investigating migration from WebLogic 7 to Tomcat 5. As of
WebLogic 7, BEA separates out configuration info, their equivalent of
webapps, and other data into a separate directory, much like setting
CATALINA_BASE to a different directory does for Tomcat. BEA did this to
isolate patches and upgrades to the application code (in one directory)
from the web apps running on the server (in the other directory).
The nice thing is that this approach fit right in with the directory
standards for our servers, which separates out the application (the
server), the data (the webapps in this case), and the logs into three
separate directories: */apps/*, */data/*, */logs/*.
THE SETUP:
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}
I'd use the <Service name="*"> attribute to differentiate between
different Tomcat instances.
THE PROBLEM:
The only problem I can see with that approach is that it would limit me
to one <Service> per instance. Is that even problem? Would there be
times when you'd want more than one <Service> defined in a server.xml?
Any thoughts on this directory structure in general?
Thanks,
Kyle
_____
Kyle Adams | Java Developer | Gordon Food Service | 616-717-6162
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
