Implementation

In order to adhere to the DTP model, the server-implemented Transaction Coordinator provides the ability to manage global transactions. Although the Transaction Coordinator is a private implementation, it fully adheres to the XA protocol in the boundaries of its implementation.

• Because the Transaction Coordinator is a private implementation, it does not have a public interface. There is no mechanism for foreign applications to use the Transaction Coordinator.
• Not every Resource Manager, even XA-compliant, is supported unless explicitly stated.

The implementation specifics of the Transaction Coordinator are:

• It is invoked by a keyword in edaserve.cfg (transaction_coordination_mode=on).
• Every unit of work initiated inside any agent will be started as a global transaction, within this agent.
• Coordination will apply to all currently supported XA-compliant interfaces.
• It cannot be turned off.
• All XA-compliant relational resources will participate, enabled implicitly.
• All non-relational resources can be explicitly disabled from participation.
• All transactions will be in the scope of a global transaction. Each commit/rollback will subsequently begin a transaction.
• No CREATE/DROP TABLE commands in XA mode.