chris derham wrote:
Can you expand a bit on the above ?
(That seems to be the only part which is really Windows-specific).
Such as, what "variable" are you talking about, defined where ?
So currently we set catalina_home and catalina_base, cd into
\bin and run
service install myApp
then ma
>
>
> Can you expand a bit on the above ?
> (That seems to be the only part which is really Windows-specific).
> Such as, what "variable" are you talking about, defined where ?
>
So currently we set catalina_home and catalina_base, cd into
\bin and run
service install myApp
then manually run
t
chris derham wrote:
...
safer to remove service. That way if we make any tweaks to the service
configuration, they would be propagated to all environments. (currently we
update the windows service to add a variable to tell the app which
environment it is running under)
Can you expand a bit on t
> Maybe you should be more precise as to what exactly you want to be able to
update mechanically.
Fair question. We have different environments - test, uat and prod. We want
the environments to be the same. We install multiple tomcat instances, so we
don't typically customize the tomcat install mu
chris derham wrote:
..
- 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
I do not p
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
applica
