Automatic migration of a full Talend Runtime installation (recommended)
Most versions of Talend Runtime that
cannot be obtained from a patch, such as 7.3.1-R2022-09-RT and 8.0.1-R2022-10-RT, can be
migrated automatically with the migration tool. This tool automatically migrates
configuration and installed features from the existing Talend Runtime to
its new long-term support version.
Before you begin
- Your runtime version is 8.0 onwards.
- The version you want to migrate to is not 8.0.1-R2023-08-RT. To migrate to this version, see Manual migration of a full Talend Runtime installation.
- Applying an upgrade patch, the recommended approach, is too complicate to be feasible and thus you have received a full installer from Qlik.
- You have installed the new version of Talend Runtime. Note that the new version should be installed the same way as the version to be upgraded. In other words, either the new and the old versions are installed as a service or both of them are unzipped in given directories as a standalone program.
About this task
- Perform this migration in a non-production environment first to ensure that the output contains all the important custom resources, especially those you manually installed, of the old version to be fully functional.
- By default, the migration tool is stored in a folder called migration in the patch files, so this is the location used in this article. You can store it in a different directory of your choice.
Procedure
Troubleshooting: If you encountered issues during or after the migration, try the
following steps.
- Verify the error log in log/tesb.log of both the Talend Runtime versions.
On Windows, you can add $DebugPreference = 'Continue' to PowerShell before the script line to generate the specific debugging logs.
- If errors happen during the migration, do the following to roll back:
- Stop the new Talend Runtime engine.
- Start the old one.
- Stop the old and the new Talend Runtime instances.
- Delete and then re-install the new Talend Runtime version.
- Clear the log/tesb.log file.
- Restart the old Talend Runtime instance and run the migration script as explained above.