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.

  1. The AS2 request with the XML document enters the Receiver component of Partner Gateway.
  2. The Receiver saves the document to persistent shared storage.
  3. The Receiver returns an HTTP 200 response to the community participant.
  4. 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:
    1. Performing decryption and verification
    2. Performing authentication and duplicate checks
    3. Determines the sending and receiving of participants based on the business IDs
    4. Determines the payload document type
    5. Based on the sending and receiving partners, AS2 packaging and the XML document type for the participant connection is looked up.
    6. From the participant connection, the Action, Transformation Map (if specified), the document type to send, document attribute values, and gateways are determined.
    7. Performs structural validation per the Action that was specified.
    8. Adds packaging information such as Back-end Integration per the document type to be sent.
    9. Saving the final packaged document to the non-repudiation database.
  5. The Delivery Manager sends the document (in this case, using the JMS transport) to the back-end system
  6. A message disposition notification (MDN) is sent to the community participant.
  7. The community participant acknowledges the receipt of the MDN by sending an HTTP 200.

Copyright IBM Corp. 2003, 2005