SAP TIDManager

You can use the SAP TIDManager shared resource to manage the check of duplicate IDoc messages published from the SAP system or check for duplicate tRFC or qRFC calls from the SAP system.

The SAP TIDManager shared resource is used in IDoc Listener and RFC BAPI Listener activities.

Note: The SAP TIDManager created in the shared module does not set to default, when SAP Plugin activities are created in the application module. User needs to manually select the SAP TIDManager from the shared module.

General

In the General panel, specify the package where the shared resource is stored in the Package field, and the name to be displayed as the label for the shared resource in the process in the Name field. You can also provide a short description for this shared resource in the Description field.

Basic Configuration

In the Basic Configuration panel, select the TID management mode, and specify the related parameters.

The following table lists the configurations in the Basic Configuration panel:

Field	Visual diff	Module Property?	Description
TID Management resource	Yes	No	The TID management mode. The plug-in provides the following modes: None: the check of duplicate IDoc messages is disabled. If the system or application that receives the IDocs can handle the duplicate IDoc messages, you can select the None mode. Note: When running a process that contains an IDoc Listener activity configured with the None mode, if the EMS server does not start, the IDoc transaction is still confirmed after it is rolled back. Active: the check of duplicate IDoc messages is enabled. When an IDoc is published from the SAP system, the SAP TIDManager shared resource checks if the activity receives a duplicate TID. If the TID is a duplicate, the shared resource does not store its information in the database table and the corresponding message is not processed. Otherwise, the TID information is stored in the database table. The following TID information is stored in the database table: TID status: CREATED, COMMITTED, and CONFIRMED creationDate updateDate In the case of bgRFC, when a row of data where the TID is the same as the last 24 characters of the unit ID and the status is COMMITTED is available in the database table, no transaction confirmation operation is performed in the SAP system.
The following fields are displayed when you select Active from the TID Management resource list:
Database Driver	Yes	Yes	The JDBC driver. For the latest supported databases, see the Readme file.
Database URL	Yes	Yes	The URL of the database to be connected to store the TID information. Note: While configuring the Database URL and specifying the port along with the service name, use the appropriate delimiter / or : according to the database being used.
Login Timeout(msec)	Yes	Yes	The timeout value in milliseconds for logging in to the database. The default value is 30000.
Maximum Connections	Yes	Yes	The maximum number of connections that the plug-in can use in the database connection pool. The default value is 1. Note: You have to configure the maximum number of connections according to the number of messages being processed concurrently by the IDoc Listener activities.
Retry Count	Yes	Yes	The number of times that the shared resource can retry to establish a connection with the database. The default value is 3.
Retry Interval(msec)	Yes	Yes	The time interval in milliseconds between two successive attempts to establish a connection with the database. The default value is 30000. Note: The actual retry interval is longer than the configured interval, because the JDBC driver need time to establish connections and return errors.
Username	Yes	Yes	The valid user name used to log on to the database.
Password	Yes	Yes	The valid password corresponding to the user name.

Note: To support the bgRFC protocol for the IDoc Listener activity, the SAP TIDManager shared resource is modified to handle the unit ID instead of the TID. The unit ID is sent with the transaction by the SAP system. Because the unit ID is longer than the TID and the TID is used as a key for the database used by the SAP TIDManager shared resource, the last 24 characters of the unit ID are used.