[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tomcat-user
Subject:    Re: Best practice to upgrade .war files
From:       Rainer Frey <rainer.frey () inxmail ! de>
Date:       2010-08-30 11:35:55
Message-ID: 201008301335.55962.rainer.frey () inxmail ! de
[Download RAW message or body]

On Monday 30 August 2010 13:13:03 Ozgur Ozdemircili wrote:
> On Mon, Aug 30, 2010 at 12:55 PM, Rainer Frey <rainer.frey@inxmail.de>wrote:
> > Hi,
> > 
> > what is the best practice to replace a webapp with a newer version in
> > production?
> > 
> > I'm using Tomcat 6.0.29, with unpackWARs="true" autoDeploy="false". All
> > Webapps reside in appBase, some have a machine-specific context
> > descriptor, that I manually copy to conf/Catalina/localhost.
> > 
> > I use the Tomcat Manager (via HTML-Interface) to deploy applications.
> > What is
> > the recommended way to upgrade a webapp to a newer version (same war
> > name, same desired context path)?
> > 
> > The HTML manager has no "redeploy" option. "deploy" is not possible as
> > the context already exists. I tried to put the new war file into
> > appBase, and use
> > reload, but that won't update the expanded directory to the new war file.
> > 
> > What I did is:
> >  * undeploy
> >  * copy new war file
> >  * deploy
> > 
> > This is cumbersome as I have to switch forth and back between manager and
> > file
> > operations.
> > 
> > Is there a better way?

> After trying all sorts of deploy types I have found the best, simplest and
> pain-free deploy in :
> 
> - Stop tomcat

I refine myself: what is best practice to *hot* deploy upgraded war file? I 
don't want to influence other webapps.

Rainer

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

[prev in list] [next in list] [prev in thread] [next in thread]