Export (0) Print
Expand All

Background for TIP Transactions

TIP transactions implicitly assume a two-pipe architecture. In this architecture, the messages describing the work flow on one pipe, the application-to-application pipe, and messages controlling the transaction flow on another pipe, the transaction manager-to-transaction manager pipe. The only exception to this rule is that a few of the transaction propagation messages flow on the application-to-application pipe. These propagation messages are required to establish transaction context on every application that is going work on the transaction.

TIP transaction processing also requires that the application establish this transaction context with the help of its transaction manager. There are two models that can be used to establish transaction context on applications involved in the transaction. They are the push model and the pull model.

The push model requires the following steps to flow the transaction context from Application A to Application B:

  1. Application A asks its transaction manager, TM-X, to propagate the transaction to the Application B transaction manager, TM-Y.

  2. Application A gets a handle from TM-X that identifies the transaction on TM-Y.

  3. Application A sends the handle over to Application B.

  4. Application B asks TM-Y to establish transaction context for itself using the handle that it received in step 3.

In contrast, the pull model requires the following steps:

  1. Application A gets a handle for the transaction from TM-X. This handle identifies both the transaction and the network location of TM-X.

  2. Application A sends the handle over to Application B.

  3. Using the handle it received in step 3, Application B asks TM-Y to propagate the transaction from the transaction manager identified in the handle—that is, TM-X. This step also establishes transaction context for Application B.

ms679484.note(en-us,VS.85).gifNote
The TIP service feature is deprecated. The TIP service feature and all related APIs are available for use in the operating systems listed in the Requirements sections of the reference topics for those APIs. They might be unavailable in subsequent versions of the operating system. You might consider using the WS-AtomicTransaction (WS-AT) protocol as a replacement transaction coordination and propagation technology. WS-AT support is provided through Windows Communication Foundation (WCF) as part of the .Net Framework. For more information about WS-AT support in the .Net Framework see Transactions.

See Also

Show:
© 2014 Microsoft