Managing XA Transactions
The DTC can act as either an XA-compliant resource manager or a transaction manager. When the DTC is acting as an XA-compliant resource manager, it allows Microsoft SQL Server, Microsoft Message Queuing, and other OLE Transactions-compliant resource managers to participate in transactions controlled by X/Open DTP XA-compliant transaction processing monitors such as Encina, TopEnd, and Tuxedo.
The DTC displays the superior XA transaction manager's transaction identifier (XID) in the transaction properties window, which you can access by right-clicking the transaction in the Transaction List window of the Component Services administrative tool. This XID can be used to resolve any in-doubt transactions in the DTC that have an XA transaction manager as a superior. You can use the Component Services administrative tool for the XA transaction manager to determine the outcome of the transaction and force the outcome for the corresponding transaction on the subordinate DTC.
|Please attempt to reconnect the XA transaction manager with the DTC before manually trying to resolve the transaction.|
When the DTC is acting as an XA-compliant transaction manager, it allows Oracle, IBM DB/2, Sybase, Informix, and other XA-compliant resource managers to participate in transactions controlled by the DTC. When displaying information for transactions spanning XA-compliant resource managers, the DTC does not display the XID of the transaction. Instead, the DTC displays the OLE Transactions Unit of Work identifier (UOW) for the transaction.
You can use the Component Services administrative tool for the XA-compliant resource manager to correlate transactions in the DTC.
For more information, please see the XA specification.