Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.

Qlik Talend Cloud: How to configure different Java Versions to run Jobs or Microservices in Talend Remote Engine for Compatibility Configuration

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
TalendSolutionExpert
Contributor II
Contributor II

Qlik Talend Cloud: How to configure different Java Versions to run Jobs or Microservices in Talend Remote Engine for Compatibility Configuration

Last Update:

Aug 1, 2025 2:29:49 AM

Updated By:

Xiaodi_Shi

Created date:

Nov 6, 2023 2:58:29 AM

By default, a Remote Engine uses the Java version of its environment to execute Jobs or Microservices. With Remote Engine v2.13 onwards, Java 17 is mandatory for engine startup, but compatibility with JDK 8 or 11 may still be necessary.
Importantly, although Java 17 is a mandatory requirement for the new engine to start, when it comes to running Jobs or Microservices, you retain the flexibility to either use the default Java 17 version or choose older Java versions, through straightforward configuration of the engine.

This article briefly introduces how to configure different Java versions to run Jobs or Microservices in Talend Remote Engine for compatibility configuration.

 

How To

  1. Adaptive mode: Configuring Remote Engine to dynamically select Java version

    Recommended for engines starting from v2.13.9 (released in R2025-01): from that release, Remote Engine adopts a dynamic JVM selection mode. This mode automatically adapts the engine to the correct Java version to run Jobs or Microservices. See Adaptive mode: Configuring Remote Engine to dynamically select Java version

  2. Specifying a Java version to run Jobs or Microservices 

    This approach provides an alternative to the adaptive mode if the Adaptive mode is not available to your engine version. It allows you to run the artifacts designed with Java versions older than Java 17. (a solution is to use Java 8 or Java 11 to execute the job even if the RE is using Java 17).

    JDK compiler compliance level in studio was used when code built and Remote Engine relies on JAVA_HOME. 

    If your engine is v2.13 or later but still older than v2.13.9, you cannot upgrade it to the latest version and follow this procedure to specify the Java version to be used for executions. 

    This approach is not dynamic and only one version can be specified. See Specifying a Java version to run Jobs or Microservices

 

Related Content

For more information about configuring java version for job execution or microservice execution, please refer to 

configure-java-versions-for-job-execution-or-microservice-execution

 

Environment

 

 

Labels (2)
Comments
wei_guo
Support
Support

Since R2025-04, Qlik introduced a dynamic JDK switching mechanism, Remote Engine/Jobserver can be based on the job compilation JDK version to pick up the right one to run the DI job.  
Detailed configuration, pls check the doc below : 


Setting up compatible Java versions to run Jobs or Microservices | Talend Remote Engine User Guide f...
Setting up compatible Java versions for Talend JobServer to run Jobs | Talend Installation Guide Hel...

Jobserver : start_rs.sh 
 # set the JVM arguments here MY_JVM_ARGS="-Dorg.talend.execution.JAVA_8_PATH=/path/to/java8/bin -Dorg.talend.execution.JAVA_11_PATH=/path/to/java11/bin -Dorg.talend.execution.JAVA_17_PATH=/path/to/java17/bin"
 
Remote engine: <RE_installation>/etc/system.properties 
org.talend.execution.JAVA_8_PATH=/path/to/java8/bin org.talend.execution.JAVA_11_PATH=/path/to/java11/bin org.talend.execution.JAVA_17_PATH=/path/to/java17/bin
Xiaodi_Shi
Employee
Employee

Hello @wei_guo 
Thanks for your feedback and referenced links. We have added the new section into this article for the latest update.

Best regards

Sabrina

Version history
Last update:
‎2025-08-01 02:29 AM
Updated by: