tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Frey <rainer.f...@inxmail.de>
Subject Re: Best practice to upgrade (redeploy) .war files
Date Fri, 03 Sep 2010 06:53:18 GMT
On Monday 30 August 2010 12:55:19 Rainer Frey wrote:
> Hi,

It's not normally my style, but is there really no feedback on this topic?
Does anyone use explicit hot deployment with Tomcat Manager in production? How 
do you actually upgrade deployed applications? 
 
And if you use cold deployment only, how do you avoid downtime for other apps? 
Do you really use one Tomcat  instance per app?

I'd really like to hear some input / experiences about production use with 
several applications with independent release/deploy cycles.

Thanks again
Rainer

> 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?
> 
> Thanks
> Rainer

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


Mime
View raw message