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