1.3.2.2 Scenario 2b: Flowing a Transaction from a Client Application to a Participant Using WS-AtomicTransaction
The client application begins a new OleTx transaction using protocols specified in [MS-DTCO]. The client application also obtains the URI of the Registration Service of a transaction coordinator using protocols specified in [MS-DTCO] and data types specified in this document. The client application then builds a CoordinationContext Element by using the Registration Service URI and the OleTx transaction through the AppClient Role.
In this scenario, the client application also creates a Propagation_Token (PT) from the transaction, as specified in [MS-DTCO] (section 2.2.5.4). The client application then inserts the Propagation_Token in the CoordinationContext Element by using the AppClient Role, and then it flows the CoordinationContext Element in the header of an implementation-specific SOAP message (App-App) to a WS-AtomicTransaction participant.
The participant, which does not support the protocols specified in [MS-DTCO], locates the CoordinationContext Element in the header of the SOAP message and requests activation using the flowed CoordinationContext Element, as shown in the following figure.

Figure 3: Flowing a transaction from a client application to a participant using WS-AtomicTransaction