Microsoft Corporation
June 1997
Microsoft® Transaction Server (MTS) provides automatic transactions, which means that transaction requirements are declaratively stated as component properties. MTS automatically begins transactions and commits or aborts these transactions on behalf of the component, based on the component's transaction property.
Automatic transactions work because resource dispensers pass transactions to the resource manager. For example, the ODBC Driver Manager is a resource dispenser for ODBC database connections. When a database connection is requested from a transactional component, the ODBC Driver Manager obtains the transaction from the object's context. The ODBC Driver Manager then associates (enlists) the database connection with the transaction.
If you do not have a resource dispenser, you can build your own using the Microsoft Transaction Server Beta Software Development Kit (SDK), available at http://www.microsoft.com/support/transaction/. See the Resource Dispenser Guide and the samples included with the MTS Beta SDK for more information.
For a resource manager to be able to participate in an MTS transaction, it must support one of the following protocols:
OLE Transactions, the object-oriented, two-phase commit protocol defined by Microsoft, is the preferred protocol. OLE Transactions is based on the Component Object Model (COM) and is used by resource managers in order to participate in distributed transactions coordinated by Microsoft Distributed Transaction Coordinator (DTC). OLE Transactions is supported by Microsoft SQL Server™ version 6.5. See the Resource Manager Guide and the samples included with the MTS Beta SDK for more information on supporting OLE Transactions.
XA is the two-phase commit protocol defined by the X/Open DTP group. XA is natively supported by many Unix databases, including Informix, Oracle, and DB2.
For MTS to work with XA-compliant resource managers, an OLE Transactions-to-XA "mapper," provided by the MTS Beta SDK, makes it relatively straightforward for XA-compliant resource managers to provide resource dispensers that can accept OLE Transactions from MTS and translate to XA. See "Mapping OLE Transactions to the XA Protocol" in the MTS Beta SDK, or contact your resource manager vendor for more information.