Resendable Transactions

Resendable transactions can be re-transmitted from TIBCO BusinessConnect to a trading partner or from TIBCO BusinessConnect to a private process. Each protocol defines the set of resendable states, which you can determine by looking at the State list on the Resendable Transactions tab.

Note 

The entire AESchema is stored in the fields REQUEST_FROM_PP and SEND_TO_PP fields in the audit log, since this is required for the resend.

 

Note 

Only transactions for the current transport are listed under resendable transactions: if JMS is the current transport, only JMS transactions are listed.

When resending messages to the private process, such as the messages RESPONDER.REQUEST and INITIATOR.RESPONSE that were previously smart-routed, the smart route ID is re-evaluated upon the re-transmission. This allows a different back office process to handle the re-transmission of the message to the private process.

Enabling Transaction Resend

To enable the resend feature, you must enable the inclusion of message contents in log entries. See TIBCO BusinessConnect™ Installation and Configuration, "Audit, Non-Repudiation and Runtime Database Configuration."

Resending a Transaction

To resend a transaction, perform following steps:

1. Expand BusinessConnect > Log Viewer > Resendable Transactions for the selected protocol.
2. Configure the options.
3. Select the resendable state in the State list.
4. Click Search and select the checkbox of the transaction to resend.
5. Resending a message could be identical to making a new message request, depending on the state that was chosen, and can result in multiple transactions of the same request.
6. Click Resend. For outbound documents, clicking Resend retransmits the document to the trading partner. For inbound documents, clicking Resend resends the message to the private process.

Warning 

Use with caution. If the resend request is activated before the current transaction completes or returns an error, the outcome is beyond control of the protocol.