1.3.2.4.2 TIP Pull Propagation Interactions
The following diagram presents the sequence of actions that occur during a synchronous TIP pull propagation of a transaction. This diagram shows a successful synchronous pull propagation operation. For information about failure processing conditions, see Protocol Details (section 3).

Figure 3: Actions performed during a TIP pull propagation
Using the TIP URL for a transaction, the higher-layer business logic requests that the TIP interoperability application (section 1.3.2.1) perform the TIP pull propagation.
The TIP interoperability application sends a "Pull" protocol message to the TIP interoperability provider (section 1.3.2.2). The message contains the TIP URL of the transaction to be pulled. For more information, see Message Type Details (section 2.2.5.1.3).
After receiving the message, the TIP interoperability provider contacts the TIP transaction manager that is referenced by the TIP URL and requests the TIP pull propagation of the transaction.
The TIP transaction manager replies that the pull propagation was successful.
The TIP interoperability provider creates a transaction on the OleTx TM, which it associates with the pulled transaction. As part of that operation, the TIP interoperability provider enlists as a superior in the transaction on behalf of the remote TIP transaction manager. More information is specified in [MS-DTCO] section 3.2.7.12.
The OleTx TM signals that the transaction was created successfully.
The TIP interoperability provider replies with a "Pulled" protocol message to the TIP interoperability application. The message contains the identifier of the transaction that was created as a result of the pull propagation. For more information, see section 2.2.5.1.3.
The TIP interoperability application returns a "Success" result and the identifier of the transaction to the higher-layer business logic.
When all the preceding operations are complete, there is a subordinate-to-superior relationship between the OleTx TM and the TIP transaction manager.