[KB7088] Install the ESET PROTECT Web Console using JDK (Windows)

Issue

Details


Click to expand


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, use this guide to transition to a no-cost alternative. Only installations on Windows are affected.


Solution


I am a Linux user

See the related articles on installing Java on:


Supported versions

Recommended versions by ESET

Only long-term support (LTS) Java/JDK versions are supported:

Supported Java/JDK version ESET product
8 ESET PROTECT On-Prem 8.x
11 ESET PROTECT On-Prem 8.x
17
ESET PROTECT On-Prem 8.x with additional manual settings
ESET PROTECT On-Prem 9.x
ESET PROTECT On-Prem 10.x
ESET PROTECT On-Prem 11.x
21
ESET PROTECT On-Prem 11.x
 
Fix the "Failed to load data" error

Restart the Apache Service after every change

You need to restart the Apache Service after every change in the .exe or .bat files.

  1. Press the Windows key on your keyboard and type Service.

  2. Right-click Apache Tomcat from the list on the right side.

  3. Click Restart.

Option 1
  1. Navigate to the Apache Tomcat folder, and in the bin folder, locate tomcat9w.exe.

  2. Run the tomcat9w.exe file. Click the Java tab and add the following values to the Java 9 Options field:

    --add-opens=java.base/java.util=ALL-UNNAMED
    --add-opens=java.base/java.util.concurrent=ALL-UNNAMED

The Java 9 Options field now includes the following values:

--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED

  1. Click OK.
Option 2
  1. Navigate to the Apache Tomcat folder and in the bin folder, locate and edit catalina.bat.

  2. Change the values in section rem Configure JAVA 9 specific start-up parameters

    set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.base/java.lang=ALL-UNNAMED"
    set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.base/java.io=ALL-UNNAMED"
    set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED"

into

set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.base/java.lang=ALL-UNNAMED"
set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.base/java.io=ALL-UNNAMED"
set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.base/java.util=ALL-UNNAMED"
set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.base/java.util.concurrent=ALL-UNNAMED"
set "JDK_JAVA_OPTIONS=%JDK_JAVA_OPTIONS% --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED"
Option 3
  1. Navigate to the Apache Tomcat folder and in the bin folder, locate and edit service.bat.

  2. Navigate to the line s --JvmOptions9 and edit it in the following way:

--JvmOptions9 "--add-opens=java.base/java.lang=ALL-UNNAMED#--add-opens=java.base/java.io=ALL-UNNAMED#--add-opens=java.base/java.util=ALL-UNNAMED#--add-opens=java.base/java.util.concurrent=ALL-UNNAMED#--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED" ^

  • Apache Tomcat:
    • ESET PROTECT On-Prem: We recommend installing the latest Apache Tomcat 9.x.

  • JDK

If you have multiple Java versions installed on your system, we recommend that you uninstall the earlier Java versions and only keep the latest version.

Ensure that Java, ESET PROTECT, and Apache Tomcat have the same bitness (32-bit or 64-bit for later versions).

MDM scheduled for End of life

MDM mobile device enrollment using a QR code is not functional for JDK 11.0.1 and OpenJDK 11.0.1. MDM mobile device enrollment using a QR code is only functional for Amazon Corretto 8u192. 

ESET PROTECT On-Prem Mobile Device Management component is scheduled for End of Life

I am installing the ESET PROTECT Server from an All-in-one installer.


Install Amazon Corretto (JDK)

Click to expand
Amazon Corretto 11, 17 and 21 (JDK)

This procedure describes the Amazon Correto 17 or 21 install process.

A similar procedure can be applied when installing other supported versions of Amazon Corretto.

  1. Download the Windows .msi installation file for Amazon Corretto 17 or for Amazon Corretto 21.

  2. Double-click the .msi file to start the Installation Wizard.

  3. Follow the steps in the wizard.

    You have the option of setting a custom installation path. By default, Amazon Corretto 17 is installed at C:\Program Files\Amazon Corretto\. If you set a custom path, make a note of it for the next step.

  4. When the Installation Wizard is finished, set the JAVA_HOME and PATH environment variables.

    Set JAVA_HOME to the installation location, noting that the directory contains the currently installed version. See the following examples for versions 17 and 21.

  • Version 17: Set JAVA_HOME as C:\Program Files\Amazon Corretto\jdk17.0.10_7. Add %JAVA_HOME%\bin to the current PATH variable.
  • Version 21: Set JAVA_HOME as C:\Program Files\Amazon Corretto\jdk21.0.2_13. Add %JAVA_HOME%\bin to the current PATH variable.
Build numbers may change

Each build (17 and 21) contains build numbers in the "version" folder under C:\Program Files\Amazon Corretto. These numbers may change in the future (when a more recent build is released).

  1. Verify the installation by running java -version in a command prompt. You should see the following output.

    Version 17
    openjdk version "17.0.10" 2024-01-16 LTS
    OpenJDK Runtime Environment Corretto-17.0.10.7.1 (build 17.0.10+7-LTS)
    OpenJDK 64-Bit Server VM Corretto-17.0.10.7.1 (build 17.0.10+7-LTS, mixed mode, sharing)
    
    Version 21
    openjdk version "21.0.2" 2024-01-16 LTS
    OpenJDK Runtime Environment Corretto-21.0.2.13.1 (build 21.0.2+13-LTS)
    OpenJDK 64-Bit Server VM Corretto-21.0.2.13.1 (build 21.0.2+13-LTS, mixed mode, sharing)

Migrate your existing ESET PROTECT Web Console to use JDK

You can migrate your existing Web Console from Oracle Java JDK to an alternative one. Select one of the migration scenarios below based on your current Apache Tomcat version.


Migration scenario for Tomcat version 7.0.90 and later

This migration scenario does not require the reinstall of Apache Tomcat.

  1. Navigate to the Apache Tomcat location (for example, C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7w.exe)

  2. In the Apache Tomcat 7 Properties window, click the General tab and click the Stop button to stop the Apache Tomcat service.

  3. Uninstall your current JDK.

  4. Install your desired JDK.

  5. Go back to the Apache Tomcat Properties window and click the Java tab.

  6. Under the Java Virtual Machine path, select the correct path to the jvm.dll file based on the JDK. (for example, for Amazon Corretto, C:\Program Files\Amazon Corretto\jdk11.0.7\bin\jvm.dll)

  7. Go back to the General tab, and click Start to start the Apache Tomcat service.

  8. Verify that you can log in to your Web Console.


Migration scenario for Tomcat version 7.0.88 and earlier

This migration scenario requires the reinstall of Apache Tomcat.

  1. Back up the necessary files:
    C:\Program Files\Apache Software Foundation\Tomcat 7.0\.keystore
    C:\Program Files\Apache Software Foundation\Tomcat 7.0\conf\Server.xml
    C:\Program Files\Apache Software Foundation\Tomcat 7.0\conf\Tomcat-users.xml
    C:\Program Files\Apache Software Foundation\Tomcat 7.0\conf\Serverinfo.properties
    C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties

  2. Download and run the JDK installer.

  3. To change which JDK is used by Apache Tomcat, you must reinstall Apache Tomcat.

  4. If you are running more than Web Console on your instance of Apache Tomcat, we recommend that you check the official Apache Tomcat upgrade/migration documentation.

  5. If you use a custom SSL certificate stored in the Tomcat folder, back up the certificate.

  6. Uninstall the current version of Apache Tomcat.

  7. Delete the following folder if it is still present in your system:

    C:\Program Files\Apache Software Foundation\Tomcat 7.

  8. Run the Apache Tomcat installer from the ESET PROTECT All In One installers folder. During the installation, select the path to your JDK you intend to use instead of the Java SE. (for example, C:\Program Files\Amazon Corretto\jre8).

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

  10. Verify that the Apache Tomcat Service is not running.

  11. Copy the era.war file from the installers folder to the Apache Tomcat web applications folder: click StartApache TomcatTomcat Program Directory and open the webapps folder (on most Windows operating systems – C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps)

  12. Allow a few minutes for the file extraction and Web Console installation. The installation will run silently, but you can verify a successful installation by the presence of the era folder inside the webapps folder.

  13. If you run the Web Console (Apache Tomcat) on a different computer than the Server component, restore the backed-up EraWebServerConfig.properties file to its original location.

  14. Verify that the Apache Tomcat is using the JDK you selected. To do so, click StartAll ProgramsApache TomcatMonitor Tomcat. In the Java tab under Java Virtual Machine, there should be the path to the JDK you selected.

  15. You can now start the Apache Tomcat service and verify that the Web Console is running without issues.