2.5.3 Transaction Management – Management Tool
Context of use: A transaction operation is monitored or managed by the management tool.

Figure 8: Manage transactions use case
Goal: To monitor or manage a transaction.
Actors:
Management tool: The management tool is the primary actor that triggers this use case. The management tool is an application that monitors the health of a transaction manager and configures settings that are related to transaction coordination.
Transaction manager: The transaction manager is the supporting actor. It is a service that coordinates the lifetime of transactions by providing functionality for resource managers to enlist in these transactions. The root transaction manager also provides functionality to enlist in transactions that are coordinated by remote transaction managers.
Stakeholders:
Application: The application is a program that performs transactions in a distributed computed network that creates a transaction, and therefore, only that application has the right to commit the transaction.
Preconditions:
Transaction processing services are operational.
The management tool can access the transaction manager in the system.
Main success scenario:
Trigger: The management tool requests that the transaction manager provides a list of existing transactions.
The transaction manager returns a list of existing transactions and their known states.
The management tool performs a Subscribe for transaction information action against the transaction manager to monitor the progress of the two-phase commit protocol, as described in [MS-DTCO] section 1.3.1 and to resolve the transaction if it reaches an error state.
The management tool requests that the transaction manager updates the state of a transaction. For example, it can force the transaction to abort.
The transaction manager successfully updates the state of the transaction.
Postcondition: The transaction state is correctly updated.