All,

I have been reading "Continuous Integration: Improving Software Quality and
Reducing Risk". It recommends having an automated installer for all
deployments, so that the everything is the same on all environments. We
typically have multiple instances of tomcat, allowing us to segregate
applications and start|stop instances in isolation. We currently set this up
manually, but I am trying to work out if we could create an automated
deployment tool such that at deployment it would

   - Check for existing installation - if one found
   - shutdown existing service
      - remove existing service
      - remove existing tomcat instance
   - deploy new war, along with appropriate configuration files
   - register service
   - startup service

To be clear, the script could assume that tomcat was already installed - say
drop out if no CATALINA_HOME env variable set. I planned to feed it a
property file with username/password/db connection string, so we could take
the same installer and run on multiple environments without compromising the
security of passwords etc.

I can't seem to find anything included in tomcat to do this. So is the
"expected" method of deployment to manually configure multiple tomcat
instances, and then just deploy the war by hand/script? Am I missing some
key piece of software/knowledge?

I was looking at writing a script in say NSIS or something similar. Anybody
have any experience of this, or suggest a better way of doing it?

Thanks for any help

Chris

Reply via email to