Upgrading your Talend products

This page is deprecated: although the information provided may still be applicable, it will not be maintained. Please visit the Talend Help Center website to read the latest and most accurate installation information, and update your bookmarks.

 
 

This page describes the various operations required to migrate version of the Talend solutions.

Backing up the environment

Before you start migrating your Talend solutions, make sure your environment is correctly backed up.

Saving the local projects

  1. Launch the Studio.
  2. Click the icon and export your local projects to an archive file.

Upgrading the Talend projects in the Studio

Importing your local projects

  1. Launch the new Studio you have just installed.

  2. In the login window, select Import, then import the archive file containing your local projects.

    The local projects are displayed in the Project list and appear on the Studio Repository view.

Migrating MDM projects

MDM master-records are stored in a database. Depending on your installation, this may be an XML or a relational database. You can migrate from one XML database version to another, or you can export your data from an XML database and reimport it in a relational database.

Note that the MDM Repository is always stored in an XML database.

Since not everything is stored in a database, you must also manually import and redeploy the following items:

  • Jobs,

  • pictures,

  • web resources.

[Warning]  

You must delete your web browser cache and cookies whenever you change the version, or the Studio. Unpredictable behavior or display errors will occur if you do not.

The sections below explain all the tasks you must carry out to perform a complete migration of all the data objects you have on the MDM server, including master-records, Jobs, pictures and web resources.

Migrating between two XML databases

Prerequisite(s): Make sure that both MDM servers are not running.

  1. In the Jboss folder of the old MDM version, browse to:

    jboss-4.2.2.GA/server/default/deploy/exist-1.4.0-rev11706-TalendPatch.war/WEB-INF/data

  2. Copy the data folder of the old MDM version and paste it in the same path in the new MDM version.

     

    If you have pictures in your model, make sure to copy jboss-4.2.2.GA/server/default/deploy/zz.50.ext.imageserver.war/upload to the same path on the new server. For more information, see the the section called “Moving the pictures and web resources”.

  3. Launch the MDM server and then the new version of Talend Studio and you should have access to the migrated data objects.

Manually moving repository items from an XML database to a relational database

Prerequisite(s): Make sure that both MDM servers are up and running and that you have a connection to each of them in the Server Explorer panel in Talend Studio.

[Warning]  

If you need to migrate between two databases on a single machine, you must run the two MDM servers side by side. You can do this by setting a different port binding on the target server.

To manually move your repository items from an existing XML database to a relational database, do following:

  1. In the MDM Repository tree view of Talend Studio that is connected to the server with the XML database, click the Export Items button in the repository icon bar.

  2. In the Export Repository items window that opens, specify the location to which you want to export your repository items, select the items you want to export, and then click Finish.

  3. In the MDM Repository tree view of Talend Studio that is connected to the server with the relational database, click the Import Items button in the repository icon bar.

  4. In the Import Repository items window that opens, specify the location where the repository items you want to import are stored, select the items you want to import, and then click Finish.

Reimporting and redeploying your Jobs

Prerequisite(s): Make sure that the MDM server is up and running.

If you have Talend Jobs in your old MDM application, do the following to migrate these Jobs:

  1. From the Integration perspective, import your local and remote Jobs as described in the the section called “Upgrading the Talend projects in the Studio”.

  2. Deploy the Jobs to the new MDM server one by one. For further information, see the Talend Studio Administrator Guide.

[Note]  

You can also copy/paste the job scripts (.war or.zip) from their corresponding folder in the old application to the same folder in the new application: jboss-4.2.2.GA/server/default/deploy for wars and jboss-4.2.2.GA/jobox/deploy for zips. But this will not import the job design that you may need at some point. Another limitation with this copy/paste mode is that it is recommended only between two MDM servers that have the same major version (first number of the unique identifier of the version). If the major versions differ, it is very likely that the MDM components will not work with the new MDM Server. If you are migrating between 2 identical versions or 2 versions where only the minor version differs, however, copying the wars or zips will be a lot faster than redeploying the Jobs.

Moving the pictures and web resources

Prerequisite(s): Make sure that both MDM servers are not running.

If you use pictures in your data-model, do the following to migrate them to the new MDM server:

  1. In the Jboss folder of the old MDM version, browse to:

    jboss-4.2.2.GA/server/default/deploy/zz.50.ext.imageserver.war/upload

  2. Copy the upload folder of the old MDM version and paste it in the same path in the new MDM version.

  3. Launch the MDM server and then Talend Studio of the new MDM version as usual and you should have access to the migrated data objects.

    If you use web resources (images, css, js, etc. in your smart views, do the following to migrate them to the new MDM server:

  4. In the Jboss folder of the old MDM version, browse to:

    jboss-4.2.2.GA/server/default/deploy/jboss-web.deployer/ROOT.war

  5. Copy the web resources from the old MDM version and paste them in the same path in the new MDM version.

  6. Launch the MDM server and then Talend Studio of the new MDM version as usual and you should have access to the migrated data objects.