RTR Terminology
Figure 1–5 Components in the RTR Environment
User Accounts Facility
FE
Client
application
TR
BE
Server
application
General Ledger Facility
| |
| disconnected before all parts of the transaction are done, then |
| the transaction remains incomplete. |
Transaction | A transaction is a piece of work or group of operations that |
| must be executed together to perform a consistent transformation |
| of data. This group of operations can be distributed across many |
| nodes serving multiple databases. Applications use services that |
| RTR provides. |
Transactional messaging
RTR provides transactional messaging in which transactions are enclosed in messages controlled by RTR.
Transactional messaging ensures that each transaction is complete, and not partially recorded. For example, a transaction or business exchange in a bank account might be to move money from a checking account to a savings account. The complete transaction is to remove the money from the checking account and add it to the savings account.
A transaction that transfers funds from one account to another consists of two individual updates: one to debit the first account, and one to credit the second account. The transaction is not complete until both actions are done. If a system performing this work goes down after the money has been debited from the checking account but before it has been credited to the savings account, the transaction is incomplete. With transactional
Introduction
