IDoc Listener
Use the IDoc Listener activity to listen to the SAP system and receive IDocs published from the SAP system.
The IDocs are persisted to the TIBCO transport, for example, EMS, and confirmed in the SAP system.
Only IDocs of SAP port type 4x are supported using the tRFC and qRFC protocols.
If you want to control the number of messages being processed concurrently in the activity, choose one of the following configurations:
See Job Tuning for details.
General
In the General tab, you can establish connections to the SAP system and the messaging source separately, and choose an SAP TIDManager shared resource to manage the check of the duplicate IDoc messages.
The following table lists the fields in the General tab:
Field | Module Property? | Description |
---|---|---|
Name | No | The name to be displayed as the label for the activity in the process. |
SAP Connection | Yes | Click
![]() Ensure that you have created an SAP Connection shared resource accordingly first. See Creating and Configuring an SAP Connection for details. Note:
|
SAP TID Manager | Yes | Click
![]() If no matching SAP TIDManager shared resources are found, click Create Shared Resource to create one. For more details, see Creating and Configuring an SAP TIDManager Shared Resource. |
Messaging Source | No | The messaging source where the received IDocs are persisted.
Only the JMS type is supported. |
JMS Connection | Yes | Click
![]() If no matching JMS Connection shared resources are found, click Create Shared Resource to create one. For more details, see the TIBCO ActiveMatrix BusinessWorks documentation. |
Description
In the Description tab, you can enter a short description for the IDoc Listener activity.
Advanced
In the Advanced tab, you can specify the destination used to persist the IDoc received from the SAP system.
The following table lists the fields in the Advanced tab:
Field | Module Property? | Description |
---|---|---|
Sequence Key | No | This field contains an XPath expression that specifies the order in which the process runs. Process instances with sequencing keys that have the same value are executed sequentially in the order in which the process instances were created. |
Custom Job Id | No | This field contains an XPath expression that specifies a custom job ID for the process instance. This ID is displayed in the TIBCO Administrator View Service dialog, and it is also available in the $_processContext process variable. The custom job ID for the process instance. |
IDoc Destination | Yes | The destination used to persist the IDocs received from the SAP system. |