Rtr runtime environment – HP Reliable Transaction Router User Manual
Page 82

The RTR System Management Environment
• Overriding the automatic recovery procedures of RTR with
manual recovery procedures, for added flexibility
• Specifying retry limits for problem transactions
The operator can selectively inspect transactions, modify states,
or remove transactions from the journal or the running RTR
system. This allows for greater operational control and enhanced
management of a system where RTR is running.
For more details on managing partitions and their use in
applications, refer to the chapter on ‘‘Partition Management’’ in
the HP Reliable Transaction Router System Manager’s Manual.
RTR Runtime Environment
When all RTR and application components are running, the RTR
runtime environment contains:
• Client application
• Server application
• RTR shareable image, LIBRTR
• RTR control process, RTRACP
• RTR daemon, RTRD
• RTR command line interface, RTR CLI
• RTR command server, RTR COMSERV
Figure 5–2 shows these components and their placement on
frontend, router, and backend nodes. The frontend, router, and
backend can be on the same or different nodes. If these are all
on the same node, there is only one RTRACP process.
5–6 The RTR Environment