Debugging - Cloud - 8.0

SAP

Version
Cloud
8.0
Language
日本語
Product
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
ジョブデザインと開発 > サードパーティーシステム > ビジネスアプリケーション > SAP
データガバナンス > サードパーティーシステム > ビジネスアプリケーション > SAP
データクオリティとプレパレーション > サードパーティーシステム > ビジネスアプリケーション > SAP
Last publication date
2023-09-14

The SAP RFC server receives the IDocs and places these into the JMS topic. One IDoc type results to one topic.

If the embedded JMS broker is used, the topics are not visible. To check what data is stored and to see if messages are received from SAP or consumed by the Job, you need to configure an SAP RFC server that uses an external JMS broker.

Tip: You can use the Apache ActiveMQ as a broker, since it offers a browser-based user interface to see the topics.

The topics are named TALEND.IDOCS.<IDoc Type>. These are set by the consuming Job and the <IDoc Type> that matches the type configured in the tSAPIDocReceiver component.

You can also possibly write SAP trace files. This feature is initially switched off by default, but you can switch it on by setting the configuration file:
#Enable/disable RFC trace (1=on or 0=off)
jco.server.trace=1

The following shows you that a .trc file is written to the top-level directory: