This procedure describes how to upgrade your Talend
environment to use Java 17.
Procedure
Make sure that your Talend Remote Engine and Talend JobServer instances can support the Java versions to which you want to upgrade.
Configure the JDK versions used by your Talend Remote Engine and Talend JobServer instances, to ensure that all existing Jobs, Routes, and Data Services
continue to run while you rebuild the ones that aren't Java 17 compliant. Then,
align the JDK version of each Talend Remote Engine or Talend JobServer with the JDK version of each Talend Runtime that you use them with.
For example, if you have Java 8 compliant Jobs, you should configure Java 8
for these Jobs, and Java 17 for the Jobs that you will progressively migrate to
be compliant with Java 17. If all of your Jobs and Routes can run with Java 17,
you should only configure Java 17.
If you are using Routes or Data Services:
If you already built all of your Routes and Data Services as
microservices with Talend 8.0, they can run with Java 11 or Java 17. Routes and Data Services built
from the R2025-02 release require Java 17 to run.
If you are using Routes or Data Services built as OSGi, you must install
a Talend Runtime that uses Camel 4 from R2025-02. You must also install a new version of
Talend Remote Engine if a Talend Remote Engine is part of your architecture. For more information, see Manual migration of a full Talend Runtime
installation and Upgrading Talend Remote
Engine.
You can continue running your Camel 3 Talend Runtime and progressively rebuild and redeploy your Routes and Data Services
to the new Talend Runtime that uses Camel 4 and that runs with Java 17. This is because
Talend Runtime can handle only one Camel version, and Camel 4 is incompatible with
Java versions below 17.
Make sure to test and update any existing
custom code or external libraries tha tyou may be using in Routes and
Decision Services to make them compatible with Camel 4.
Upgrade your Talend Studio.
If all your Jobs can run with Java 17, you can upgrade to a version of
Talend Studio that builds and runs Jobs with Java 17 only. If some of your Jobs cannot run
with Java 17, you should continue to use a Talend Studio version that can build Jobs with Java 8, while progressively rebuilding all
your Jobs with Java 17 in another Talend Studio instance.
Information noteImportant:Talend Studio versions that support Java 8 will be maintained for a limited time. If
you are using Java 8, we recommend that you migrate to Java 17 as soon as
possible to ensure continued support of your environment.
Progressively rebuild your artifacts so that they can run on Java 17 natively.
The best practice is to first rebuild Routes and Data Services, and then
continue with the Jobs that are modified often before rebuilding other
artifacts.
Routines will continue to be built with a Java 8 compliance level by default.
You can upgrade routines to Java 17 depending on your needs. Note that Big Data
Jobs don't support routines that run on Java 17. The flexibility of running
routines with Java 8 exists to accommodate big data technologies that don't yet
support other Java versions.
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!
