HP Reliable Transaction Router - Manual (Page 93)

roles
Roles are defined for each node in an RTR configuration based on
the requirements of a specific facility. Roles are frontend, router,
or backend.
rollback
When a transaction has been committed on the primary
database but cannot be committed on its shadow, the committed
transaction must be removed or rolled back to restore the
database to its pretransaction state.
router
The RTR role that manages traffic between RTR clients and
servers.
RTRACP
The RTR application control process.
RTR configuration
The set of nodes, disk drives, and connections between them
used by RTR.
RTR environment
The RTR run-time and system management areas.
RTRData object
An instance of the C++ API RTRData class. This object contains
either a message or an event. It is used for both sending and
receiving data between client and server applications.
secondary
See shadow.
server
A server is always a server application or process, one that
reacts to a client application’s units of work and carries them
through to completion. This may involve updating persistent
storage such as a database file, toggling the switch on a device,
or performing another predefined task. In the context of RTR, a
server must run on a node defined to have the backend role.
Glossary–9