R2020-11-RT (cumulative patch) - 7.3

author
Talend Documentation Team
EnrichVersion
7.3
EnrichProdName
Talend ESB
EnrichPlatform
Talend ESB

R2020-11-RT (cumulative patch)

Info Value
Patch Name Patch_20201120_R2020-11_v1-RT-7.3.1
Release Date 2020-11-20
Target Version 20200219_1130-7.3.1
Product affected Talend ESB Runtime

Introduction

This patch is cumulative. It includes the previous generally available patches from Talend ESB Runtime 7.3.1.

NOTE: To download this patch, liaise with your Support contact at Talend.

Fixed issues

This patch contains the following fixes:

TESB

  • TESB-31051: No more authentication methods available
  • TESB-30992: Conflicting spifly bundle versions leading to jetty random behaviour
  • TESB-30676: ESB patch doesn't remove all previous talend-data-mapper features
  • TESB-30396: Issue with 'sleep 10' during ESB patch installation
  • TESB-30308: Error Updating talend-data-mapper in Unix
  • TESB-29858: unresolved dependencies [(&(language=js)(objectClass=org.apache.camel.spi.LanguageResolver))] with Java 11
  • TESB-29867: Avoid org.talend.libraries.jmx export META-INF.services
  • TESB-29786: Problems using groovy.json
  • TESB-29133: Update dom4j to 2.1.3
  • TESB-28966: MQTT: consume messages published before client starts up
  • TESB-29278: Swagger UI not getting updated
  • TESB-29223: Unsolicited restart of Talend resources while deploying/undeploying routes
  • TESB-28029: Update to use Spring 5.1.14.RELEASE

TPSVC

  • TPSVC-14107: Parameter Delimiter tab (\t) treated as string in tFileOuputDelimited if artifact published fromTalend Studio 7.2 and task published in 7.1 updated
  • TPS-4318: JobServer memory leak related to ZeroMQ mailbox (TPSVC-12728)

TDM

  • TDM-8409 tHMap with payload output of HL7V2 representation has an NPE execution error
  • TDM-8359 Warning about overflow is incorrect for negative Cobol numbers
  • TDM-8364 TDM IO WriteURL broken
  • TDM-8363 Map isn't working after "R2020-09" patch installation (Error: "Input to cast cannot be atomized")
  • TDM-8327 NumberFormatException when running an imported project with a Map rep on the output map element
  • TDM-8326 Cobol Reader stops on 0xFF values with Variable Blocked format
  • TDM-8318 Cobol Reader should silently truncate records with VB option
  • TDM-8307 High memory usage by TDMEndpoint class in Runtime
  • TDM-8293 highlight is not right when show document for json with null element or invisible group
  • TDM-8225 cMap throws classcastException and not able to map a property from java bean
  • TDM-8217 Warning should not be issued for BTS and FTS segments
  • TDM-8210 Unable to MAP HL7 with CSV
  • TDM-8198 Export more packages in org.talend.transform.saxonpe.osgi
  • TDM-8163 Add new Function FormatDateTime
  • TDM-8125 DatabaseLookup creating new DataSources for each message on the ESB
  • TDM-8106 Remove dependency on org.codehaus.jackson in JSON io module
  • TDM-8094 Databaselookup fails on new runtime unless it is a top-level expression
  • TDM-8092 XML Reader should honor encoding set in the XML Representation
  • TDM-8089 Problem with camel headers when cJMS and cMap are used
  • TDM-8084 [7.3.1] Using thmap is getting an error when using a map with X12_5050_HIPPA structure
  • TDM-8074 Field alignment in positional flat file structures
  • TDM-7969 TDM adds unencrypted passwords to error message
  • TDM-7908 ReadNested within CSV or HashMap Representation fails
  • TDM-7789 CSV reader should use the optimization done for the CSV writer
  • TDM-7781 Result is incorrect when map attributes from xml to flat
  • TDM-7780 Result is incorrect when map attributes from xml to json
  • TDM-6619 Mapper bundles in state 'Failure' after deployment

Prerequisites

Consider the following requirements for your system:

  • Talend ESB Runtime 7.3.1 must be installed.

  • Depending on the product, {container} is Talend-ESB-V7.3.1/container/ or Talend-Runtime-V7.3.1/

  • Before applying the patch, and if old TDM patches have been installed (ie: org.talend.transform.runtime.distrib-X.Y.Z_yyyyMMdd_HHmm.zip), please check the repository files are actually available on system, using this command:

    karaf@trun()> feature:version-list talend-data-mapper | grep file
    Version             | Repository | Repository URL
    --------------------+------------+---------------------------------------------------------------------------------------------------------
    7.3.1.20200413_0622 |            | file:/opt/TALEND/org.talend.transform.runtime.distrib-7.3.1_20200413_0651/features.talend-esb.xml
    7.3.1.20200528_1359 |            | file:/opt/TALEND/org.talend.transform.runtime.distrib-7.3.1_20200528_1415/features.talend-esb.xml
    

Here for instance, check these files are available:

/opt/TALEND/org.talend.transform.runtime.distrib-7.3.1_20200413_0651/features.talend-esb.xml
/opt/TALEND/org.talend.transform.runtime.distrib-7.3.1_20200528_1415/features.talend-esb.xml

If not, make sure to re-extract the old TDM patches to make these files available at the above locations After successful execution of the current patch, these files can be removed

  • Before applying the patch, and if TAC is used, latest TAC patch should be installed

  • Before applying the patch, please change the following properties in file {container}/etc/org.apache.karaf.jaas.cfg

    encryption.enabled = true
    encryption.name = basic (or jasypt)
    
  • Only in case that you have custom changes made in {container}/etc/org.talend.remote.jobserver.server.cfg, you need to backup this file and set the following properties explicit to your file and then copy it back after the patch is applied

    # Set to false to avoid the creation of a temporary context file - useful for big data jobs where the default context is inside the job jar
    # Note that if the default context is not found JS automatically uses the command line to transfer context parameters even if
    # SECURE_CONTEXTS=true
    org.talend.remote.jobserver.commons.config.JobServerConfiguration.SECURE_CONTEXTS=true
    
    # Set the timeout(milliseconds) for job TRACE and STATS LOGS, value shouldn't be less than 0;
    # 0 millisecond means an infinite timeout
    org.talend.remote.jobserver.commons.config.JobServerConfiguration.TRACE_STATS_TIMEOUT=0
    
  • TPS-4318: JobServer memory leak related to ZeroMQ mailbox (TPSVC-12728) requires configuration in {container}/etc/org.talend.remote.jobserver.server.cfg:

    org.talend.remote.jobserver.server.TalendJobServer.ENABLED_PROCESS_MESSAGE=false
    

Installation

Container

New Container (never started)

  • Extract & replace the content of ZIP directory container into {container} directory

Structure after extract & replace should be :

{container}
├───bin     : existing dir
├───deploy  : existing dir
├───etc     : existing dir superseeded by patch
├───...
├───patches : dir from current or previous patch
│   └───Patch_20201120_R2020-11_v1-RT-7.3.1
│           patch.bat
│           patch.commands
│           patch.sh
├───system  : existing dir superseeded by patch
│   ├───... : existing dir
│   ├───... : directories from patch
├───...

Existing Container

  • Start Runtime Container
  • Extract & replace the content of ZIP directory container into {container} directory

Structure after extract & replace should be :

{container}
├───bin     : existing dir
├───deploy  : existing dir
├───etc     : existing dir superseeded by patch
├───...
├───patches : dir from current or previous patch
│   └───Patch_20201120_R2020-11_v1-RT-7.3.1
│           patch.bat
│           patch.commands
│           patch.sh
├───system  : existing dir superseeded by patch
│   ├───... : existing dir
│   ├───... : directories from patch
├───...
  • Ensure username/password are right in {container}/patches/Patch_20201120_R2020-11_v1-RT-7.3.1/patch.bat or {container}/patches/Patch_20201120_R2020-11_v1-RT-7.3.1/patch.sh

    ... -u {username} -p {password} -f patch.commands ... 
    
  • Execute {container}/patches/Patch_20201120_R2020-11_v1-RT-7.3.1/patch.bat or {container}/patches/Patch_20201120_R2020-11_v1-RT-7.3.1/patch.sh

  • Ensure directory {container}/patches/Patch_20201120_R2020-11_v1-RT-7.3.1/ contains new log files :
  • xxx-installation.log: patch installation log
  • xxx-init.log: state before patch installation
  • xxx-installed.log: state after patch installation
Please note that Routes using cMap (TDM feature) are not automatically restarted by the patch procedure.
You will need to restart the Runtime Container for changes to take effect.