Duplicate Detection
You can utilize the duplicate detection functionality in TIBCO BusinessConnect Container Edition - RosettaNet Protocol to deal with duplicate outbound messages according to your preferences.
Inbound Duplicate Detection
TIBCO BusinessConnect Container Edition - RosettaNet Protocol marks an inbound message as a duplicate if it contains the process identifier of a successfully processed PIP. By default, it forwards such a message to the private process with the isDuplicate field set to true (see Inbound Request Format and Inbound Response Format.
You can change the behavior of TIBCO BusinessConnect Container Edition - RosettaNet Protocol when it detects inbound duplicate messages. The option is:
- Send an automatic response to the trading partner for a duplicate message, for more information, see RosettaNet Configurations for Hosts.
Outbound Duplicate Detection
By default, TIBCO BusinessConnect Container Edition - RosettaNet Protocol does not perform special processing of duplicate outbound messages. You can, however, configure TIBCO BusinessConnect Container Edition - RosettaNet Protocol to detect outbound messages and terminate the processing.
TIBCO BusinessConnect Container Edition - RosettaNet Protocol marks an outbound message from the private process as a duplicate if it contains the process identifier of a successfully processed PIP (in the transactionID field of BCRequestFromPP messages or the responderTrackingID field of BCResponseFromPP messages, see Outbound Request Format and Outbound Response Format for more information). Once outbound duplicate detection is detected, TIBCO BusinessConnect Container Edition - RosettaNet Protocol terminates a transaction as soon as it detects a duplicate outbound message.