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