Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Manual Java version selection (v2.13 to v2.13.8)

Last updated: 9/17/2026

Use this guidance if your Talend Remote Engine version is v2.13 to v2.13.8 and you cannot upgrade to a later version.

For these versions, Java 21 artifact execution is not supported. If you need Java 21, upgrade to Talend Remote Engine v2.14.2 or later and then use Adaptive mode on: dynamic Java selection (v2.14.2 or later) or Adaptive mode off: manual Java version configuration (v2.14.2 or later), depending on your runtime setup.

About this task

This approach is not dynamic. You specify a single Java version for execution through PATH and custom configuration.

Procedure

  1. Stop the engine.
  2. Browse to the <RemoteEngineInstallationDirectory>/etc directory.
  3. Depending on the type of the artifacts you need to run with a specific Java version, do the following:
    • For Jobs, add the path to your Java instance to be used to your PATH environment variable. Then open a command-line terminal and execute the java -version command. You should see the version of the Java instance printed.

      Any Java process starts with this instance defined in the PATH.

    • For Microservices, in the <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.dsrunner.cfg, add the path to the Java executable file. For example,
      ms.custom.jre.path=/usr/lib/jvm/java-openjdk-amd64/bin

      Make this modification before deploying your Microservices to ensure that these changes are correctly taken into account.

    For both artifact types, use backslashes to escape characters specific to a Windows path, such as colons, whitespace, and directory separators, while keeping in mind that directory separators are also backslashes on Windows. For example:
    c:\\Program\ Files\\Java\\jdk\\bin\\java.exe
  4. Depending on whether the engine has been installed as a Linux system service, do the following:
    • If the engine was not installed as a Linux system service:
      1. Browse to the <RemoteEngineInstallationDirectory>/bin/setenv file.
      2. Add the following line: export PATH="<path-to-jvm-bin-directory>:${PATH}"

        This path-to-jvm-bin-directory is the path to the bin folder of the JVM instance you need to use to run Jobs or Microservices. This line adds this path to the PATH environment variable.

    • If the engine was installed as a Linux system service:
      1. Browse to the <RemoteEngineInstallationDirectory>/etc/talend-remote-engine-wrapper.conf file.
      2. Add the following line to the Wrapper Properties section or change the path if this line exists already: 
        set.PATH=<desired-java-home-path>:%PATH_WITH_JAVA%
        This desired-java-home-path is the path to the bin folder of the Java instance to be used. This path must be added right after set.PATH=. Keep %PATH_WITH_JAVA% as is.
  5. Restart the engine.

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 – please let us know!

Leave your feedback here