Skip to main content Skip to complementary content
Close announcements banner

Compatible Java Environments

The following tables provide information on the recommended Java Environment you should download and install to use your Talend product.

The Compiler Compliance Level corresponds to the Java version used for the Job code generation. For more information, see Setting up Java in Talend Studio.

The supported Java platforms are OpenJDK and Oracle JDK. The recommended distribution for OpenJDK is Zulu.

Information noteImportant: All Talend products and associated third-party applications, such as the Hadoop cluster, should use the same Java version for compliance. Before you install or upgrade any associated third-party application, Talend recommends that you check which Java version they support.

In the following documentation:

  • Recommended: designates an environment recommended by Talend based on experience and customer usage.
  • Supported: designates a supported environment for use with the listed component or service.
  • Supported with limitations: designates an environment that is supported by Talend but with certain conditions explained in notes.

Talend Studio Java environments

Compatible Java environments for launching Talend Studio
Java version (OpenJDK or Oracle JDK) Support type
17 Supported from R2023-10 onwards
11 Supported

Pay attention to the following before working with Java 17:

  • If your Talend Studio has been launched with Java 11, after installing the 8.0 R2023-10 Talend Studio monthly update or a later one, Talend Studio keeps the same behavior as before. You must set the Java interpreter in Talend Studio to Java 8 if you want to execute your Jobs with Java 8. For more information, see Java Interpreter path (Talend).
  • After installing the 8.0 R2023-10 Talend Studio monthly update or a later one, if you switch the Java version to 17 and relaunch your Talend Studio with Java 17:
    • To run your Data Integration Jobs locally in Talend Studio, activate the Enable Java 17 compatibility option on the Build > Java Version view in the Talend Studio Project Settings dialog box.

      If your Jobs include any custom components that require access to the Java internal modules, you need to configure them manually after activating the Enable Java 17 compatibility option. For more information, see Setting up Java in Talend Studio.

      Information noteWarning: With the Enable Java 17 compatibility option activated, any Job built by Talend Studio cannot be executed with Java 8. For this reason, verify the Java environment on your Job execution servers before activating the option.
    • To run your Data Integration Jobs on a Remote Engine v2.13 onwards, which requires Java 17 to start and uses Java 17 by default for execution, you have two options:
      1. Rebuild your Jobs: activate the Enable Java 17 compatibility option on the Build > Java Version view, following the same process as explained above for running Jobs locally in Talend Studio. This is the recommended approach. This approach allows you to run those Jobs with the default Java 17 version of Talend Remote Engine.
      2. If you prefer not to rebuild your Jobs, configure the engine to use a different Java version from its default. To do this, specify the Java 8 or 11 instances to be used when installing the engine using the installer, or manually modify a configuration file after the installation.
    • To run your Data Integration Jobs locally in Talend Studio or on a Remote Engine or Talend JobServer which is running on Java 8, you must set the Java interpreter in Talend Studio to Java 8 and deactivate the Enable Java 17 compatibility option on the Build > Java Version view in the Talend Studio Project Settings dialog box. For more information, see Java Interpreter path (Talend) and Setting up Java in Talend Studio.

The following table shows in which Java environments the corresponding item can be executed:

Item type Java version for execution Support type
Data Integration Jobs 1 17 Supported 2

(with the Enable Java 17 compatibility option activated)

11 Supported
8 Supported with

(with the Enable Java 17 compatibility option deactivated)

Routes and Data Services Jobs
17 Supported
11 Supported
8 Not supported
Big Data Spark Jobs 4
17 Supported

(with the Enable Java 17 compatibility option activated)

11 Supported

(with the Enable Java 17 compatibility option activated)

8 Supported

(with the Enable Java 17 compatibility option deactivated)

1 The Data Integration components using Big Data distributions are only supported with Java 8 and Java 17.

2 If you want to execute your Job artifacts on Talend Remote Engine with Java 17, you must use Talend Remote Engine v2.13 or later.

3 The execution of the Big Data Spark Jobs actually depends on the Java versions supported by the cluster.

Server Java environments

Compatible Java environments for Talend Server modules
Talend Server Module Java version (OpenJDK or Oracle JDK) Support type
  • Talend Data Stewardship
  • Talend Administration Center 1
  • Talend Identity and Access Management
  • Talend Dictionary Service
  • Talend SAP RFC Server
  • Talend Data Preparation
  • Talend JobServer
  • Talend MDM Server 2
  • 17
  • 11
  • 8
Supported
  • Talend ESB Server
  • Talend ESB/Microservices
  • Talend Runtime
  • 17
  • 11
Supported
  • Talend LogServer
  • 11
  • 8
Supported
1 To use Talend Administration Center with Java 17, you need to open the <tac_installation_folder>/apache-tomcat/bin/setenv.sh file and add the following commands:
# export modules 
export JAVA_OPTS="$JAVA_OPTS --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
2 To use Talend MDM Server with Java 17, you need to open the <mdm_installation_folder>/apache-tomcat/bin/catalina.sh file and add the following commands:
JDK_JAVA_OPTIONS="$JDK_JAVA_OPTIONS --add-opens=java.xml/com.sun.org.apache.xml.internal.serialize=ALL-UNNAMED"
Information noteNote: The recommended Java environments for Big Data Distributions are OpenJDK 8 and Oracle JDK 8.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!