2.5.6.5 Drive Completion of a Transaction – Root Transaction Manager
In this use case, the root transaction manager drives the completion of the transaction on all transaction participants.
Context of use: A transaction has to be completed on all its participants.
Goal: To drive completion of the transaction on all transaction participants.
Actors:
Root transaction manager: The root transaction manager is a supporting actor. The root transaction manager coordinates the lifetime of transactions by providing functionality for resource managers to enlist in these transactions and functionality to enlist in transactions that are coordinated by remote transaction managers. Here, the root transaction manager creates the transaction and starts performing the transaction.
-
Transaction managers that are subordinate to the transaction manager that is executing this use case are supporting actors for this use case. Supporting actors execute a new instance of this use case on resource managers and transaction managers that are enlisted in the transaction through them.
Stakeholders:
Architects
Implementers
Preconditions:
Transaction processing services are operational.
The transaction manager can access the participants in the transaction.
Main success scenario:
Trigger: The root transaction manager triggers its subordinate transaction managers.
The root transaction manager drives the two-phase commit notifications on each participant that is enlisted in the transaction.
Each transaction manager that is subordinate to this root transaction manager initiates a new use case for the participants.
The root transaction manager returns success after the transaction has completed.
Postcondition: The transaction has completed successfully.
Extensions: None.