HP Reliable Transaction Router (RTR) is a transactional middleware for computer software, marketed by Hewlett Packard. RTR is used to integrate with applications that require reliable transaction services.
The RTR software package manages the messages sent between client-server to provide node and network fail-over for increased reliability, transactional integrity, and interoperability between dissimilar systems.
The RTR software has three logical entities: front-end (FE), back-end (BE), and transaction-router(TR). The router is a software component that provides fail-over intelligence and manages connections to the back-end.The client applications running on the Front End, combined with the Router and Server applications running on the back end, interact to provide transaction integrity and reliability. The three logical entities can exist on the same node but are usually deployed on different nodes to achieve modularity, scalability, and high availability.
The client application interacts with the front-end which forwards the messages to the router, the router in turn routes the message to the intended back-end where the appropriate Server application is available for processing the message. The RTR routing capability partitions data across multiple servers and nodes for increased performance. The partition determines how messages are routed between the client and the servers within an application. The message exchange happens between the client and the server. Transactions start at the client and involve messages that can go to several servers. Such a method of messaging is used when there are multiple recipients for a message, or unsolicited messages need to be sent. RTR can help survive the failures generally seen in distributed application environments, including complete site, node, network link, and software process failures. RTR also provides continuous availability by using redundant resources in the distributed environment.
RTR provides a Web Interface and a Command-Line Interface(CLI) for managing the RTR environment. When RTR and its components are running along with the applications, then Client Application, Server Application, and RTR services will be active.
RTR is integrated with client applications and can be customized. User and Management Applications can be written using RTR APIs. The C, C++, Java, and .Net variants of APIs are available for creating applications to use RTR.
RTR was first conceived in Zurich, Switzerland, by Dr. Paul Shrager in early 1988 and developed by a small team of four engineers working for DEC (Digital Equipment Corporation). The initial release was written in a mix of Macro, Bliss, Pascal, and SDL on top of DECnet and VMS. Later, it was reimplemented in C on top of a TCP/IP stack and an OS-agnostic infrastructure that allowed it to be deployed on multiple operating systems, including various flavors of Unix/Linux, VMS, and Windows. A Java and C++ veneer was added in the mid-90s to support an RPC-style veneer on top of the "services" oriented interface.
RTR was one of the first OLTP middleware services that provided the following features (in addition to the usual ones), viz.
Additionally, RTR guarantees the data equivalence of the repositories behind the primary and shadow servers, by enforcing a deduced "dependency relationship" among the set of concurrent transactions being shadowed. This allows RTR to process multiple transactions on the shadow without compromising dependency violations.
The most high-profile users of RTR are banks, stock exchanges and Railway Passenger Reservation Systems.
RTR was available on HP-UX, Linux, Windows and OpenVMS in 2010.