tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Stewart <bstew...@iname.com>
Subject Re: [OT Upgrade: tomcat8w.exe //ES//example - dump Java Options and other information to tomcat9
Date Tue, 04 Aug 2020 22:59:40 GMT
On Tue, Aug 4, 2020 at 4:01 PM Christopher Schultz wrote:

I have a client who runs our product on Windows (we usually run it on
> Linux) and there are 2-4 separate Tomcat-based services on each node,
> so they have "Tomcat 8.5.x for FOO", "Tomcat 8.5.x for BAR", etc. in
> their service descriptions. Can they use your installer to upgrade
> just one of those with a new Tomcat version?
>

The alternative installer can only upgrade Tomcat instances it installs.
(It can't upgrade instances installed using Apache's installer or manual
installations; it doesn't know about those.)

The process in your case would be something like this:

1. Document the Tomcat service installation details for the instance you
want to replace and back up its config files.

2. Remove it (reverse whatever process you used to install, whether Apache
installer, manual, etc.).

3. Install using alternate installer; e.g.:

apache-tomcat-a.b.c-setup.exe /instance="FOO"

4. Update the config files, copy application server files, etc.

See the documentation - https://github.com/Bill-Stewart/ApacheTomcatSetup -
for details. (Without /instance it installs a default instance - i.e.,
default directory of "\Program Files\Apache Tomcat", "Apache Tomcat" as the
service name, etc.)

To upgrade (in general):

1. Touch (update timestamps of) config files you don't want the installer
to overwrite.

2. Run the above install commands with the new version of the installer.
Don't forget the /instance parameter if you used it to install initially
(otherwise, the installer will install or upgrade the default instance).

Note that each instance installed using the alternate installer (default or
otherwise) installs to a separate directory and appears as a separate entry
in the Windows "installed application" list. (This is typically the
expected behavior for application installations on Windows machines.)

I certainly don't claim that the alternative installer is suitable for all
applications and configurations, but for fairly common use cases on Windows
machines, the two-step upgrade process noted above (I think) is pretty
simple.

Bill

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message