How do TIBCO BusinessConnect tibXML and SOAP plugins handle duplicates?
Article ID: KB0088502
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| Not Applicable | - |
Description
Resolution:
tibXML and SOAP plugins detect and handle duplication for both inbound and outbound transactions.
Singularity of each message is guaranteed by maintaining the BC_DUP table. For each message, BC will calculate a fingerprint based on the MD5 message digest of the message and its attributes (including TPName, transaction id, operation id). If no previous record contains the same finger print, BC will consider this message to be unique.
Outbound traffic:
------------------
Duplicate detection for outbound requests is conditional, based on a flag set through the configuration interface. Detected duplicates are not sent to the Trading Partners (TPs); the Private Process (PP) is notified of the problem.
The outbound responses are conditionally checked based on a flag set through the configuration interface. Detected duplicates are not sent to the TPs; the PP should be notified of the problem.
Inbound traffic:
------------------
Requests received are all checked for duplication. These duplicates are not considered erroneous, and are forwarded to the PP with the appropriate flag set.
All responses received are checked for duplication; similarly to duplicate requests described above, these duplicates are not considered errors, and are forwarded to the PP with appropriate duplicate flag set.
tibXML and SOAP plugins detect and handle duplication for both inbound and outbound transactions.
Singularity of each message is guaranteed by maintaining the BC_DUP table. For each message, BC will calculate a fingerprint based on the MD5 message digest of the message and its attributes (including TPName, transaction id, operation id). If no previous record contains the same finger print, BC will consider this message to be unique.
Outbound traffic:
------------------
Duplicate detection for outbound requests is conditional, based on a flag set through the configuration interface. Detected duplicates are not sent to the Trading Partners (TPs); the Private Process (PP) is notified of the problem.
The outbound responses are conditionally checked based on a flag set through the configuration interface. Detected duplicates are not sent to the TPs; the PP should be notified of the problem.
Inbound traffic:
------------------
Requests received are all checked for duplication. These duplicates are not considered erroneous, and are forwarded to the PP with the appropriate flag set.
All responses received are checked for duplication; similarly to duplicate requests described above, these duplicates are not considered errors, and are forwarded to the PP with appropriate duplicate flag set.
Issue/Introduction
How do TIBCO BusinessConnect tibXML and SOAP plugins handle duplicates?
Feedback
Yes
No
Powered by
