Skip to main content Skip to complementary content

TPS-5410

Info Value
Patch Name Patch_20221209_TPS-5410_v1-7.3.1
Release Date 2022-12-09
Target Version 20200219_1130-V7.3.1
Product affected Talend SAP RFC Server

Introduction

This is a self-contained patch.

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:

  • TDI-44295 Studio - Improve performance of SAP Streaming
  • TDI-44841 Issue configuring Talend ELT with streaming
  • TDI-44391 The embedded tomcat version for sap-rfc-serv was still 8.5.31, not 9.0.30 as others.
  • TDI-45536 Multiple SAP Connections from SAP RFC Server
  • TDI-46850 Upgrade ActiveMQ Jars (5.15.15)
  • TDI-46932 tSAPInput component parses TIMS Midnight as null when using dynamic schema
  • TDI-47241 CVE: log4j-api(core)-[2 - 2.16.0)
  • TDI-47325 Cannot create data source(SAP BW version 7.5)
  • TDI-47763 Assess Spring4Shell vulnerability
  • TDI-47861 CVE: tomcat-embed-core 9.0.30 have risk
  • TDI-47869 Authentication Bypass in Talend/tsap-rfc-server
  • TDI-48136 CVE: com.google.code.gson:gson:2.8.0
  • TDI-48715 CVE-2022-42003,CVE-2022-42004, jackson-databind-2.13.2.2jar
  • TDI-48818 Kafka: Denial Of Service (DoS) in Talend/tsap-rfc-server,sap-api and cloud-components

Prerequisites

Consider the following requirements for your system:

  • Talend SAP RFC Server 7.3.1 must be installed. and work with Talend Studio 7.3.1 with patch "R2021-12" or newer

Installation

Installing the patch using Talend SAP RFC Server

  1. Stop the Talend SAP RFC Server
  2. Extract the zip.
  3. Overwrite the {sap rfc server home}/tsap-rfc-server-7.3.1.jar
  4. Adjust the new configuration in {sap rfc server home}/conf/tsap-rfc-server.properties and {sap rfc server home}/conf/named-connections/*.properties ,please refer to README.md file in the patch root folder.
  5. Restart the Talend SAP RFC Server

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!