Using the DTC with Other TIP Transaction Managers
This section introduces concepts for application developers building bridges and gateways between the DTC and other Transaction Internet Protocol (TIP) compliant transaction managers. Such bridges and gateways are useful for providing solutions spanning heterogeneous transaction processing systems and component object systems.
In a transaction processing system or a component object system spanning a homogenous environment, the transaction manager communication can use a proprietary protocol. However, in a heterogeneous environment, this communication needs to occur using a well-documented and standardized protocol (for example, TIP, LU6.2). For this reason, the DTC supports the TIP protocol, an Internet Engineering Task Force (IETF) proposed standard.
For example, suppose Application A is using TM-X as its transaction manager and Application B is using TM-Y as its transaction manager. Assuming that Application A has begun a transaction with TM-X, if Application A now wants to request some service from Application B and would like the request to be a part of the transaction that it started, Application A will propagate the transaction to Application B and TM-Y by using the TIP extensions to the OLE Transactions protocol. At commit time, both TM-X and TM-Y will coordinate, and all the work done by Application A and Application B will be committed as an atomic unit.
For more detailed information, see the following topics in this section:
|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.|