Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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.
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
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
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
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...
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