Two-phase commit for federated transactions - examples

A federated system that uses two-phase commit can be configured in several different ways. Configuration choices depend on the required solution.

Configurations can use Type 1 or Type 2 connections.

Type 1 connections are connections in which an application process is connected to an application server according to the rules for remote unit of work.

Type 2 connections are connections in which an application process is connected to an application server and establishes the rules for application-directed distributed unit of work. The application server is then the current server for the process.

The following figure shows a Type 1 connection with a federated server functioning as the transaction manager.
Figure 1. Type 1 connection with a federated server as the transaction manager

The following figure shows a Type 2 connection with a federated server functioning as the resource manager. In this configuration, all federated data sources must be supported for federated two-phase commit and enabled for federated two-phase commit.

Figure 2. Type 2 connection with federated server as the resource manager
The following figure shows a Type 2 connection with a federated server functioning as the transaction manager.
Figure 3. Type 2 connection with a federated server as the transaction manager
The following figure shows an XA connection with a federated server functioning as the resource manager.
Figure 4. XA connection with federated server as the resource manager