Warning about migration of Studio Preferences and Nexus

If you are planning or doing a migration from an earlier version of Talend to the latest version, you may have seen an option to export your Studio preferences. This would be useful to migrate all saved configurations within Studio to a newer version to speed up migration and maintain settings.

 

However, if you have Nexus settings in your configuration, or have a different repository structure in your earlier Talend instance than the newest one, do not import your previous preferences into your new Studio instance. The preferences will contain permissions and symbolic mapping to your Nexus repositories that may have changed, and when you try to build a Job, Studio and TAC may not be able to map or locate the original repositories that the folders are located in, causing errors. An example is shown below:

 

Print updateLockStatus : 110 (5 executions avg : 246 tot : 1234)
ERROR: http://<location of Nexus>:8081/nexus/content/repositories/releases/org/talend/components/index/6.4.1/index-6.4.1.xml
java.io.FileNotFoundException: http://340a-eda.domain.local:8081/nexus/content/repositories/releases/org/talend/components/index/6.4.1/index-6.4.1.xml
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1872)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
	at org.talend.updates.runtime.nexus.component.NexusComponentsTransport.downloadXMLDocument(NexusComponentsTransport.java:224)
	at org.talend.updates.runtime.engine.factory.ComponentsNexusInstallFactory.retrieveComponentsFromIndex(ComponentsNexusInstallFactory.java:106)
	at org.talend.updates.runtime.engine.factory.ComponentsNexusInstallFactory.getLocalNexusFeatures(ComponentsNexusInstallFactory.java:82)
	at org.talend.updates.runtime.login.InstallLocalNexusComponentsLoginTask$ComponentsLocalNexusInstallFactory.getAllExtraFeatures(InstallLocalNexusComponentsLoginTask.java:48)
	at org.talend.updates.runtime.engine.factory.ComponentsNexusInstallFactory.retrieveUninstalledExtraFeatures(ComponentsNexusInstallFactory.java:154)
	at org.talend.updates.runtime.login.InstallLocalNexusComponentsLoginTask.run(InstallLocalNexusComponentsLoginTask.java:90)
	at org.talend.rcp.intro.ApplicationWorkbenchAdvisor.preStartup(ApplicationWorkbenchAdvisor.java:115)
	at org.eclipse.ui.internal.Workbench$24.runWithException(Workbench.java:1699)

 

There are ways that you can avoid this issue and shorten downtime and your migration path:

  1. Verify that your Nexus migration went correctly. To verify, see the following document for the correct steps:

    Talend Big Data Platform Migration Guide > Upgrading the Nexus Artifact repository

  2. Once you have upgraded your Nexus, check the repositories and make sure they are the same for both environments. There may have been Talend-custom-libs in the previous environment, and Talend-Custom-libs-Snapshots, and Talend-Custom-Libs-Releases, in the new environment, for example.

    If they are different, please make sure to manually copy settings over from your old Studio instance to your new one.

     

If you have additional questions, consult the migration guide for the platform that you are using on help.talend.com.

Version history
Revision #:
4 of 4
Last update:
‎06-06-2018 09:23 AM
Updated by: