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