TPS-4209 (cumulative patch) - 7.2

Introduction

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

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

Fixed issues

This patch contains the following fixes:

• TPS-4209: [7.2.1] Camel-salesforce feature failed to be installed on Runtime (TESB-26595)
• TPS-4170: [7.2.1] Swagger UI not getting updated (TESB-29278)
• TPS-4133: [7.2.1] Runtime errors net.sf.saxon.trans.LicenseException: when using "camel-saxon" and tdm components (TESB-29218)
• TPS-4098: [7.2.1] Unsolicited restart of Talend resources while deploying/undeploying routes (TESB-29223)
• TPS-3791: [7.2.1] Camel route with cSetProperty failing on runtime (TESB-28215)
• TPS-3646: [7.2.1] The Karaf will not work with an SSL authenticated client set up (TESB-27544)
• TPS-3613: [7.2.1] Timeout when trying to connect to JMX port 8888 (TESB-26434)
• TPS-3594: [7.2.1] Runtime "org.ops4j.pax.logging.cfg" overwritten by Cloud-RemoteEngine (TESB-27385)
• TPS-3446: [7.2.1] Talend Runtime - Jobserver - [Regression] Not able to overwrite context param through TAC using BigData jobs(TPSVC-11563)
• TPS-3385: [7.2.1] Talend Runtime - Jobserver - Default context is generated in children job folder falsely (TPSVC-11101)
• TPS-3333: [7.2.1] Remove hard coded keys used for encryption from JobServer ( Talend Runtime )
• TPS-3297: [7.2.1] Default user in AMQ WebConsole config (needs to be removed) (TESB-26606)
• TPS-3279: [7.2.1] Encryption of user passwords does not work as expected (TESB-26507)

Prerequisites

Consider the following requirements for your system:

• Talend ESB Runtime 7.2.1 must be installed.

• Depending on the product, <container> is Talend-ESB-V7.2.1/container/ or Talend-Runtime-V7.2.1/

• 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
  

Installation

Standalone Activemq

Optional, only needed in case the standalone Apache ActiveMQ Broker is used. This directory also only exists in the Talend-ESB package but is not part of the Talend-Runtime package.

• Stop Standalone Activemq
• Extract & replace the content of ZIP directory activemq into Talend-ESB-V7.2.1/activemq/

Structure after extract & replace should be :

Talend-ESB-V7.2.1
├───activemq  : existing dir superseeded by patch
├───add-ons   : existing dir
├───bin       : existing dir
├───container : existing dir
├───...

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
│   └───TPS-4209
|           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
│   └───TPS-4209
|           patch.bat
|           patch.commands
|           patch.sh
├───system  : existing dir superseeded by patch
│   ├───... : existing dir
│   ├───... : directories from patch
├───...

• Execute <container>/patches/TPS-4209/patch.bat or <container>/patches/TPS-4209/patch.sh
• Ensure directory <container>/patches/TPS-4209/ contains two new log files : xxx-init.log and xxx-installed.log