Planning for federated two-phase commit

Federated two-phase commit does not provide benefits in all business environments. Also, there are several factors to consider before you decide to deploy federated two-phase commit.

To use two-phase commit for federated transactions, you must consider the following issues:

• Whether your operating system and data source environment can support two-phase commit for federated transactions.
• Whether your business environment requires two-phase commit for federated transactions.

  To decide whether or not two-phase commit is right for your business environment, you need to understand how two-phase commit for federated transactions works and the problems that it solves.

• How to configure the federated server and compatible data sources to use two-phase commit for federated transactions.

  There are basic federated server and data source requirements to use two-phase commit for federated transactions as well as performance considerations you must consider when deploying two-phase commit.

• To manually resolve indoubt transactions, you need to understand the inner workings of two-phase commit for federated transactions.

  Two-phase commit for federated transactions can resolve problems without intervention. But when there are extended network outages, hardware failures, or an urgent need to free up system resources, you can manually resolve problems through heuristic processing.