Frequently asked questions about the upgrade to 8.0.1-R2023-08

Where can I get the Talend Runtime archive or installer?

The last up-to-date version for full installers is 8.0.1-R2024-05 that provides support for Java 17.

If you are using Talend Cloud, you can download Talend Runtime from the Talend Cloud download page.

If you are using on-premises Talend products, the 8.0.1-R2024-05-RT deliverables are available for download on https://www.opensourceetl.net. The license credentials issued with your original Talend 8.0.1 product subscription will be required for the download. Please contact Talend Support if you miss these credentials. The download link is determined according to the product license you have subscribed to. Please replace the license placeholder in the following URLs with the appropriate short name:

https://www.opensourceetl.net/tis/[license]_801/TalendRuntime-8.0.1-R2024-05-RT-linux-x64-installer.run
https://www.opensourceetl.net/tis/[license]_801/TalendRuntime-8.0.1-R2024-05-RT-windows-installer.exe
https://www.opensourceetl.net/tis/[license]_801/Talend-Runtime-V8.0.1.R2024-05-RT.tar.gz
https://www.opensourceetl.net/tis/[license]_801/Talend-Runtime-V8.0.1.R2024-05-RT.zip

The license short names corresponding to Talend product names are:

Talend ESB 8.0.1: "esbee"
Talend Data Fabric 8.0.1: "tdf"
Talend MDM Platform 8.0.1: "tpmdm"
Talend Data Services Platform 8.0.1: "tpds"
Talend Real-Time Big Data Platform 8.0.1: "tpdsbdrt"

For example, the download link for the Linux installer corresponding to the Talend ESB 8.0.1 license is https://www.opensourceetl.net/tis/esbee_801/TalendRuntime-8.0.1-R2024-05-RT-linux-x64-installer.run.

Do I need to upgrade my Remote Engine?

Upgrading your Remote Engine is not a requirement, but if you are not using the latest version of the Remote Engine, it is a good opportunity to upgrade it.

Are my already published artifacts compatible with the new Talend Runtime 8.0.1-R2023-08 (or later)?

No. Breaking changes brought by the third-party libraries cause the old artifacts to become incompatible with the new Talend Runtime. A new publish is required for all Routes and Data Services.

Deploying an old artifact in the new Talend Runtime will fail and add a message in Talend Runtime logs telling that the artifact is not compatible.

What if I deploy a newly published artifact from 8.0.1-R2023-08 in an old Talend Runtime?

Deployment will fail silently. Old Talend Runtime does not include any mechanism that could detect a version incompatibility.

How can I recognize an artifact which is newly built with version 8.0.1-R2023-08 from an older artifact?

You can define rules about artifacts versioning or artifacts naming.

Can I use Talend Runtime migration tooling provided with recent patches to automate migration to 8.0.1-R2023-08?

No. The provided tooling helps if artifacts deployed in the source Runtime are compatible with the target Runtime. Here it is not the case. Even Runtime configuration must be manually migrated.