Outbound

The external partner sends a pull request to the internal partner. The internal partner sends the ebMS3 message to the external partner when the pull request is authenticated and authorized and can request a response. The external partner responds synchronously or asynchronously.

Submit operation

The following figure illustrates the submit operation of an outbound message that is sent with one-way pull pattern.
Illustration of the submit operation of an outbound message that is sent with one-way pull pattern
  1. The internal partner produces the message payload and sends the payload with the From and To information to the B2B gateway that is used as the sending MSH.
  2. The MSH of the internal partner parses the From and To party IDs from the trigger message. The MSH of the internal partner matches the internal partner profile from the From party ID and the external partner profile from the To party ID. The MSH determines the following settings of the external partner profile to use for submitting the message.
    • The name of the MPC to submit messages to.
    • Depending on the MPC authentication method, the name of the username token or the validation credential. The name is used as the username for storing messages in the MPC.
  3. The sending B2B gateway saves the message payload into the corresponding MPC.

Deliver operation

The following figure illustrates the deliver operation of an outbound message that is sent with the one-way pull pattern.
Illustrates of the deliver operation of an inbound message that is sent with one-way pull pattern as explained in the following list.
  1. The external partner sends a trigger message with From and To information to the B2B gateway that is used as the MSH of the external partner.
  2. The MSH of the external partner parses the From and To party IDs from the trigger message. The MSH of the external partner matches the external partner profile from the From party ID and the internal partner profile from the To party ID. The MSH determines the following settings of the external partner profile to use for sending the pull request signal.
    • The destination URL to send the pull request signal to.
    • The name of the MPC on the MSH of the internal partner to pull the message from.
    • Depending on the authentication method that the MPC requires, the username token and password, or the certificate that the pull request signal uses to be authorized to pull message from corresponding MPC.
  3. The MSH of the external partner creates a pull request signal message is based on the matched settings. The MSH sends a pull request to the B2B gateway that is used as the MSH of the internal partner.
  4. The MSH of the internal partner authenticates and authorizes the pull request.
  5. The MSH of the internal partner packages the payload in the corresponding MPC into an ebMS3 message based on the ebMS3 settings. The MSH of the internal partner fetches one ebMS3 message from the MPC storage per one pull request. The MSH sends the message to the MSH of the external partner through the response channel of the pull request.
  6. The MSH of the external partner unpacks the received ebMS3 message, and forwards the message to the external partner.
  7. The MSH of the external partner sends another pull request signal message. When a receipt acknowledgment is requested for a received message, the MSH of the external partner sends the receipt signal message to the MSH of the internal partner asynchronously.
  8. The MSH of the internal partner fetches the next message from the MPC storage until no more user messages are available for pulling.