Talend Open Studio for ESB Release Notes

7.3.1 Last updated: 2020-02-26 Contents

Copyleft...... 3

System requirements...... 5

Talend Open Studio for ESB: new features...... 6 ESB: new features...... 6 Data Integration: new features...... 6

Talend Open Studio for ESB: bug fixes...... 16

Talend Open Studio for ESB: deprecated and removed items...... 17 Language support...... 17 ESB: deprecated and removed items...... 17 Data Integration: deprecated and removed items...... 17

Talend Open Studio for ESB: known issues and limitations...... 19 ESB: known issues and known limitations...... 19 Data Integration: known issues and known limitations...... 20

Talend Open Studio for ESB: migration...... 21 ESB: migration from 6.x.x to 7.3.1...... 21

Talend Open Studio for ESB: hints and notes...... 23 ESB: hints and notes...... 23

Documentation...... 24

Reporting defects and issues...... 25 Copyleft

Copyleft

Adapted for 7.3.1. Supersedes previous releases. The content of this document is correct at the time of publication. However, more recent updates may be available in the online version that can be found on Talend Help Center. This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/. Notices Talend and Talend ESB are trademarks of Talend, Inc. Talend, Talend Integration Factory, Talend Service Factory, and Talend ESB are trademarks of Talend, Inc. Apache CXF, CXF, Apache Karaf, Karaf, , Camel, , Maven, Apache Syncope, Syncope, Apache ActiveMQ, ActiveMQ, Apache , Log4j, , Felix, Apache ServiceMix, ServiceMix, , Ant, , Derby, , Tomcat, Apache ZooKeeper, ZooKeeper, , Jackrabbit, Apache Santuario, Santuario, Apache DS, DS, , Avro, Apache Abdera, Abdera, , Chemistry, Apache CouchDB, CouchDB, , Kafka, , Lucene, Apache MINA, MINA, , Velocity, Apache FOP, FOP, Apache HBase, HBase, , Hadoop, , Shiro, Apache Axiom, Axiom, Apache Neethi, Neethi, Apache WSS4J, WSS4J are trademarks of The Apache Foundation. Eclipse Equinox is a trademark of the Eclipse Foundation, Inc. Hyperic is a trademark of VMware, Inc. Nagios is a trademark of Nagios Enterprises, LLC. All brands, product names, company names, trademarks and service marks are the properties of their respective owners. License Agreement The described in this documentation is licensed under the , Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.html. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software developed at AOP Alliance (Java/J2EE AOP standards), ASM, AntlR, Apache ActiveMQ, Apache Ant, Apache Avro, Apache Axiom, , Apache Axis 2, , Apache CXF, Apache Camel, Apache Chemistry, Apache Common Http Client, Apache Common Http Core, , Apache Commons Bcel, Apache Commons JxPath, Apache Commons Lang, Apache Derby Database Engine and Embedded JDBC Driver, , Apache Hadoop, , Apache HttpClient, Apache HttpComponents Client, , Apache Log4j, Apache Lucene Core, Apache Neethi, Apache POI, , -Jms, Apache Tomcat, Apache Velocity, Apache WSS4J, Apache WebServices Common Utilities, Apache Xml-RPC, Apache Zookeeper, Box Java SDK (V2), CSV Tools, DataStax Java Driver for , Ehcache, Ezmorph, Ganymed SSH-2 for Java, Google APIs Client Library for Java, Google Gson, Groovy, Guava: Google Core Libraries for Java, H2 Embedded Database and JDBC Driver, HsqlDB, Ini4j, JClouds, JLine, JSON, JSR 305: Annotations for Software Defect Detection in Java, JUnit, Jackson Java JSON-processor,

3 Copyleft

Java API for RESTful Services, Jaxb, Jaxen, Jettison, Jetty, Joda-Time, Json Simple, MetaStuff, Mondrian, OpenSAML, Paraccel JDBC Driver, PostgreSQL JDBC Driver, Resty: A simple HTTP REST client for Java, Rocoto, SL4J: Simple Logging Facade for Java, SQLite JDBC Driver, Simple API for CSS, SshJ, StAX API, StAXON - JSON via StAX, Talend Camel Dependencies (Talend), The Castor Project, The Legion of the Bouncy Castle, W3C, Woden, Woodstox : High-performance XML processor, XML Pull Parser (XPP), Xalan-J, Xerces2, XmlBeans, XmlSchema Core, Xmlsec - Apache Santuario, Zip4J, atinject, dropbox- sdk-java: Java library for the Dropbox Core API, google-guice. Licensed under their respective license.

4 System requirements

System requirements

Users should refer to the Talend Installation and Migration Guide on the Talend Help Center (http:// help.talend.com) for more information on Installation and System Requirements.

5 Talend Open Studio for ESB: new features

Talend Open Studio for ESB: new features

ESB: new features

Feature Description

Core Framework updates • Apache Karaf 4.2.7 • Apache CXF 3.3.4 • Apache Camel 2.24.2 • Apache ActiveMQ 5.15.10 (patched, including a critical post 5.15.10 fix)

Log4j2 support Talend ESB Studio and Runtime supports now also Log4j2 (default for new projects).

cConfig 3rd Party Module/Jar selection harmonization The Route Builder cConfig component is now setup to use the 3rd Party Module / Jar selection dialog as used in tLibraryLoad and Routes/Beans already in previous versions.

Data Integration: new features

Feature Description

Online help for components on pressing F1 Starting from Talend 7.3, by default, pressing F1 on a component will open the relevant documentation on Talend Help Center using the default Web browser. To switch to offline help, go to Window > Preferences > Talend > Components and clear the Enable online help for components check box. Before using offline help, subscription users need to install the Talend Help package by following the instructions when switching to offline help, or going to Help > Install Additional Packages.

Rotating encryption keys Talend Studio now allows you to rotate the following two encryption keys by adding a new version of the key with an empty value in the encryption key configuration file. • the system encryption key: for encrypting properties and nexus passwords

6 Talend Open Studio for ESB: new features

Feature Description

• the routine encryption key: for encrypting passwords of generated Jobs

Log4j 2 support Talend Studio now supports Apache logging utility Log4j 2 in components and allows you to enable or disable Log4j 2 loggers and customize the configuration globally for the project.

Note: If you need to deploy your Jobs to Talend Cloud, the use of Log4j 2 requires Talend Remote Engine 2.8.1 or higher.

Redshift SSO support with Ping Federate in metadata wizard The Login and Password fields have been added in the Database Connection metadata wizard for Redshift SSO.

7 Talend Open Studio for ESB: new features

Feature Description

Metadata Bridge version upgrade The version of Talend Metadata Bridge has been updated to 10.1.

New components available The following new components are now available. • tSnowflakeCommit, tSnowflakeRollback • tAzureAdlsGen2Input, tAzureAdlsGen2Output • tWorkdayInput

New option available: Connection timeout The Connection timeout option is added to the Advanced settings view. Components concerned: • tFTPFileExist, tFTPPut, tFTPConnection, tFTPDelete, tFTPFilelist, tFTPFileProperties, tFTPGet, tFTPRename

Excel 2007 xlsm support This feature enables accesses to Excel 2007 files (with the extensions of .xlsx and .xlsm) through the Read excel2007 file format (xlsx / xlsm) and the Write excel2007 file format (xlsx / xlsm) options. Components concerned: • tFileInputExcel, tFileOutputExcel

Excel 2007 password support This feature allows the tFileInputExcel component to read password-protected Excel 2007 (and later) files given that the passwords are available; it also allows the tFileOutputExcel component to set passwords for Excel 2007 (and later) files. Components concerned: • tFileInputExcel, tFileOutputExcel

tSetProxy: Https proxy with authentication This feature allows for connections to a basic authentication -enabled Https proxy server through the Use authentication , Proxy user, Proxy password, and Enable Basic

8 Talend Open Studio for ESB: new features

Feature Description

Authentication Header (in the Advanced settings view) options. Component concerned: • tSetProxy

tJDBCInput: prepared statements This feature enables you to query a database using a prepared statement through the Use PreparedStatement option in the Advanced settings view. Component concerned: • tJDBCInput

AWS server-side encryption (SSE) for SQS queues Components concerned: • tSQSConnection, tSQSInput, tSQSMessageCha ngeVisibility, tSQSMessageDelete, tSQSOutput, tSQSQueueAttributes, tSQSQueueCreate, tSQSQueueDelete, tSQSQueueList, tSQSQueuePurge tPostgresqlOutput: new option available The tPostgresqlOutput component provides the Convert column and table to lowercase option in the Advanced settings view, to put column names of newly created Postgres tables in lower case.

9 Talend Open Studio for ESB: new features

Feature Description

tServiceNowInput: combined filtering conditions This feature allows for combined filtering conditions (combined with AND and OR operators) for retrieving data from ServiceNow through the Advanced Query field in the Advanced settings view.

tRunJob: customizable Child Job JVM argument This feature provides the following two ways in the Advanced settings view for setting JVM arguments for the Job to be called or processed (Use dynamic job needs to be selected in the Basic settings view). • Use child job JVM arguments • Overwrite child job JVM arguments

tJDBCSCDELT: End date configurable This feature allows you to set the End date for type 2 SCD.

Access control list for S3 components This feature allows you to set access control list (ACL) for the current component through the Access control option in the Advanced settings view.

10 Talend Open Studio for ESB: new features

Feature Description

Components concerned: • tS3Put • tS3BucketCreate

Redshift Bulk components: reuse S3 connection This feature enables Redshift components to reuse existing S3 connections. Components concerned: • tRedshiftUnload, tRedshiftOutputBulk, tRedshiftOutpu tBulkExec, tRedshiftBulkExec

tSetProxy: three new options provided for using proxy The tSetProxy components provides the following three new options. • Use Java Virtual Machine Proxy Configuration • URIs to use proxy • Thread isolated proxy (in the Advanced settings view) See Talend Components Reference Guide for related information.

11 Talend Open Studio for ESB: new features

Feature Description

Setting Kafka connections and configuring Azure EventHub This feature enables you to set Kafka connections and as Kafka cluster configure an Azure EventHub as Kafka cluster.

Using a schema other than the schema of the connection Through the Use alternate schema option in the Advanced settings view, this feature enables you to use a schema other than the one specified by the component that establishes the database connection (Use an existing connection needs to be selected in the Basic settings view). Components concerned: • tAmazonOracleOutput • tRedshiftOutput • tGreenplumOutput • tDB2Output • tInformixOutput • tMSSqlOutput • tOracleOutput • tParAccelOutput • tPostgreSQLOutput • tPostgresPlusOutput • tSAPHanaOutput • tSybaseOutput • tVerticaOutput

tSnowflakeConnection: key pair authentication The tSnowflakeConnection component provides the key pair authentication.

Customizing SET clause This feature generates SET clauses for update operations based on the columns you selected in the Clause SET table in the Advanced settings view (Update needs to be selected

12 Talend Open Studio for ESB: new features

Feature Description

from the Action on data drop-down list in the Basic settings view). Components concerned: • tELTTeradataOutput • tELTOutput

Extending AWS ECS role support to other components This feature makes instance profile credential valid both on Amazon EC2 instances and AWS ECS instances.

SHA2 support SFTP connection now supports SHA2 authentication algorithm. Components concerned: • tFTPConnection • tFTPDelete • tFTPFileExist • tFTPFileList • tFTPFileProperties • tFTPGet • tFTPPut • tFTPRename • tFTPTruncate

New Amazon S3 region options The following new Amazon S3 region options are provided: • US East (Ohio) • Asia Pacific (Hong Kong) • Asia Pacific (Seoul) • Canada (Central) • China (Ningxia) • EU (London) • EU (Paris) • EU (Stockholm) Components concerned: • tRedshiftOutputBulk, tRedshiftOutputBulkExec • tS3BucketCreate, tS3BucketDelete, tS3BucketExist , tS3BucketList, tS3Connection, tS3Copy, tS3Delete, tS3Get, tS3List, tS3Put

New Amazon S3 region options The following new Amazon S3 region options are provided: • US East (Ohio) • Asia Pacific (Hong Kong) • Asia Pacific (Seoul) • Canada (Central) • EU (London) • EU (Paris) • EU (Stockholm)

13 Talend Open Studio for ESB: new features

Feature Description

Components concerned: tSnowflakeOutputBulk, tSnowflakeOutputBulkExec, and tSnowflakeBulkExec tRedshiftBulkExec: the Assume Role option available to For the tRedShiftBulkExec component, in addition to S3 other data source types besides S3 data sources, the Assume Role option is now available to these data sources: EMR, DynamoDB, and Remote host. You can thus set IAM role ARN chains for these four types of data sources.

tSQLTemplateMerge: the Database Type drop-down list The tSQLTemplateMerge component now provides the provides the Snowflake option Snowflake option in the Database Type drop-down list. In addition, the following system SQL templates are provided: • SnowflakeCreateSourceTable • SnowflakeCreateTargetTable • SnowflakeDropSourceTable • SnowflakeDropTargetTable • SnowflakeMerge

tAmazonEMRManage: cluster version upgrade The tAmazonEMRManage component now supports the cluster version EMR 5.15.0, which is the default cluster version when configuring the component. Besides, the support for EMR 4.2.0, EMR 4.1.0, and EMR 4.0.0 is dropped.

ActiveMQ 5.15.10 support Components concerned: • tMomCommit, tMomConnection, tMomInput, tMomMessageIdList, tMomOutput, tMomRollback • tSAPADSOInput, tSAPBApi, tSAPBWInput, tSAPCommit, tSAPConnection, tSAPDataSource Output, tSAPDataSourceReceiver, tSAPDSOInput, tSAPDSOOutput, tSAPIDocInput, tSAPIDocOutput, tSAPIDocReceiver, tSAPInfoCubeInput, tSAPInfoObject Input, tSAPInfoObjectOutput, tSAPODPInput, tSAPRollback, tSAPTableInput

14 Talend Open Studio for ESB: new features

Feature Description

Snowflake JDBC driver 3.11.x support Components concerned in Standard Jobs: • tSnowflakeBulkExec, tSnowflakeClose, tSnowflakeConn ection, tSnowflakeInput, tSnowflakeOutput, tSnowflakeOutputBulk, tSnowflakeOutputBulkExec, tSnowflakeRow

Redshift JDBC driver 1.23.7.1061 support Components concerned in Standard Jobs: • tRedshiftBulkExec, tRedshiftClose, tRedshiftCommit, tRedshiftConnection, tRedshiftInput, tRedshiftOutpu t, tRedshiftOutputBulk, tRedshiftOutputBulkExec, tRedshiftRollback, tRedshiftRow, tRedshiftUnload

MySQL driver 8.0.18 support (MySQL 4 support dropped) Components concerned in Standard Jobs: • tMysqlCDC, tMysqlClose, tMysqlColumnlist, tMysqlCommit, tMysqlConnection, tMysqlInput, tMysqlInvalidRows, tMysqlLastInsertId, tMysqlOutput, tMysqlOutputBulk, tMysqlOutputBulkExec, tMysqlRollback, tMysqlRow, tMysqlSCD, tMysqlSCDELT, tMysqlSP,tMysqlTableList, tMysqlValidRows

Vertica DB 9.3.1 support Components concerned: • tVerticaBulkExec, tVerticaClose, tVerticaCommit, tVerticaConnection, tVerticaInput, tVerticaOutput , tVerticaOutputBulk, tVerticaOutputBulkExec, tVerticaRollback, tVerticaRow, tVerticaSCD

Postgres 12.1 support Components concerned: • tPostgresqlCDC, tPostgresqlClose, tPostgresqlCom mit, tPostgresqlConnection, tPostgresqlInput, tPostgresqlInvalidRows, tPostgresqlOutput, tPostgresqlOutputBulk, tPostgresqlOutputBulkExec, tPostgresqlRollback, tPostgresqlRow, tPostgresqlSCD, tPostgresqlSCDELT, tPostgresqlValidRows

MariaDB 10.x support (MariaDB JDBC driver upgraded to Components concerned in Standard Jobs: 2.5.3) • tCreateTable • tELTMysqlMap • tMysqlBulkExec, tMysqlConnection, tMysqlInput, tMysqlOutput, tMysqlOutputBulkExec, tMysqlRow, tMysqlSCD, tMysqlSCDELT, tMysqlSP, tMysqlCDC • tJDBCClose, tJDBCColumnList, tJDBCCommit, tJDBCConnection, tJDBCInput, tJDBCOutput, tJDBCRollback, tJDBCRow, tJDBCSCDELT, tJDBCSP, tJDBCTableList

Default Salesforce endpoint updated The default Salesforce endpoint updated as: https:// login.salesforce.com/services/Soap/u/47.0.

Netsuite endpoint updated Netsuite endpoint updated as: https:// webservices.netsuite.com/services/ NetSuitePort_2019_2 (API version 2019.2 required).

15 Talend Open Studio for ESB: bug fixes

Talend Open Studio for ESB: bug fixes

In addition to the new features, a number of minor improvements within the entire products and significant bug fixes have been made. See the corresponding Change Logs on our bug tracking system for more details on the individual issues:

Module Change Log

ESB https://jira.talendforge.org/issues/?filter=31371

16 Talend Open Studio for ESB: deprecated and removed items

Talend Open Studio for ESB: deprecated and removed items

Language support

From the 7.3 release onwards, the community-based UI localization system (Babili) has been decommissioned. All localization of Talend products is now handled internally by Talend. This means that the scope of languages available in the products will be restricted to French, Japanese and (partially) Chinese so that Talend can maintain and support them over time. For the 7.3 release itself, all community languages and their partial translations are still available. Talend reserves the right to remove these languages in subsequent releases.

ESB: deprecated and removed items

Item Description

BPM: Expose Process as Service The support for creating a Rest or SOAP Service directly from a Bonita BPM Process is deprecated from 7.0.1 onwards.

BPM: ESB Connectors The ESB REST, SOAP Data Service and ESB Route connector for Bonita BPM is deprecated from 7.0.1 onwards.

SAM Server The SAM Server is deprecated from 7.0.1 onwards as we plan to combine the SAM and Event Logging Feature into one solution within a future release of Talend ESB. Nevertheless the feature to capture Service Activity Events on Talend Runtime will still be possible. But the way we capture them and the way we transport and handle them on the server side will change in a future version and we will no longer provide an explicit SAM Server.

SWAGGER UI The SWAGGER UI within RESTful Data Services and Routes (tRESTRequest / cREST) are deprecated. We plan to provide a similar feature with the API design and testing. The product portfolio will also be added in future Talend Cloud of 7.x versions.

tRunJob Support for Data Service and Route use cases The use of tRunJob for ESB use cases within Data Services and Routes is deprecated. For the current release please see also ESB: known issues and known limitations on page 19.

Data Integration: deprecated and removed items

Feature Description

Log4j 1 The Apache Log4j 1 logging utility in components is deprecated from Talend 7.3 onwards.

17 Talend Open Studio for ESB: deprecated and removed items

Feature Description

MicrosoftAX components The following MicrosoftAX components are removed from Talend 7.3 onwards: • tMSAXInput • tMSAXOutput

Sage X3 components The following Sage X3 components are removed from Talend 7.3 onwards: • tSageX3Input • tSageX3Output

OleDB components The following OleDB components are removed from Talend 7.3 onwards: • tOleDBInput • tOleDBOutput • tOleDBRow

CentricCRM components The following CentricCRM components are removed from Talend 7.3 onwards: • tCentricCRMInput • tCentricCRMOutput

SugarCRM components The following SugarCRM components are removed from Talend 7.3 onwards: • tSugarCRMInput • tSugarCRMOutput

SAS components The following SAS components are removed from Talend 7.3 onwards: • tSasInput • tSasOutput

SPSS components The following SPSS components are removed from Talend 7.3 onwards: • tSPSSInput • tSPSSOutput • tSPSSProperties • tSPSSStructure

18 Talend Open Studio for ESB: known issues and limitations

Talend Open Studio for ESB: known issues and limitations

ESB: known issues and known limitations

We encourage you to consult the JIRA bug tracking tool for a full list of open issues: https://jira.talendforge.org/issues/?filter=31370 All ESB use cases (Routes, REST and SOAP Data Services) require Java 8.

Studio

Limitation Description

Java PSU not supported Talend is only supported on Java CPU Versions, not Java PSU. Some users reported problems using Talend Studio with Java PSU versions (such as jdk8_u92), but when reverting to a Java CPU Version (such as jdk8_u91) the problem was resolved. See also: http://www.oracle.com/technetwork/java/javase/ cpu-psu-explained-2331472.html

Only WS-I Basic Profile compliant WSDL documents are All WSDL service descriptions should be at least WS-I supported Basic Profile compliant if you want to use them in Talend Studio. See http://ws-i.org/deliverables/workinggroup.aspx? wg=basicprofile%20for%20more%20information. Other WSDL documents might also work but they are more likely to fail.

tRunJob is supported with limitations The tRunJob component is supported with limitations, which means that only S4 (Minor) support cases are accepted and no patches are provided. If you use tRunJob within Data Services and Routes (with cTalendJob), support is provided on a "best effort" basis only. In most cases, there are class loading issues which can sometimes be resolved but not always. This is because tRunJob is not designed to work in a Service/Route style (ESB) deployment, so regular support is not provided if you decide to use it, even though it may work in many cases. If you used tRunJob in the past, it is recommended to change your Job Design to use Joblets instead. For DI and non-ESB use cases, it is still a valuable component and will have full support as before. Additionally, the Use dynamic job option is not supported within ESB Routes or Data Services at all.

Issue Workaround

Route Builder beans cannot be organized in packages None [TESB-3701]

19 Talend Open Studio for ESB: known issues and limitations

Issue Workaround

Beans in a route build can be used to add Java code for the route builder routes, however all beans are currently located in one single package.

XML payload content is not fully displayed in trace or debug If you need to see the XML data you can place a tLogRow mode component anywhere in your models. Keep in mind that Talend Studio also allows you to disable this component, so When starting a Data Service Job in trace/debug mode, the that you can enable it for testing inside Talend Studio, but content of the Document fields of the flows is not displayed disable it for export or publishing. fully - only the first line of the XML payload is shown.

Filter can be applied with the CI for ESB to limit the Data A recommendation would be to name the Job(s) with the Services and Routes which get built and deployed by the same name as the Route with any extra details after the CI Builder maven plugin. Nevertheless when a Route uses Route name. By this, the Route and the Job(s) would have cTalendJob, it will only work in case the Job and the Route the same starting name and would apply to a filter on this are both part of the filter (criteria). partial name. Alternative you can build the entire project where this limitation would also not exists.

Runtime

Issue Workaround

OSGi Container fails to log messages that were sent to If you encounter this issue, you can run the same scenario system.err / system.out [TESB-11603] in Console mode as the system.err and system.out will show up on the console. In the tesb.log file you will not see any messages which were sent via system.err or system.out.

Data Integration: known issues and known limitations

We encourage you to consult the JIRA bug tracking tool for a full list of open issues: https://jira.talendforge.org/issues/?filter=31260

20 Talend Open Studio for ESB: migration

Talend Open Studio for ESB: migration

ESB: migration from 6.x.x to 7.3.1

Studio

Item Description

ESB Studio upgrade The ESB Studio requires a new installation. You need to export your 6.x, 7.0, 7.1 or 7.2 projects from your local workspace and import the project with the ESB Studio 7.3.1.

Studio project upgrade Studio projects can be used without any manual migration. When the Data Services, Jobs and Routes are opened in the ESB Studio, the components that need changes will be upgraded automatically.

Runtime

Item Description

ESB Runtime upgrade The ESB Runtime (OSGi Container) requires a new installation. See also Compatibility notes on page 21 for details.

Compatibility notes

Item Description

Talend ESB container migration If you want to run your existing Data Services or Routes on the new 7.3.1 Container, you need to re-build, re-publish and re-deploy the Studio models to use the latest code changes. We support the mixed installation and use of Talend ESB container 6.x with Data Services and Routes generated by Talend ESB Studio 6.x and the Talend ESB Infrastructure Services in 7.3.1.

Studio Routes migration From 6.3.1 onwards, the cMessageEndpoint Libraries are not shipped with the ESB Studio anymore. For more information about how to use Routes generated by ESB Studio older than 6.3.1, see the /esb/Readme_cMe ssageEndpoint_Libraries.txt for details.

Studio Routes - Bean Migration The migration from 6.x to 7.3 needs to consider that Beans are now built on their own (independent of the Route). This is different from 6.x and has a side effect in cases where cConfig is used for both the Route and the Beans to get a related library loaded for Beans. In 7.x the use of cConfig is limited to Routes only (which was also the original use case) while Beans must load external libraries via the Edit Bean Libraries dialog. As all beans are compiled together it is sufficient to assign the libraries needed to one Bean or to assign each library explicitly to the related Bean which needs the library.

21 Talend Open Studio for ESB: migration

Item Description

In version 7.0, 7.1 or 7.2 there is one more limitation which requires to use org.talend.libraries as fixed Group ID and 6.0.0-SNAPSHOT as fixed version in the case the same library is needed by cConfig and Beans. In the above mentioned versions the cConfig can only use the fixed Group ID and version while with 7.3 custom version is allowed and the same dialog and functionality is shared between cConfig and the Edit Bean Libraries dialog. All 7.x versions (7.0 to 7.3) still require a fixed Group ID org.talend.libraries.

Migration of Studio Jobs using SAP with a Talend Runtime With Talend Runtime 7.x, it is required that the shared Connection Pool connection pool has a fixed name SAP_CONNECTION _POOL. If you have changed it, you need to update your models to use this fixed value.

22 Talend Open Studio for ESB: hints and notes

Talend Open Studio for ESB: hints and notes

ESB: hints and notes

Studio

Item Description

cAMQP requires the Client ID to be set When you use the cAMQP component in the Route Builder, make sure you always set the Client ID to a unique value which is not used in other Routes (the clientId header in cAMQP advanced settings.) If more than one cAMQP based Routes are executed in the same Talend Runtime container and the Client ID is not set, you will see some exceptions like: org.springframework.jms.UncategorizedJmsEx ception: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Broker: localhost - Client: tlnd-spappala(6968):2 already connected from tcp://127.0.0.1:49729

Runtime

Item Description

Copying an ESB Container will lead to unexpected A Talend Runtime container which was started once behaviour can't be copied to a different directory or machine. It is recommended to always use a fresh (never started) container that is shipped with the product.

23 Documentation

Documentation

Talend Help Center Find out more about how to get the most out of your Talend products on the Talend Help Center: http://help.talend.com.

Open issues We encourage you to consult the JIRA bug tracking tool for a full list of open issues: https://jira.talendforge.org/issues/?filter=18375

24 Reporting defects and issues

Reporting defects and issues

As a customer of Talend with a valid support contract, you can use our Talend Online Helpdesk or you can contact our customer support by phone and e-mail as stated in your contract. Often the following information is needed and would help us to more easily evaluate your issue: • Product and Version which you used (for example, Talend Data Fabric 7.3.1) • Operating System, for example, Windows Server 2008 R2 SP1 (64bit) • Version of Java Platform JDK / JRE in use (for example, ORACLE JDK 1.8.0_161) • Log files and/or screenshots Also, in order to ensure that the technical support team has sufficient information to help you, describe at least the following in detail: • your actions up to the point when the problem occurred • the results you expected In addition to our support helpdesk, you can also use our community support tools: • Talend Community. • You can also look into the Talend Bug Tracker. • Just keep in mind that only cases you create via one of the Talend Support channels in our Talend Support Helpdesk are treated under the service level agreements we provided in the related contract to you.

25