Sample message flow
The scenario below describes the sequence of events in
a Partner Gateway document exchange scenario.
In this scenario, a partner sends an AS2 packaged XML document
payload over HTTP. Partner Gateway unpackages the document extracting
the XML payload, validates the payload and sends the payload to
the back-end using JMS transport. The Partner Gateway also sends
back an MDN receipt to the partner.
- The AS2 request with the XML document enters the Receiver component
of Partner Gateway.
- 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 and verification
- Performing authentication and duplicate checks
- Determines the sending and receiving of participants based on
the business IDs
- Determines the payload document type
- Based on the sending and receiving partners, AS2 packaging and
the XML document type for the participant connection is looked up.
- From the participant connection, the Action, Transformation
Map (if specified), the document type to send, document attribute
values, and gateways are determined.
- Performs structural validation per the Action that was specified.
- Adds packaging information such as Back-end Integration per
the document type to be sent.
- 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 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.
