Java - 6.4

Talend Real-time Big Data Platform Installation Guide for Linux

English (United States)
Talend Real-Time Big Data Platform
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Data Preparation
Talend Data Stewardship
Talend DQ Portal
Talend ESB
Talend Identity Management
Talend Installer
Talend JobServer
Talend Log Server
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio
Installation and Upgrade

In order to use your Talend product, Java must be installed on your machine. If you install your Talend Studio using the Talend Studio Installer, you do not need to set up a Java Environment as it is embedded in the Installer.

These pages list:

Compatible Java environments


In the following documentation:

  • recommended: designates an environment recommended by Talend based on our experiences 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.

These tables provide a summary of the supported Java Runtime environments.

In this table:

  • (R) means that this combination is recommended;

  • means that this combination is supported;

  • means that this combination is not supported.

Note that only the 64-bit versions of the compatible Java Runtime environments are supported.

The Compiler Compliance Level corresponds to the Java version used for the Job code generation. This option can be changed in the project settings of the Studio. For more information, see Talend Studio User Guide.


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 with java version they support.

Table 7. Studio Java environments

Support Type

JRE Version

Studio JDK Compiler Compliance Level



Oracle 8

1.8 (default)


Oracle 8


Needs to be switched to manually. Only supported for Big Data Distributions requiring it. Routes are not supported with JDK Compiler Compliance level 1.7.

Depending on the license you have, the available Execution Servers may differ.

Table 8. Server Java environments

JRE Version


MDM Server

ESB/Talend Runtime


Big Data Distributions

Talend Server Applications1


Oracle 7 (running alongside Oracle 8)

Compatible with Java 1.7 only

Compatible with Studio JDK Compiler Compliance Level 1.7 only

Oracle 8 (recommended)





Compatible with Java 1.8


Compatible with Studio JDK Compiler Compliance Level 1.7 (default/recommended) or 1.8

IBM 8 (deprecated)

Only for AIX and SUSE SLES

1: Talend server applications include Artifact Repository, CommandLine, Talend Activity Monitoring Console, Talend Administration Center, Talend Data Preparation, Talend Data Quality Portal, Talend Data Stewardship, Talend Log Server, Talend Repository Manager.

For example, the recommended combination is:

  • Oracle 8 installed on the machine running the Studio;

  • The Compiler Compliance Level set to 1.7 in the project settings of the Studio;

  • Oracle 8 installed on the machine(s) running the Execution Server(s) and the Talend Server Application(s);

  • Big Data Distributions compatible with Java 1.8 used.

For more information on Java specificities (version, Operating Systems compatibility), see Talend Help Center and Talend Community.

Setting up JAVA_HOME

In order for your Talend product to use the Java environment installed on your machine, you must set the JAVA_HOME environment variable.

To do so, proceed as follows:

  1. Find the folder where Java is installed, usually /usr/lib/jvm/java-x-oracle.

  2. Open a terminal.

  3. Use the export command to set the JAVA_HOME and Path variables.

    For example:

    export JAVA_HOME=/usr/lib/jvm/jre1.8.0_65
    export PATH=$JAVA_HOME/bin:$PATH
  4. Add these lines at the end of the global profiles in the /etc/profile file or in the user profiles in the ~/.profile file.

    After changing one of these files you have to log on again.