Figure 8 shows the flow of an EDI document with AS packaging sent
over the HTTP transport protocol through the Business Integration Connect
server, for eventual delivery to an EDI back-end system.
In this example, it is assumed that the inbound AS2 message requested an
asynchronous MDN (message disposition notification).
Figure 8. Sequence diagram of the delivery of an EDI document from a participant to an EDI back-end system.

- The AS2 request with the EDI payload enters the Receiver component of
Business Integration Connect.
- The Receiver saves the document to persistent shared storage.
- The Receiver returns an HTTP 200 response to the community
participant.
- The Document Manager picks up the document for processing by the Document
Processing Engine and saves the original document to the non-repudiation
database. The Document Processing Engine processes the document, which
includes:
- Performing decryption, de-enveloping, and structure-level validation
- Performing authentication and authorization and duplicate checks
- Performing content-level validation
- Digitally signing or encrypting the message (or both), if specified by the
configuration.
- Adding header information.
- Saving the final packaged document to the non-repudiation database
- The Delivery Manager sends the document (in this case, using the JMS
transport) to the EDI back-end system.
- A message disposition notification (MDN) is sent to the community
participant.
- The community participant acknowledges the receipt of the MDN by sending
an HTTP 200.
