HP Reliable Transaction Router Version 5.2 for Linux on Integrity servers (March 2010)

Software
Product
Description
PRODUCT NAME: HP Reliable Transaction Router Version 5.2 for 82.42.03
Linux on Integrity servers
DESCRIPTION
HP Reliable Transaction Router (RTR) is fault tolerant
transactional messaging middleware used to implement
large, distributed applications using client/server tech-
nology. This version of Reliable Transaction Router en-
ables enterprises to deploy distributed applications on
Linux Integrity servers.
Reliable Transaction Router enables distributed appli-
cations to run in heterogeneous environments, allow-
ing client and server applications to interoperate on the
supported Linux, Windows, HP-UX, and OpenVMS plat-
forms.
Reliable Transaction Router provides APIs for develop-
ment of distributed applications using languages such
as C and C++, with all-or-nothing transaction semantics
as well as an optional message broadcasting capabil-
ity. C API calls are also available from a command line
interface. The C++ API provides an object-oriented in-
terface for developing user and system management
applications. Applications can also use the X/Open XA
interface.
Reliable Transaction Router provides a reliable, trans-
parent, dynamic message-routing system that includes
both a transactional and non-transactional message
control system. RTR transaction management supports
two-phase commit of distributed transactions.
Reliable Transaction Router implements automatic soft-
ware fault tolerance and failure recovery in multinode
environments by adapting to many kinds of hardware
(CPU), communications, application software, and site
failures. Automatic failover and recovery of service op-
erate by exploiting redundant or alternate hardware and
network links. If alternate hardware or network links
are not available, RTR automatically continues service
when the CPU or network link becomes available.
Reliable Transaction Router applications are developed
and deployed using a three-tier client/router/server soft-
ware model. Client applications call the RTR client soft-
ware tier, which passes messages to the router tier of
the software. Transaction messages are routed reliably
and transparently, based on message content, to the
appropriate processes in the server tier. Server applica-
tions typically execute transactions against a database
and return results back to clients.
A single physical node may run one, two, or three tiers
of the RTR client/router/server software model. Each
of the three software tiers may consist of one or more
nodes. The software model and its content-based rout-
ing present a virtual rather than physical network to the
application developer. This model enables application
software to be independent of physical hardware (CPU)
location, network naming conventions, and communica-
tions protocol. This facilitates single-node development,
and transparent scalability of applications in complex
network congurations.
Reliable Transaction Router software fault tolerant fea-
tures such as router failover and shadow-server pro-
cessing provide continuous computing services with
completion of in-progress transactions despite single or
multiple points of failure in the distributed client/server
environment. Callout servers implement user authenti-
cation control, and concurrent servers provide dynamic
message load balancing for high performance. High
performance transactional messaging is implemented
as a full-duplex conversation with remote server pro-
cedures using real-time ow control techniques. Use of
these features generally requires no special user appli-
cation programming logic.
September 2009

Summary of content (4 pages)