I'm Arthur from the Support team. I got together with our Talend Support Engineers and our community content editors and discussed how we could make migrations/upgrades easier for everyone using Talend. Following this intro will be a list of URLs and topics that will hopefully make upgrading easier and smoother for all of our users, new or old. We'll continue to add to this list, so keep checking back! And without further ado...
Migration Guide Links:
For all versionsBackup the database:Before you do anything, do not forget to backup the database. Even if you do accidentally go to the DB Config page, it will notice that you are on a lower version of Talend first. Stop here and backup all of your data before clicking on "Proceed to migrate".
Be sure to check the version of the database that you are migrating from and take the appropriate version when placing it into the Tomcat: \tac\apache-tomcat\lib.
Normally if the database has a lot of data, there is one particular table that you can truncate in order to allow the database to migrate. This table is the taskexecutionhistory.
Cannot login to TAC:
Per discussion in the community article (https://community.talend.com/t5/Talend-Tech-Internal/Data-Stewardship-Job-migration-on-Talend-7-0/m-...), The Data Stewardship Console has been retired in Talend 7.0, so the migration from data stewardship console to Talend data stewardship needs to be handled prior to Talend 7.0.
The migration methodology in the link below works fine for Talend 6.5 and older, but not 7.0
This is a known issue with dirty records in the database regarding schema. You may get an "array out of bounds error"
The workaround is to truncate table "usergroup_user" and "user_usergroup" before proceed to migration
Talend's official suggestion is that if you are planning to migrate to 6.4.1: there is a patch available for the issue. Please open a Support Case and ask for patch TPS-2548.
Customer should avoid creating SVN/Git based tasks in job conductor as this feature is being deprecated. The best practices suggest that the customers should use CI builder to build and publish the artifacts and use these published artifacts to create the tasks in Job Conductor.
All customers planning to use Talend 7.0.1 ESB should apply the cumulative patch TPS-2462. Read more about it in the below documentation.
If you require this patch, please open a Support Case and request TPS-2462.
If a customer wants to use the "Publisher" in TAC they need to install Nexus 2 on their own as Publisher is not supported with Nexus 3 which comes with our installation package. The customer can either do a fresh install of Nexus 2 or can use a Nexus 2 that is working with their current Talend version.
You can find the list of new features and deprecations in the link below:
Build-aggregator.pom does not exist error after migrating to 7.0.1
This is a known issue.
To resolve the issue, go to File -> Edit project settings -> Build -> Maven -> Force full re-synchronization poms. This should resolve the Build-aggregator.pom does not exist errors after migration.
There is also a patch that was created for the issue.
After opening a Support Case please request: TPS-2571
All of the jobs on Studio 7.0 are not editable for LDAP users
This is a known issue where the job is always locked when LDAP user login to studio. (https://jira.talendforge.org/browse/TMC-13493)
The workaround is to use the value of the "Login field" configured on the TAC to login to Studio
If you run into the issue above, please open a Support Case and request for patch: TPS-2584.
Clear steps from R&D is how to migrate the artifacts from Nexus 2.11 (Talend 6.3.1) to Nexus 3.9 (Talend 7)
Upgrade 2.11 to 2.14.9 which can be downloaded here:
Just overwrite your folder in the example path with the new version folder and this will upgrade your nexus but you may need to fix the service:
Enable the upgrade agent capabilities
How to Enable the upgrade agent:
While both nexus 2.14.9 and 3.9 are running navigate to your nexus 3.x website making sure that both nexus sites do not have conflicting ports. Ports can be changed here:
In the UI of Nexus 3.9 go ahead and delete all of the repositories that you are wanting to import in. Go to the capabilities screen and activate the upgrade tab of the preferences screen. Then you will be able to point to the Endpoint and the access token that you get from Nexus 2.14.9 and complete the migration. Video from sonatype on the steps post upgrade to 2.14.9:
Note: After migrating nexus from 2.11 - 2.14 - 3.9, the roles for talend-updates-admin in nexus 3.9 are very limited, include all the roles. In TAC, update the local username & password, it should clear all the errors from software update configuration section.
Important Note Regarding Nexus 3
It is paramount that you move to Nexus 3.14 if you are planning to stay on Nexus 3. As mentioned above Nexus 3.9 has limitations and in particular has issues regarding performance. Do not move to higher versions of Nexus as 3.14 is the highest version supported by Talend as of Talend 7.0/7.1.
If you are using Nexus on versions later than 3.09, please review this link which is applicable for both 7.0 and 7.1: https://help.talend.com/reader/Od7BSSwZmOsHBIPRY760sA/PCXotGURcHH_eZEEHJiPpQ
Join us live for a sneak peek!
Accelerate your data lake projects with an agile approach
Create systems and workflow to manage clean data ingestion and data transformation.
Introduction to Talend Open Studio for Data Integration.