Xa distributed transactions

Xa distributed transactions

Xa

The XA protocol is first proposed by Tuxedo and presented to the X/open organization as the interface standard for the Resource Manager (database) and transaction manager. Currently, major database manufacturers such as Oracle, Informix, DB2, and Sybase provide support for XA. The XA protocol uses a two-phase commit method to manage distributed transactions. The XA interface provides a standard interface for communication between the resource manager and the transaction manager. The XA protocol consists of two sets of functions, beginning with Xa_ and beginning with Ax_.

Introduction edit depends on context, XA has multiple meanings. The XA in our common database connection transaction refers to the specification of distributed transaction processing proposed by X/open organization. The XA specification primarily defines the interface between the transaction manager (Transaction Manager) and the local Resource manager. Some say that XA is the abbreviation of eXtended Architecture, In fact, I think this is just a coincidence. EXtended Architecture is a driver architecture for CD ROM. Action edit the following function to enable the transaction manager to perform operations on the resource Manager: 1) Xa_open,xa_close: Establish and close the connection to the resource manager. 2) Xa_start,xa_end: Start and end a local transaction. 3) Xa_prepare,xa_commit,xa_rollback: Pre-commit, commit, and rollback a local transaction. 4) Xa_recover: Rolls back a transaction that has been pre-committed. 5) Ax_ begins with a function that allows the resource manager to dynamically register in the transaction manager and can operate on XID (TRANSACTION IDS). 6) Ax_reg,ax_unreg; allow one resource manager to dynamically register or unregister in a single TMS (TRANSACTION MANAGER SERVER)

Xa distributed transactions