Working with TIDManager Configurations
The Transaction Identification Manager (TIDManager) is used to ensure exactly-once delivery for the transaction data between the SAP system and the adapter.
The TIDManager guarantees that no transactional data is duplicated in case of communication errors between the adapter and the SAP system.
- Outbound Configurations
Multiple Publication Service or Request-Response Invocation Service services (for tRFCs) use the same program ID and run in a load-balanced fashion.
Outbound configurations sharing the same program ID must refer to the same remote TIDManager configuration.
- Inbound Configurations
Mutiple Subscription Service or Request-Response Service services (for tRFCs) run in a load-balanced fashion.
Interactions between the Adapter Configuration and the TIDManager Server Configuration
After the adapter configuration is set for the remote TID Management mode, the adapter configuration invokes the TIDManagement operations on the remote TIDManager server in the TIBCO environment. The adapter configuration and the TIDManager server can interact on TIBCO Rendezvous, which is the default setting, or JMS transports.
The TIDManager server maintains the status of each Transaction Identifier (TID) associated with the transaction executed by the adapter. The TIDManager server creates and maintains a local file system of a TID file that maintains the TID status.
In the Transports tab of the Adapter for SAP Configuration editor, ensure that the TID_RPC_CLIENT or the TID_JMS_RPC_CLIENT client of the TIDManager session is correctly configured for each adapter configuration. For more information, see the Transports Tab of the adapter configuration.
The subject of the TID_RPC_CLIENT or the TID_JMS_RPC_CLIENT client in the adapter configuration has to match that of the TID_RPC_SERVER or the TID_JMS_RPC_SERVER client in the TID Manager configuration. For more information, see the Transports Tab of TIDManager configuration.