HP Reliable Transaction Router Version 5.1 for Windows

HP Reliable Transaction Router Version 5.1 53.88.16
Windows
The web-based interface provides a point and click style
of managing RTR from a browser. The browser inter-
face provides monitoring and management of the RTR
configuration with the RTR Manager, and RTR Explorer,
components of the browser-based RTR Administrator.
Both interfaces allow the creation, deletion, and modi-
fication of application networks (facilities) within a net-
work, and permit control of distributed RTR processes
from a single system in the distributed environment. The
RTR system management interfaces are used to bind
the physical hardware (CPU and communications) to a
virtual network namespace and are transparent to the
applications software. A monitoring utility can be in-
voked to report application performance information on
a local or remote node.
Reliable Transaction Router is independent of forms and
window management systems and databases. Multiple
databases and other resource managers (for example,
flat-file systems) can be updated within the same dis-
tributed transaction.
Reliable Transaction Router is intended for distributed
applications that require continuous computing services
and transaction integrity (for example, trading systems,
banking systems, electronic commerce, payment sys-
tems, transportation systems, and telecommunications
systems).
Reliable Transaction Router can also be used for ap-
plications that require reliable messaging and fault tol-
erant application control over LANs or WANs. Reliable
Transaction Router provides the enabling technology for
applications requiring fully distributed client/server mod-
els.
On Windows, RTR provides an interface for controlling
transaction commitment directly with a Microsoft DTC
compliant resource manager such as Microsoft SQL
Server.
On Windows, Reliable Transaction Router provides an
interface for controlling transaction commitment directly
with an XA-compliant resource manager, such as ORA-
CLE9.
License Types
Reliable Transaction Router for Windows has two li-
cense types.
The Backend license provides full client/router/server
functionality. It is required for nodes configured as
routers or servers, and can also be used for nodes con-
figured as clients.
The Frontend license provides client application func-
tionality only, in a production environment, plus a single-
node development and testing environment for RTR ap-
plications.
Backend Features
• Runs on the Windows 2000, Windows 2003 Server,
or Windows XP operating systems.
• May be started as a Windows service.
• Provides transparent, content-based transaction
routing for client/server applications.
• Provides publish/subscribe broadcast (nontransac-
tional) messaging for delivery to multiple subscription
domains within a virtual network.
• Allows user-defined partitioned data models (content-
based routing) for improved performance of user ap-
plications.
• Acts as a layer between client and server applica-
tions, thus decoupling the end-to-end relationship
normally required by user application control. This
provides the application developer with a single sys-
tem view of the programming environment.
• Ensures atomicity of transactions (all or nothing) by
using a two-phase commit protocol for transactional
message delivery among one or more server appli-
cations.
• Offers at-most-once semantics for valid transactions.
This includes specially flagged transaction replay to
a surviving server application, or a later instantiation
of that server on the same or a different machine on
the virtual network.
• Supports multiple (concurrent) servers as well as
multithreaded clients and servers.
• Supports user authentication control (callout servers)
with consistent reply in shadow environments.
• Provides disaster protection against site failure by
mirroring transactions in shadow-server environ-
ments. Automatic resynchronization of shadow pairs
after recovery is provided transparently to the appli-
cation.
• Maintains performance scaling over a wide range of
configurations allowing easy horizontal expansion of
both hardware systems and application software.
• Enables automatic failover/failback of server appli-
cations on multiple backend systems while remain-
ing transparent to client applications executing on re-
mote systems. RTR can maintain application opera-
tion in many instances of single or multiple failures in
a widely distributed software/hardware configuration.
• Includes system management interfaces for online
control of virtual networks from any workstation or
terminal with the appropriate privileges. Monitoring of
statistics, software and hardware states, and clients
and servers is provided from local and remote nodes.
• Uses HP TCP/IP IPv4 as the underlying network
transport. HP DECnet is also supported.
2