USER MANUALS

Supported Java Development Kits (JDK)

The installers of the Denodo Platform and the Solution Manager, for Windows and for Linux, include the OpenJDK version 17 LTS - HotSpot provided by the Eclipse Adoptium project (continuation of the project AdoptOpenJDK), which provides runtime binaries that are high performance, enterprise-caliber, cross-platform, open-source licensed, Java SE TCK-tested and compliant for general use across the Java ecosystem.

If you are installing the Denodo Platform on an operating system that is not Windows nor Linux, download a Java Development Kit (JDK) for this operating system (it has to be a Java Development Kit, not a Java Runtime Environment).

These are the Java Development Kits (JDK) supported to run the Denodo Platform and the Denodo Solution Manager:

  • OpenJDK version 17 LTS - HotSpot provided by the Eclipse Adoptium project. This is the version included in the Denodo Platform.

  • The Red Hat build of OpenJDK version 17.

  • The Java Development Kit version 17 of Oracle.

Note

For all of these JDKs, we recommend downloading the latest update available of Java 17. The minimum update supported is Java 17 update 16.

If you need to upgrade the update of the JDK included in the Denodo Platform and the Solution Manager, do this:

  1. Follow the steps of the Knowledge Base Article: How to change the JVM used by the Denodo Platform

  2. Rename the file <PATH TO THE NEW JDK>/lib/security/cacerts to `cacerts.backup`.

  3. Copy the file <DENODO_HOME>/jre/lib/security/cacerts to <PATH TO THE NEW JDK>/lib/security/cacerts. The “cacerts” file contains the trusted certificate authority (CA) certificates; you need to copy it to the new JDK in case you added certificates to this file.

  4. Compare the file <DENODO_HOME>/jre/conf/security/java.security with <PATH TO THE NEW JDK>/jre/conf/security/java.security. If there are differences, check if these difference are due to changes that you did in this file in the JDK included in the Denodo Platform.

Note

In Linux OS take into account that if the JVM used by Denodo Platform is changed, the Denodo monitor will continue using the default one, so you must declare the DENODO_JAVA_HOME environment variable pointing where the new JVM is located and restart all the denodo monitors. For example:

export DENODO_JAVA_HOME=<PATH TO THE NEW JDK>
Add feedback