Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
Software
Product
Description
PRODUCT NAME:
HP Reliable Transaction Router Version 5.1
82.33.05
Linux Frontend
DESCRIPTION
• Uses HP TCP/IP IPv4 as the underlying network
transport.
HP Reliable Transaction Router (RTR) is fault tolerant
transactional messaging middleware used to implement
• Supports transactional and broadcast (nontransac-
large, distributed applications using client/server tech-
tional) messages.
nology. This version of Reliable Transaction Router en-
• Supports router load balancing in a facility.
ables enterprises to deploy distributed applications on
• Supports automatic router failover in the event of a
Linux frontend/client systems. On the Linux operating
communication link failure.
system, only the client tier is supported.
• Supports Reliable Transaction Router system man-
On the Linux operating system, RTR can be used as a
agement operations.
frontend (that is, for client support) in an RTR application
network. It is used in conjunction with RTR backend
and router nodes running on other supported operating
HARDWARE REQUIREMENTS
systems to create a distributed, fault-tolerant application
network.
• For frontend functionality, any Intel 32 system that
runs Redhat Enterprise Linux WS Version 3.0.
License Types
• Disk space requirement: 22 MB1
Reliable Transaction Router for Linux Frontend has one
• Memory requirements: 5.8 MB2
frontend license type. RTR is not supported or licensed
on Linux in a backend or router role.
SOFTWARE REQUIREMENTS
The Frontend license provides client application func-
tionality only.
• Redhat Enterprise Linux WS Version 3.0.
Frontend Features
• TCP/IP as provided by the operating system.
• At least one HP Reliable Transaction Router Back-
• Provides the ability for the client to start transaction
end license for a supported operating system for ap-
branches, where the global transaction may be con-
plication deployment.
trolled by RTR.
• Provides the necessary environment to run Reliable
Transaction Router client applications under Linux as
part of a Reliable Transaction Router application net-
1 This count refers to the minimum disk space required on the system disk. The size
work (facility).
is approximate; actual size may vary depending on the user’s system environment,
configuration, and software.
2
• Provides client functionality in a production environ-
Basic memory requirements for an unconfigured RTR Application Control Pro-
cess (RTRACP). Additional memory may be required depending on the RTRACP
ment.
operating system environment.
March 2007
...