1.3.2.1 Scenario 2a: Flowing a WS-AtomicTransaction CoordinationContext from a Client Application to a Participant
The client application uses protocols specified in [MS-DTCO] and data types specified in this document to obtain the URI of the Activation Service of a transaction coordinator. The client application then requests a new CoordinationContext (that is, transaction) through the Activation Service URI by using the protocols specified in [WSAT10] or [WSAT11], depending on the implementation of the transaction coordinator.
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 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 2: Flowing a WS-AtomicTransaction CoordinationContext from a client application to a participant