TID Management resource
|
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
|
The JDBC driver.
For the supported databases, see the
readme file.
|
Database URL
|
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
|
The timeout value in milliseconds for logging in to the database.
The default value is
30000.
|
Maximum Connections
|
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
|
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
|
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
|
The valid user name used to log on to the database.
|
Password
|
Yes
|
The valid password corresponding to the user name.
|