Tomcat .war deployment and rollback

deploymenttomcat

I have a ROOT.war file which I used to deploy version 1 of my web site. I now rename this file to be ROOT_v1.war and set it aside. Then I do some changes and create a new ROOT.war file and deploy it.

If I want to do a rollback, will it be enough to just rename and copy ROOT_v1.war back to the server?

Or do I need to update its date? Or do the dates that count are those of the files inside it?

Best Answer

To be sure, I would undeploy the application, check my tomcat/webapps/ folder for any traces of the application having been left & then deploy the 'original' application.

Related Solutions

Iis – Strategy for zero downtime rollouts: what about the DB

Nobody has a great answer for this. You have to make backwards-compatible schema changes, however hard that may be.

Typically this means that your app can't just depend on one schema version, but needs to be able to support multiple schemas during the transition. (Your transactions should update both schemas, etc.)

Note that even NoSQL schema-less datastores don't solve this problem, but rather require you to solve it, in much the same way: if you have a key with N values, and you need to add a new value, your app needs to deal with the possibility that the key might not be updated yet.

Good luck!

Tomcat – Auto-deploy WAR to arbitrary URL on Tomcat

Thanks to a mailing list response, I found a way to do what I want.

The solution is to not use the auto-deploy feature for WAR files in "/var/lib/tomcat6/webapps", but instead uploading the WAR file to another directory. Then one must explicitly create a context configuration file matching the URL path, e.g. "/var/lib/tomcat6/conf/Catalina/localhost/sub#url.xml" with this content:

<Context docBase="/path/to/war/arbitrary-filename.war" />

Best Answer

Related Solutions

Iis – Strategy for zero downtime rollouts: what about the DB

Tomcat – Auto-deploy WAR to arbitrary URL on Tomcat

Related Topic