MDN Receipts and Business Acknowledgments
An MDN receipt is a transport-level acknowledgment that does not guarantee that the document from the Initiator was validated by the Responder’s translator. An MDN receipt merely states that the document was received and its contents were verified for integrity. No document validation takes place before an MDN receipt is sent back. An acknowledgment is a business level response that is sent back if required by the specified protocol in use.
A Responder might refuse an MDN receipt if the Responder does not recognize from which trading partner a message originated and is not listed in the Responder’s list oftrading partners.
Here are some conditions in which the Responder sends back an ERROR MDN receipt:
- The Responder does not have the certificates of the trading partner installed so it cannot verify the contents of the inbound document if a signed document was sent and an MDN receipt was requested.
- The Responder cannot decrypt the inbound message from the trading partner as it might have not been encrypted with a valid set of certificates.
MDN Messages Sent to Private Processes
Miscellaneous message types are available for the protocol of the specified TIBCO BusinessConnect Container Edition shared configuration resource. These messages can occur when the AS1, AS2 or Email transports are used and receipts (MDNs) are utilized.
The miscellaneous messages that can be received for MDN receipts are MDN Alert messages and MDN Timeout messages. An MDN Alert is sent to the private process when an MDN receipt is sent to or received from a trading partner.
If the MDN receipt is requested but was not received from the trading partner before the configured timeout occurs, an MDN Timeout is sent to the private process. See documentation for a specific business protocol for more information.
To learn more about MDN messages sent to Private Processes, see TIBCO BusinessConnect Palette Reference, Receive Misc. Msg.