Return-Path: 
 <tomcat-user-return-91998-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 376 invoked from network); 5 Feb 2004 16:25:06 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 5 Feb 2004 16:25:06 -0000
Received: (qmail 46939 invoked by uid 500); 5 Feb 2004 15:34:07 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 46877 invoked by uid 500); 5 Feb 2004 15:34:07 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 46781 invoked from network); 5 Feb 2004 15:34:06 -0000
Received: from unknown (HELO expredir3.cites.uiuc.edu) (128.174.5.186)
  by daedalus.apache.org with SMTP; 5 Feb 2004 15:34:06 -0000
Received: from shalom.cso.uiuc.edu (shalom.cso.uiuc.edu [130.126.112.169])
	by expredir3.cites.uiuc.edu (8.12.10/8.12.10) with ESMTP id i15FY8c6017040
	for <tomcat-user@jakarta.apache.org>; Thu, 5 Feb 2004 09:34:08 -0600 (CST)
Date: Thu, 5 Feb 2004 09:34:08 -0600 (CST)
From: Milt Epstein <mepstein@uiuc.edu>
X-X-Sender: mepstein@shalom.cso.uiuc.edu
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: RE: context configuration file being overwritten
In-Reply-To: <399E1F52E73BD41194A800D0B74A08AB0340067B@skipper.cincom.com>
Message-ID: <Pine.GSO.4.58.0402050017360.20935@shalom.cso.uiuc.edu>
References: <399E1F52E73BD41194A800D0B74A08AB0340067B@skipper.cincom.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

On Wed, 4 Feb 2004, Cox, Charlie wrote:

> > From: Milt Epstein [mailto:mepstein@uiuc.edu]
> > Sent: Wednesday, February 04, 2004 2:47 PM
[ ... ]
> > > Have you tried using CATALINA_BASE and CATALINA_HOME to separate
> > > your webapps/configuration(BASE) and your tomcat
> > > installation(HOME)?  Maybe this would serve your needs instead
> > > of symbolic links.
> > [ ... ]
> >
> > Thanks for the response.
> >
> > I am aware of using CATALINA_HOME/CATALINA_BASE, but I don't think
> > that would serve my needs better.  That's more for when you're
> > going to have multiple Tomcat instances, and you want to eliminate
> > redundancy and reduce the amount of total space used.  And it
> > still has problems when it comes to upgrades.
>
> Actually I am using CATALINA_HOME/CATALINA_BASE for a single
> instance for the ease of upgrading. I have separated /webapps,
> /conf, and /temp from /bin, /common, /shared, and /server. The only
> issue that I see upon upgrade is that I need to copy my libs in
> /common and /shared if I install the new version to a new directory
> and change CATALINA_HOME appropriately. I'm interested to hear what
> other issues you see with this as /conf wouldn't be affected by a
> new tomcat point release to CATALINA_HOME.
[ ... ]

Well, with the caveats that I don't have extensive experience with
different Tomcat setups and I've only just come up with my current
setup (so it's kind of a work in progress) ...

The setup I'm trying now has:

1. the tomcat distrib under /usr/local
   (e.g., /usr/local/jakarta-tomcat-5.0.18)
2. /usr/local/tomcat as a symbolic link to the "current" distrib
3. all my webapps, with their associated context configuration files,
   under /usr/local/webapps

So to get things working, all I do is copy the context configuration
files to the appropriate Tomcat directory (it used to be
<tomcat>/webapps in Tomcat 4, but in 5 it's apparently
<tomcat>/conf/<engine>/<host>).  (I was hoping to use symbolic links,
but then I ran into the problem I posted about.)

When I upgrade Tomcat versions, all I do is drop the new distrib in,
change the /usr/local/tomcat link, copy the context configuration
files in, and voila!, I'm up and running.

Maybe the differences are minor as compared to your setup, but I think
they are there.  For example, you may have to re-copy conf and/or
webapps (I believe there can be changes in what's under those
directories on new point releases).  Basically you don't have to worry
about splitting the distrib up between $CATALINA_HOME and
$CATALINA_BASE, and any potential issues related to that that could
come up with an upgrade to a new version.

Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org