       $                               COMPAQ   Software Product  Description   C ___________________________________________________________________   D PRODUCT NAME:   Reliable Transaction Router Version 4.1 for 51.04.09                  OpenVMS[TM]   DESCRIPTION   F Reliable Transaction Router (RTR) is fault tolerant transactional mes-C saging middleware used to implement large, distributed applications D using client/server technology. This version of Reliable TransactionG Router enables enterprises to deploy distributed applications on  Open-  VMS Alpha and VAX systems.  C Reliable Transaction Router enables distributed applications to run F in heterogeneous environments, allowing client and server applicationsD to interoperate on the supported Windows, Compaq Tru64 UNIX, Sun So- laris, and OpenVMS platforms.   H Reliable Transaction Router provides APIs for development of distributedE applications using languages such as C and C++, with optional all-or- C nothing transaction semantics as well as a message broadcasting ca- C pability. C API calls are also available from a command line inter- D face. The C++ API provides an object-oriented interface for develop- ing applications. [1]   E Reliable Transaction Router provides a reliable, transparent, dynamic O message-routing system that includes both a transactional and non-transactional E message control system. RTR transaction management supports two-phase # commit of distributed transactions.    ____________________  D  The  C++ API is not available for the OpenVMS VAX operating system.  C                                                         August 2001   C                                                         AE-Q3B3K-TE        D Reliable Transaction Router implements automatic software fault tol-D erance and failure recovery in multinode environments by adapting toC many kinds of hardware (CPU), communications, application software, C and site failures. Automatic failover and recovery of service oper- D ate by exploiting redundant or alternate hardware and network links.C If alternate hardware or network links are not available, RTR auto- G matically continues service when the CPU or network link becomes avail-  able.   C Reliable Transaction Router applications are developed and deployed E using a three-tier client/router/server software model. Client appli- C cations call the RTR client software tier, which passes messages to D the router tier of the software. Transaction messages are routed re-D liably and transparently, based on message content, to the appropri-C ate processes in the server tier. Server applications typically ex- I ecute transactions against a database and return results back to clients.   W A single physical node may run one, two, or three tiers of the RTR client/router/server C software model. Each of the three software tiers may consist of one G or more nodes. The software model and its content-based routing present D a virtual rather than physical network to the application developer.C This model enables application software to be independent of physi- C cal hardware (CPU) location, network naming conventions, and commu- H nications protocol. This facilitates single-node development, and trans-E parent scalability of applications in complex network configurations.   D Reliable Transaction Router software fault tolerant features such asD router failover and shadow-server processing provide continuous com-C puting services with completion of in-progress transactions despite E single or multiple points of failure in the distributed client/server C environment. Callout servers implement user authentication control, F and concurrent servers provide dynamic message load balancing for highD performance. High performance transactional messaging is implementedG as a full-duplex conversation with remote server procedures using real- F time flow control techniques. Use of these features generally requires. no special user application programming logic.        "                                  2       F The RTR system management interface is available as a command line in-E terface and a web-based interface. The web interface provides a point C and click style of managing RTR from a browser. Both interfaces al- E low the creation, deletion, and modification of virtual networks (fa- F cilities) within a network, and permit control of distributed RTR pro-C cesses from a single system in the distributed environment. The RTR C system management interfaces are used to bind the physical hardware F (CPU and communications) to a virtual network namespace and are trans-D parent to the applications software. A monitoring utility can be in-E voked to report application performance information on a local or re- 
 mote node.  C Reliable Transaction Router is independent of forms and window man- D agement systems and databases. Multiple databases and other resourceC managers (for example, flat-file systems) can be updated within the  same distributed transaction.   D Reliable Transaction Router is intended for distributed applicationsD that require continuous computing services and transaction integrityD (for example, trading systems, banking systems, electronic commerce,D payment systems, transportation systems, and telecommunications sys-D tems). Reliable Transaction Router can also be used for applicationsC that require reliable messaging and fault tolerant application con- D trol over LANs or WANs. Reliable Transaction Router provides the en-L abling technology for applications requiring fully distributed client/server models.   E Reliable Transaction Router on OpenVMS provides an interface for con- D trolling transaction commitment directly with a DECdtm compliant re- source manager.   I Reliable Transaction Router provides an interface for allowing RTR nested E transactions to be part of a global transaction coordinated by an ex- I ternal transaction manager. For example, Microsoft MTS, Encina, or Tuxedo D applications can be written to use this functionality of the RTR APIF so that the application can coordinate RTR transactions as part of theF globally coordinated transactions. It is the responsibility of the ex-C ternal transaction manager application to ensure that it works with  RTR.  "                                  3        Backend Features  L o  Provides transparent, content-based transaction routing for client/server    applications.  D o  Provides publish/subscribe broadcast (nontransactional) messagingF    for delivery to multiple subscription domains within a virtual net-    work.  C o  Allows user-defined partitioned data models (content-based rout- 6    ing) for improved performance of user applications.  C o  Acts as a layer between client and server applications, thus de- E    coupling the end-to-end relationship normally required by user ap- D    plication control. This provides the application developer with a5    single system view of the programming environment.   E o  Ensures atomicity of transactions (all or nothing) by using a two- E    phase commit protocol for transactional message delivery among one     or more server applications.   F o  Offers at-most-once semantics for valid transactions. This includesD    specially flagged transaction replay to a surviving server appli-C    cation, or a later instantiation of that server on the same or a ,    different machine on the virtual network.  F o  DECdtm support is provided for use with resource managers that sup-    port DECdtm.   * o  Supports multiple (concurrent) servers.  H o  Provides disaster protection against site failure by mirroring trans-E    actions in shadow-server environments. Automatic resynchronization F    of shadow pairs after recovery is provided transparently to the ap-
    plication.   D o  Maintains performance scaling over a wide range of configurationsF    allowing easy horizontal expansion of both hardware systems and ap-    plication software.  "                                  4       E o  Enables automatic failover/failback of server applications on mul- E    tiple backend systems while remaining transparent to client appli- D    cations executing on remote systems. RTR can maintain applicationI    operation in many instances of single or multiple failures in a widely /    distributed software/hardware configuration.   C o  Includes system management interfaces for online control of vir- D    tual networks from any workstation or terminal with the appropri-J    ate privileges. Monitoring of statistics, software and hardware states,C    and clients and servers is provided from local and remote nodes.   F o  Uses TCP/IP as the underlying network transport. DECnet and DECnet-    Plus are also supported.   C 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.  C    -  Select the failover precedence option to choose between local %       and cross-site shadow failover.   C    -  Suspend and resume operations to synchronize database backups        with transaction flows.   F    -  Override RTR's automatic recovery decisions to allow manual spe-       cial recovery procedures.   4    -  Specify retry limits for problem transactions.  D o  Enables the operator to selectively inspect, modify the state of,E    or remove transactions from the journal or the running RTR system.   D o  Supports anonymous clients, that is, allows clients to be config-#    ured with wildcarded node names.    Frontend Features   "                                  5       E o  Provides the ability for the client to start transaction branches, C    where the global transaction may be controlled by RTR or another      external transaction manager.  H o  Provides the necessary environment to run Reliable Transaction RouterC    client applications under OpenVMS as part of a Reliable Transac-     tion Router virtual network.   E o  Provides client functionality in a production environment, as well C    as a single-node application development and testing environment     for RTR applications.  F o  Uses TCP/IP as the underlying network transport. DECnet and DECnet-    Plus are also supported.   D o  Supports transactional and broadcast (nontransactional) messages.  G o  Supports automatic failover to another router in the event of a com-     munication link failure.   E o  Supports Reliable Transaction Router system management operations.    HARDWARE REQUIREMENTS   E Any hardware that supports the OpenVMS operating system. Refer to the D configuration charts listed in the OpenVMS Operating System SoftwareC Product Description (SPD 25.01.xx) Hardware Support Tables for fur-  ther information.    SOFTWARE REQUIREMENTS   D To qualify for a software support contract, you must have one of the3 following versions of the OpenVMS operating system:   + o  OpenVMS Alpha Version 6.2, 7.2-1, or 7.3   ' o  OpenVMS VAX Version 6.2, 7.2, or 7.3   E You must also have one of the following networking products appropri-  ate for the version of OpenVMS:   - o  TCP/IP Services for OpenVMS (SPD 46.46.xx)   "                                  6       . o  DECnet for OpenVMS (Phase IV, SPD 48.48.xx)  G o  DECnet-Plus (Phase V, SPD 50.45.xx for Alpha, SPD 25.03.xx for VAX).   E Versions of the networking products supported for each version of the ; OpenVMS operating system are listed in the following table:   C ___________________________________________________________________                          DECnetC OpenVMS_____TCP/IP______IV__________DECnet_V_______________________   * Alpha       4.2         6.2         6.3[1] 6.2   ) Alpha       5.x         7.2-1       7.2-1  7.2-1   ' Alpha       5.1         7.3         7.3  7.3   ' VAX 6.2     4.2         6.2         6.3   ' VAX 7.2     5.x         7.2         7.2   ' VAX 7.3     5.1         7.3         7.3 C ___________________________________________________________________ C [1]Requires_ECO5___________________________________________________    OPTIONAL SOFTWARE   D Reliable Transaction Router applications can be written using Compaq C and C++ compilers.  E o  Remote execution software to support system management from remote 	    nodes.   F o  Windows-based browser for system management: Internet Explorer Ver-
    sion 5.01.       OpenVMS VAX  F o  Compaq C Version 6.2-003 for OpenVMS. For more information, see the0    C Software Product Description, SPD 25.38.29.  "                                  7           OpenVMS ALPHA  F o  Compaq C Version 6.2-006 for OpenVMS. For more information, see the0    C Software Product Description, SPD 25.38.29.  D o  Compaq C++ Version 6.2-035 for OpenVMS. For more information, see6    the C++ Software Product Description, SPD 70.57.03.   GROWTH CONSIDERATIONS   D The minimum hardware/software requirements for any future version ofC this product may be different from the requirements for the current  version.   DISTRIBUTION MEDIA  I The software and documentation for Reliable Transaction Router are avail- 7 able on the Compaq CD-ROM Software Library for OpenVMS.   C The software and documentation for Alpha systems are also available D on a separate CD-ROM supplied as part of the media and documentationG kit QA-2AQAA-H8. A hardcopy documentation set can be ordered separately  as QA-2AQAA-GZ.   D The software and documentation for VAX systems are also available onF a separate CD-ROM as part of the media and documentation kit QA-XNKAA-G H8. A hardcopy documentation set can be ordered separately as QA-XNKAA-  GZ.    ORDERING INFORMATION  
 OpenVMS Alpha   / Back End Software Product Services: QT-2AQA*-** 0 Front End Software Product Services: QT-2ARA*-**          "                                  8        OpenVMS VAX   / Back End Software Product Services: QT-XNKA*-** 0 Front End Software Product Services: QT-XNLA*-**E For more information on software licensing, refer to the Software Li-  censing section.  F *  Denotes variant fields. For additional information on available li-D    censes, services, and media, refer to the appropriate price book.   SOFTWARE LICENSING  E Reliable Transaction Router is no longer licensed as a separate prod- C uct, but is licensed as part of the OpenVMS product. An OpenVMS li- D cense permits use of RTR V4.1 and prior versions providing the givenF version of RTR runs with the given version of OpenVMS, as shown in the following table.  C ___________________________________________________________________  RTR Ver-C sion__________OpenVMS_Version______________________________________   / 4.1           7.3, 7.2-1, 6.2 for Alpha systems   + 4.1           7.3, 7.2, 6.2 for VAX systems   6 4.0           7.3, 7.2-1, 7.1-2, 6.2 for Alpha systems  0 4.0           7.3, 7.2, 7.1, 6.2 for VAX systems   3.2           7.2, 7.1, 6.2     3.1D          7.1, 7.0, 6.2, 6.1  C 2.2D__________6.1__________________________________________________    SOFTWARE PRODUCT SERVICES   D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.  "                                  9        SOFTWARE WARRANTY   F This software is provided by Compaq with a 90 day conformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.   
 TRADEMARKS  E Compaq and the Compaq logo are registered in the United States Patent  and Trademark Office. C Alpha, DEC, DECdtm, DECnet, OpenVMS, Tru64 UNIX, and VAX are trade- 4 marks of Compaq Information Technologies Group, L.P.C Microsoft, Windows, and Windows NT are trademarks of Microsoft Cor- 	 poration. * Intel is a trademark of Intel Corporation.1 UNIX is a registered trademark of The Open Group.   D All other product names mentioned herein may be trademarks or regis-/ tered trademarks of their respective companies.   #  2001 Compaq Computer Corporation.                                       "                                 10                                                                                                                                                                                                                                                                                    