Software Product Description ___________________________________________________________________ PRODUCT NAME: HP Reliable Transaction Router Version 5.2 for51.04.19 OpenVMS DESCRIPTION HP Reliable Transaction Router (RTR) is fault tolerant transactional messaging middleware used to implement large, distributed applications using client/server technology. This version of Reliable Transaction Router enables enterprises to deploy distributed applications on Open- VMS Alpha Systems and OpenVMS for Integrity servers. Reliable Transaction Router enables distributed applications to run in heterogeneous environments, allowing client and server applications to interoperate on the supported Linux, Windows, HP-UX, and OpenVMS platforms. Reliable Transaction Router provides application programming inter- faces (APIs) for development of distributed applications using lan- guages such as C and C++, with all-or-nothing transaction semantics as well as an optional message broadcasting capability. C API calls are also available from a command line interface. The C++ API provides an object-oriented interface for developing user and system manage- ment applications. Applications can also use the X/Open XA interface. Reliable Transaction Router provides a reliable, transparent, dynamic message-routing system that includes both a transactional and non-transactional message control system. RTR transaction management supports two-phase commit of distributed transactions. Reliable Transaction Router implements automatic software fault tol- erance and failure recovery in multinode environments by adapting to many kinds of hardware (CPU), communications, application software, and site failures. Automatic failover and recovery of service oper- ate by exploiting redundant or alternate hardware and network links. September 2009 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS If alternate hardware or network links are not available, RTR auto- matically continues service when the CPU or network link becomes avail- able. Reliable Transaction Router applications are developed and deployed using a three-tier client/router/server software model. Client appli- cations call the RTR client software tier, which passes messages to the router tier of the software. Transaction messages are routed re- liably and transparently, based on message content, to the appropri- ate processes in the server tier. Server applications typically ex- ecute transactions against a database and return results back to clients. A single physical node may run one, two, or three tiers of the RTR client/router/server software model. Each of the three software tiers may consist of one or more nodes. The software model and its content-based routing present a virtual rather than physical network to the application developer. This model enables application software to be independent of physi- cal hardware (CPU) location, network naming conventions, and commu- nications protocol. This facilitates single-node development, and trans- parent scalability of applications in complex network configurations. Reliable Transaction Router software fault tolerant features such as router failover and shadow-server processing provide continuous com- puting services with completion of in-progress transactions despite single or multiple points of failure in the distributed client/server environment. Callout servers implement user authentication control, and concurrent servers provide dynamic message load balancing for high performance. High performance transactional messaging is implemented as a full-duplex conversation with remote server procedures using real- time flow control techniques. Use of these features generally requires no special user application programming logic. The RTR system management interface is available as a command line in- terface and a web-based interface. The web-based interface provides a point and click style of managing RTR from a browser. The browser interface provides monitoring and management of the RTR configuration with the RTR Manager, and RTR Explorer, components of the browser-based RTR Administrator. 2 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS Both interfaces allow the creation, deletion, and modification of ap- plication networks (facilities) within a network, 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 names- pace and are transparent to the applications software. A monitoring utility can be invoked to report application performance information on a local or remote node. Reliable Transaction Router is independent of forms and window man- agement systems and databases. Multiple databases and other resource managers (for example, flat-file systems) can be updated within the same distributed 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 systems, transportation systems, and telecommunications sys- tems). Reliable Transaction Router can also be used for applications that re- quire reliable messaging and fault tolerant application control over LANs or WANs. Reliable Transaction Router provides the enabling tech- nology for applications requiring fully distributed client/server mod- els. On OpenVMS, Reliable Transaction Router also provides an interface for controlling transaction commitment directly with a DECdtm compliant resource manager. Backend Features o Provides transparent, content-based transaction routing for client/server applications. o Provides publish/subscribe broadcast (nontransactional) messaging for delivery to multiple subscription domains within a virtual net- work. o Allows user-defined partitioned data models (content-based rout- ing) for improved performance of user applications. 3 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS o Acts as a layer between client and server applications, thus de- coupling the end-to-end relationship normally required by user ap- plication control. This provides the application developer with a single system view of the programming environment. o Ensures atomicity of transactions (all or nothing) by using a two- phase commit protocol for transactional message delivery among one or more server applications. o Offers at-most-once semantics for valid transactions. This includes specially flagged transaction replay to a surviving server appli- cation, or a later instantiation of that server on the same or a different machine on the virtual network. o DECdtm support is provided for use with resource managers that sup- port DECdtm. o Supports multiple (concurrent) servers. o Supports user authentication control (callout servers) with con- sistent reply in shadow environments. o Provides disaster protection against site failure by mirroring trans- actions in shadow-server environments. Automatic resynchronization of shadow pairs after recovery is provided transparently to the ap- plication. o Maintains performance scaling over a wide range of configurations allowing easy horizontal expansion of both hardware systems and ap- plication software. o Enables automatic failover/failback of server applications on mul- tiple backend systems while remaining transparent to client appli- cations executing on remote systems. RTR can maintain application operation in many instances of single or multiple failures in a widely distributed software/hardware configuration. o Includes system management interfaces for online control of vir- tual networks from any workstation or terminal with the appropri- ate privileges. Monitoring of statistics, software and hardware states, and clients and servers is provided from local and remote nodes. o Uses HP TCP/IP IPv4 as the underlying network transport. 4 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS o Enables the operator to manage partitions, providing the ability to: - Create or delete a partition with a user-specified name. - Define a key range definition. - Select a preferred primary node. - Select the failover precedence option to choose between local and cross-site shadow failover. - Suspend and resume operations to synchronize database backups with transaction flows. - Override RTR's automatic recovery decisions to allow manual spe- cial recovery procedures. - Specify retry limits for problem transactions. o Enables the operator to selectively inspect, modify the state of, or remove transactions from the journal or the running RTR system. o Supports anonymous clients, that is, allows clients to be config- ured with wildcarded node names. o Supports compression and decompression of broadcast event and trans- action reply data to improve network throughput. o Supports failover between multiple IP addresses for any host ma- chine with multiple network adapters. Frontend Features o Provides the ability for the client to start transaction branches, where the global transaction may be controlled by RTR. o Provides the necessary environment to run Reliable Transaction Router client applications under OpenVMS as part of a Reliable Transac- tion Router application network (facility). o Provides client functionality in a production environment. o Uses HP TCP/IP IPv4 as the underlying network transport. o Supports transactional and broadcast (nontransactional) messages. 5 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS o Supports router load balancing in a facility. o Supports automatic router failover in the event of a communication link failure. o Supports Reliable Transaction Router system management operations. HARDWARE REQUIREMENTS Any hardware that supports the OpenVMS operating system. Refer to the OpenVMS Operating System Software Product Description (SPD 82.35.xx) for further information. o Disk space requirement: 53000 blocks to install, 36000 blocks af- ter installation[1] o Memory requirements: 5.8 MB[2] SOFTWARE REQUIREMENTS To qualify for a software support contract, you must have one of the following versions of the OpenVMS operating system: o OpenVMS Alpha Version 7.3-2 or 8.2 or 8.3 o OpenVMS Integrity servers Version 8.2-1 or 8.3 o HP TCP/IP Services for OpenVMS (SPD 46.46.xx) ____________________ [1] This count refers to the minimum disk space required on the system disk. The size is approximate; actual size may vary depending on the user's system environment, configuration, and software. [2] Basic memory requirements for an unconfigured RTR Application Con- trol Process (RTRACP). Additional memory may be required depending on the RTRACP operating system environment. 6 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS The following table lists versions of the networking products supported for each version of OpenVMS: ___________________________________________________________________ OpenVMS_____________TCP/IP_________________________________________ Alpha 7.3-2 5.4 Alpha 8.2 5.5 Alpha 8.3 5.6 Integrity 5.5 servers 8.2-1 Integrity 5.6 servers_8.3________________________________________________________ CLUSTER ENVIRONMENT This layered product is fully supported when installed on any valid and licensed VMScluster configuration without restrictions. The HARD- WARE REQUIREMENTS section of this product's Software Product Descrip- tion details any special hardware required by this product. VMScluster configurations are fully described in the VMScluster Soft- ware Product Description (SPD 29.78.xx) and include CI, Ethernet, and Mixed Interconnect configurations. OPTIONAL SOFTWARE o Remote execution software to support system management from remote nodes. o Microsoft-supported Windows-based browser for system management run- ning on a Windows PC: Internet Explorer Version 6.0 and higher. Reliable Transaction Router applications can be written using the RTR C or C++ APIs and compiled using HP C and C++ compilers. - For more information, see the C Software Product Description, SPD 25.38.xx. 7 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS - For more information, see the C++ Software Product Description, SPD 70.57.xx. GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. DISTRIBUTION MEDIA Reliable Transaction Router is distributed on CD-ROM and on DVD. Please see "Ordering Information" for details. SOFTWARE LICENSING HP Reliable Transaction Router Back End and Front End for OpenVMS Al- pha are licensed as part of the OpenVMS Alpha Operating System. HP Reliable Transaction Router Back End for OpenVMS Integrity is li- censed as part of the OpenVMS Integrity Mission Critical Operating En- vironment. When the full MCOE is not required, the RTR Back End for OpenVMS In- tegrity may be licensed with a Per Core License (PCL). The HP Reli- able Transaction Router Front End for OpenVMS Integrity is also li- censed with a Per Core License (PCL). One PCL is required for each ac- tive processor core running OpenVMS. License Management Facility Support Licenses for HP Reliable Transaction Router and the OpenVMS Operat- ing System support LMF. HP RTR is Per Core Licensed (PCL) with one license required for each physical core which is active in the system or hard partition. If ad- ditional processors are later added to the system or hard partition, each core requires an additional PCL. 8 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS ORDERING INFORMATION Licenses License types vary by platform. ___________________________________________________________________ _________________HP_OpenVMS_Integrity_Licenses[1]__________________ HP RTR Front End VMS BA384AC[2] Integrity servers PCL LTU: HP RTR Back End VMS BA408AC[2] Integrity servers PCL LTU [3]: ___________________________________________________________________ [1]Update licenses not available; updates available through SW Updates Service. [2]Order one PCL license for each active processor core running OpenVMS. [3]HP Mission Critical Operating Environment for OpenVMS Integrity server_includes_RTR_Back_End.______________________________________ ___________________________________________________________________ _____________________HP_OpenVMS_Alpha_Licenses_____________________ HP RTR Front End and Back End are licensed with OpenVMS Alpha OS[1] ___________________________________________________________________ [1]Asterisk denotes system tier. E=workgroup tier, G=departmental tier,_Q=enterprise_tier.___________________________________________ Media and Documentation Product binary kits and online documentation are delivered on consol- idated media libraries. Delivery model varies by platform. 9 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS ___________________________________________________________________ ______HP_OpenVMS_Integrity_Media_and_Online_Documentation[1]_______ Foundation Operating BA322AA#AJR Environment Enterprise Operating BA323AA#AJR Environment Mission Critical Operat- BA324AA#AJR ing Environment ___________________________________________________________________ [1]Product ships on Layered Products Library media included in all Operating Environment media kits, available with initial OpenVMS OE_order.__________________________________________________________ ___________________________________________________________________ __________HP_OpenVMS_Alpha_Media_and_Online_Documentation__________ Software Layered Products QA-03XAA-H8 Library Package[1] Software Layered Products QA-5G98A-H8 and Operating System Library Package[1] ___________________________________________________________________ [1]Quarterly_Software_Updates_Service_is_available.________________ 10 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS ___________________________________________________________________ _________________HP_OpenVMS_Integrity_SW_Update[1]_________________ HP RTR Front End VMS BA384AA Integrity servers Media HP RTR Back End VMS BA416AA Integrity servers Media HP OpenVMS Integrity BA324AA servers MCOE Media[2] ___________________________________________________________________ [1]For the OpenVMS Integrity platform, media updates are ordered by adding SW Updates Service to individual products. The above media product numbers must be pulled into an order if SW Updates Service is planned. [2]Where RTR Back End is ordered as part of the MCOE, SW Updates Service_is_linked_to_MCOE_Media.___________________________________ NOTE: If you are adding a layered product to an existing OpenVMS In- tegrity system and do not have the latest software revision on site, please contact your local Sales Representative to request a Special Media kit. SOFTWARE PRODUCT SERVICES A variety of service options are available from HP. For more infor- mation, contact your HP account representative or distributor. Infor- mation is also available on www.hp.com/hps/software. SOFTWARE WARRANTY This software is provided by HP with a 90 day conformance warranty in accordance with the HP warranty terms applicable to the license pur- chase. © 2009 Hewlett-Packard Development Company, L.P. 11 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS Confidential computer software. Valid license from HP required for pos- session, use or copying. Consistent with FAR 12.211 and 12.212, Com- mercial Computer Software, Computer Software Documentation, and Tech- nical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional war- ranty. HP shall not be liable for technical or editorial errors or omis- sions contained herein. 12 HP Reliable Transaction Router Version 5.2 for 51.04.19 OpenVMS 13