Upgrade Apache Tomcat manually (Windows)

Apache Tomcat is a mandatory component required to run the ESMC Web Console.

important

Important

If a custom version of Apache Tomcat is installed (manual installation of the Tomcat service), the subsequent ESMC Web Console upgrade via the All-in-one installer or via Components Upgrade Task is not supported.

Follow these instructions to upgrade Apache Tomcat manually (if you do not have the latest ESMC All-in-one installer):

Before upgrading

1.Ensure that Java/OpenJDK is up to date.

warning

Warning

Starting January 2019, Oracle JAVA SE 8 public updates for business, commercial or production use require a commercial license. If you do not purchase a JAVA SE subscription, you can use this guide to transition to a no-cost alternative and install one of listed supported Java editions.

important

Important

64-bit Java is required.

If you have multiple Java versions installed on your system, we recommend that you uninstall older Java versions (the oldest supported version is Java 8) and keep only the latest version of Java.

2.Check to see which version of Apache Tomcat is currently available.

a.Navigate to the Apache Tomcat installation folder:
C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\

b.Open the RELEASE-NOTES file in a text editor and check the version number (for example 7.0.90).

c.If a more recent supported version is available, perform an upgrade.

How to upgrade

1.Stop the Apache Tomcat service: Navigate to Start  > Services > right-click the Apache Tomcat service and select Stop.

Close Tomcat7w.exe if it is running in your system tray.

2.Back up the following files:

C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\.keystore
C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\conf\server.xml
C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties

If you are using a custom SSL certificate store in the Tomcat folder, also back up that certificate.

3.Uninstall the current version of Apache Tomcat.

4.Delete the following folder if it is still present on your system:

C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\

5.Download the latest supported version of the Apache Tomcat installer file (32-bit/64-bit Windows Service Installer) apache-tomcat-[version].exe from https://tomcat.apache.org.

6.Install the newer version of Apache Tomcat that you downloaded:

In case more Java versions are installed, select the path to latest Java during the installation.

When you are finished, deselect the check box next to Run Apache Tomcat.

7.Restore .keystore, server.xml, and custom certificates to their original location.

8.Open the server.xml file and make sure the keystoreFile path is correct (update the path if you upgraded to a higher major version of Apache Tomcat):

keystoreFile="C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\.keystore"

 

9.Make sure that HTTPS connection for Apache Tomcat for ESMC Web Console is set up properly.

10. Deploy the ESMC Web Console (Web Console installation - Windows).

11. Restore EraWebServerConfig.properties to its original location.

12. Run Apache Tomcat and set a correct Java VM:

a)Navigate to the folder C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\bin and run Tomcat9w.exe.

b)In the General tab set Startup Type to Automatic and press Start.

c)Click the Java tab, make sure Use default is deselected and Java Virtual Machine includes the path to jvm.dll file (see illustrated Knowledgebase instructions), and then click OK.

13. Connect to the ESMC Web Console and ensure that the program works correctly.

note

Note

See also the additional Web Console configuration for enterprise solutions or low-performance systems.

Troubleshooting

If you are unsuccessful in setting up an HTTPS connection for Apache Tomcat, you can skip this step and use an HTTP connection temporarily.

If the upgrade of Apache Tomcat fails, install your original version and apply the configuration from step 2.