TPS-3653 (cumulative patch) - 7.1

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

TPS-3653 (cumulative patch)

Info Value
Patch Name Patch_20200114_TPS-3653_v1-7.1.1
Release Date 2020-01-14
Target Version 20181026_1147-7.1.1
Product affected Talend ESB Runtime

Introduction

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

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

Fixed issues

This patch contains the following fixes:

  • TPS-3653: [7.1.1] The connection from TAC to Runtime has been permanently lost (TPSVC-12684)
  • TPS-3465: [7.1.1] When contexts are used in a DB component for connection fields and then published to nexus3, the job fails with a connectivity error in TAC. (TPSVC-8790) - Talend Runtime
  • TPS-3320: [7.1.1] Timeout when trying to connect to JMX port 8888 (TESB-26434)
  • TPS-3138: [7.1.1] CreateProcess error=206, The filename or extension is too long (TPSVC-6838)
  • TPS-3033: [7.1.1] When contexts are used in a DB component for connection fields and then published to nexus3, the job fails with a connectivity error in TAC (TPSVC-8790)
  • TPS-2984: [7.1.1] Swagger UI not displayed (TESB-25111)
  • TPS-2887: [7.1.1] JobServer connection from JobServer side (TPSVC-6981)
  • TPS-2828: [7.1.1] Talend 7.1.1 - SSH issue connecting to karaf (TESB-24169)
  • TPS-2822: [7.1.1] Not possible to use Event Monitor if SAM Server not started (TESB-24308)

Prerequisites

Consider the following requirements for your system:

  • Talend ESB Runtime 7.1.1 must be installed.

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

  • Current patch must be installed together with TPS-3669 for Talend Administration Console

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

Existing Container

  • Stop Runtime Container : logout, system:shutdown or (CTRL+D)
  • 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-3653
|           patch.commands
├───system  : existing dir superseeded by patch
│   ├───... : existing dir
│   ├───... : directories from patch
├───...
  • Start Runtime Container
  • Execute source patches/TPS-3653/patch.commands from Runtime console
  • Ensure directory <container>/patches/TPS-3653/ contains two new log files : xxx-init.log and xxx-installed.log
  • Restart Runtime Container