Resolution:
Description:
============
The AS2 protocol allows for two types of MDNs (Message Disposition Notifications) over the HTTP/S/CA transport.  This article will describe the difference.

Environment:
==========
BusinessConnect 5.0.0 and above

Resolution:
=========
When using AS2, synchronous receipts are receipts that are sent back on the same HTTP/S/CA channel that initiated the outbound request.  BusinessConnect keeps the outbound channel open and waits for the receipt to be sent back as part of the "200 OK" response from the trading partner.  Similarly, BC's inbound HTTP/S/CA channel will be kept open when an inbound AS2 request is received from a trading partner until BC prepares and returns the MDN.

Asynchronous receipts are what their name implies. They are generated and sent back to the trading partner on a separate HTTP/S/CA channel from the receiving trading partner to the sending trading partner. With asynchronous AS2 messages, a field is included in the message instructing the receiver as to which URL to post the MDN to.  This field is called the "Return-Receipt-URL".  When an AS2 message is sent, the receiver sends back a "200 OK" to close the channel.  The receipt is sent to the sender via a separate HTTP/S/CA channel which the receiver initiates.

See Chapter 17, "Message Disposition Notifications", in the BusinessConnect Trading Partner Administration Manual for more details.

What is the difference between AS2 Sychronous Receipts and Asynchronous Receipts?