Resend Transactions

Resend transactions can be re-transmitted from TIBCO BusinessConnect™ Container Editionto a trading partner or from TIBCO BusinessConnect™ Container Edition to a private process.

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.

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.

Resending a Transaction

To resend transactions, perform the following task:

  1. On the Audit Trail page, click protocol to view the protocol transactions.
  2. On the Transactions page, from the Select dropdown list, select Resend, click = (Equals) operator, and then select Sendable to filter the transactions that can be sent again. Click Find.
    This displays entire list of transactions you can resend.
  3. To resend a transaction, you can do one of the following:
    a. Expand the transaction, click audit event you want to resend, and then click Resend.
    b. Select one or more transactions from the filtered list and click Resend. The transaction is sent again to a private process or a trading partner as required.
    4. Note: For sending multiple transactions, you must unselect the Expand/Collapse for similar Transaction ID checkbox on Settings dialog. This is required because the collapsed transactions when selected cannot be directed to a specific audit event for resend.

  4. After you click Resend, the Resend button remains disabled until the resend is complete.

  5. Using resend from Search filter, you can search for transactions that are:

  • Waiting: The transactions that are waiting to be picked by poller server to resend.

  • Completed: The resend process of transactions is complete.

  • Expired : The transactions that failed to resend.

After the transaction is sent, new transaction events are generated with resend displayed in the transaction event name.

The Resend button is not available for the state that has been sent already, but it is available for the original state, allowing you to resend the request multiple times.