1. ebMS3 Routing scenarios Part 2

2. MSH A MSH intermediary MSH B 1-way from A to B 1-way/push: A-Int 1-way/push: Int-B Int only forwards the message M1 HTTP 200 M1 1-way from A to B, end-to-end reliable 1-way/push: A-Int 1-way/push: Int-B Int forwards the asynchronous RM Ack HTTP 200 M1 HTTP 200 RM Ack1 (MessageID-preserving Forward) 1-way from A to B, robust 1-way/push: A-Int 1-way/push: Int-B Int forwards the HTTP status code / SOAP fault M1 HTTP 500 / Fault PUSH Scenarios (forward M1, wait for the status code / Fault and forward it) (status codes / Faults are only for each leg) (forward the RM Ack)

3. MSH A MSH intermediary MSH B 1-way from B to A, pulled Two “synchronized pulls” 1-way/pull: A-Int, synchronized with: 1-way/pull: Int-B PullRequest (MessageID-preserving Forward) PULL Scenarios M1 PullRequest (forward the PullRequest, wait for the pulled msge) 1-way from B to A, pulled / decoupled Two non-synchronized pulls, only connected by an MPC in intermediary 1-way/pull: A-Int, decoupled from: 1-way/pull: Int-B PullRequest Whatever message in the Intermediary MPC M1 PullRequest (PullRequest is NOT forwarded) PullRequest Whatever message, here M1 (M1 posted in the Intermediary MPC) Reliable variant : Replace “M1” by “M1 + RM Ack” Optional RM Ack for M1 is pushed from A to B Reliable variant : No end-to-end reliability, but for each leg Intermediary must have RM capability