TPS-3498 (cumulative patch) - 6.4

author
Talend Documentation Team
EnrichVersion
6.4
EnrichProdName
Talend Data Fabric
Talend MDM Platform
EnrichPlatform
Talend MDM Server
Talend MDM Web UI
Talend Studio

TPS-3498 (cumulative patch)

Info Value
Patch Name Patch_20191021_TPS-3498_v1
Release Date 2019-10-21
Target Version 20170623_1246-6.4.1
Product affected Talend MDM Server, Talend Studio

Introduction

This patch is cumulative. It includes all previous generally available patches for MDM 6.4.1

NOTE: For information on how to obtain this patch, reach out to your Support contact at Talend.

Fixed issues

This patch contains the following fixes:

  • TPS-1997 [6.4.1] Unable to redeploy a DataModel after adding a reusable complex type Element to an Entity(TMDM-10993)
  • TPS-2166 [6.4.1] Can only import the first FK value if the field is multiple(TMDM-11453)
  • TPS-2102 [6.4.1] "OnComponentError" and "On SubjobError" not triggered when an error occurs (TMDM-11214)
  • TPS-2162 [6.4.1] [RESTApi] query returns incomplete results while executing multiple joins on entities(TMDM-11362)
  • TPS-2314 [6.4.1] Errors when deploying MDM workflows using commandline (TMDM-11705)
  • TPS-2299 [6.4.1] transaction does not commit when multiple tMDMOutput used in same subjob (TMDM-11629)
  • TPS-2433 [6.4.1] LDAP Indirect bind : LDAP: error code 32 - No Such Object (TMDM-11487)
  • TPS-2487 [6.4.1] Unable to save record ORA-02291 parent key not found / When importing if the foreign key contains a dash (TMDM-12032)
  • TPS-2679 [6.4.1] Cache implementation is flawed (TMDM-11972)
  • TPS-2683 [6.4.1] 'Modify file' svn commitsfor workflow objects (TMDM-12547)
  • TPS-2750 [6.4.1] Error when trying to open a journal record after deletion of an occurence of [0..many] (TMDM-12666)
  • TPS-2743 [6.4.1] Security issue: XXE injection (TMDM-12544)
  • TPS-2764 [6.4.1] Talend MDM decimal precision error (TMDM-12595)
  • TPS-2910 [6.4.1] [RestAPI] GET /data/{containerName}/{type}/{id} fails with HTTP 500 (TMDM-13124)
  • TPS-3075 [6.4.1] Cannot get validation token from MDM (Works ok in TAC) (TMDM-13300)
  • TPS-3343 [6.4.1] MDM WebUI, When sorting the results on a Date column (NoticeDate) the order is not correct. (TMDM-13451)
  • TPS-3400 [6.4.1] User with role System_interactive can access Data Model info via REST API even if no right via custom roles (TMDM-13941)
  • TPS-3498 [6.4.1] Workflow fails : BScript1.groovy: 2: String too long. The given string is 65984 Unicode code units long, but only a maximum of 65535 is allowed. (TMDM-14092)

Prerequisites

Consider the following requirements for your system:

  • Talend Studio 6.4.1 must be installed.
  • Talend MDM Server 6.4.1 must be installed.

Installation

PATCH INSTALLATION NOTES FOR TALEND MDM SERVER 6.4.x

PRE-INSTALLATION

  • Stop the MDM server
  • Create a patch directory (eg: C:\MDM_Patch)
  • Unzip patch file you receive from support into this directory
  • Create a backup directory (eg: C:\MDM_Backup)

WEB APPLICATION REPLACEMENT

  • Copy folder <MDM_SERVER_HOME>/apache-tomcat/webapps/talendmdm into the backup directory
  • Replace it with the folder talendmdm contained in patch directory

DB MIGRATION TOOL REPLACEMENT

  • Copy file <MDM_SERVER_HOME>/tools/dbmigration/lib/org.talend.mdm.db.migration-6.4.1.jar into the backup directory
  • Replace it with the file org.talend.mdm.db.migration-6.4.1.jar contained in <PATCH_DIRECTORY>/dbmigration

POST-INSTALLATION

  • Restart the MDM server
  • Clear browser cache on clients

PATCH INSTALLATION NOTES FOR TALEND MDM STUDIO & COMMAND-LINE 6.4.x

PRE-INSTALLATION

  • Close the Talend Studio
  • Create a backup directory (eg: C:\MDM_Backup)

PLUGINS REPLACEMENT

Copy files/folder below into the backup directory
  • <TALEND_STUDIO_HOME>/plugins/org.talend.mdm.repository.enterprise_6.4.1.20170623_1246
  • <TALEND_STUDIO_HOME>/plugins/org.bonitasoft.studio.connectors.mdm_6.4.1.20170623_1246.jar
  • <TALEND_STUDIO_HOME>/plugins/org.bonitasoft.studio.workspace.mdm_6.4.1.20170623_1246.jar
  • <TALEND_STUDIO_HOME>/plugins/org.talend.mdm.bos_6.4.1.20170623_1246.jar
  • <TALEND_STUDIO_HOME>/plugins/org.talend.mdm.studio.process.model_6.4.1.20170623_1246.jar
  • <TALEND_STUDIO_HOME>/plugins/org.talend.mdm.workbench.enterprise_6.4.1.20170623_1246.jar
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMConnection
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMBulkLoad
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMConnection
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMDelete
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMOutput
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMReadConf
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMRouteRecord
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMSP
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMViewSearch
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.localprovider_6.4.1.20170623_1246/components/tMDMWriteConf
  • <TALEND_STUDIO_HOME>/plugins/org.talend.designer.components.tisprovider_6.4.1.20170623_1246/components/tMDMRestInput
Replace them from corresponding files contained in patch directory

REMOVE LOCAL CACHED JAR FILE IN WORKSPACE

If you have an existing Studio workspace, please remove cached jar files if exist:

  • <TALEND_STUDIO_HOME>/workspace/default/lib/bulkloadclient.jar
  • <TALEND_STUDIO_HOME>/workspace/default/lib/org.talend.mdm.bonita.connector-6.4.1.jar
  • <TALEND_STUDIO_HOME>/workspace/default/lib/org.talend.mdm.common-6.4.1.jar
  • <TALEND_STUDIO_HOME>/workspace/default/lib/org.talend.mdm.workflow-6.4.1-server.jar

Copy the following jar files into <TALEND_STUDIO_HOME>/workspace/default/lib

  • <PATCH_DIRECTORY>/workspace/org.talend.mdm.bonita.connector-6.4.1.jar
  • <PATCH_DIRECTORY>/workspace/org.talend.mdm.common-6.4.1.jar
  • <PATCH_DIRECTORY>/workspace/org.talend.mdm.workflow-6.4.1-server.jar

REMOVE LOCAL CACHED JAR FILE IN REPOSITORY

If you have the following folders, please remove them:

  • <TALEND_STUDIO_HOME>/configuration/.m2/repository/org/talend/libraries/bulkloadclient
  • <TALEND_STUDIO_HOME>/configuration/.m2/repository/org/talend/libraries/mdm_transaction

POST-INSTALLATION

UPDATE JAR FILE IN NEXUS SERVER

If you rely on Sonatype Nexus to push updated jar to remote Studio Commandline, please follow these steps to update the jar files in Nexus and Studio Commandline

Login to Sonatype Nexus as administrator user
  • Select "talend-custom-libs-release" repository
  • Select Browse Storage tab, navigate and right click on org/talend/libraries/bulkloadclient and org/talend/libraries/mdm_transaction folders and select Delete action
  • On the top toolbar, click Trash -> Empty Trash
Start a Studio which is already patched, login to the remote project.
  • Select a job which contains tMDMBulkload and tMDMConnection components, right click the job from Repository view and Select Build Job, click Finish in the dialog.
  • Restart the Studio and login to the remote project again.

This will upload the new bulkload client jar file and mdm transaction jar file onto Nexus server.

Verify by login to Nexus server and check org/talend/libraries/bulkloadclient and org/talend/libraries/mdm_transaction library is poplulated under talend-custom-libs-release repository.

From a remote Studio Commandline, login to the remote project, build a job that contains tMDMBulkload and tMDMConnection component with command: buildJob <Job_Name> -dd <Path>

This will download the new bulkload client jar and mdm transaction jar from Nexus server to local maven repository.

Alternatively, bulkload client jar and mdm transaction jar will also be downloaded automatically when the job is excecuted.