Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router manual 8 Browser Applet Conﬁguration, Introduction

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 20

Figure 1–8 Browser Applet Conﬁguration

RTR Terminology

All components can reside on a single node but are typically deployed on different nodes to achieve modularity, scalability, and redundancy for availability. With different systems, if one physical node goes down or off line, another router and backend node takes over. In a slightly different conﬁguration, you could have an application that uses an external applet running on a browser that connects to a client running on the RTR frontend. Such a conﬁguration is shown in Figure 1–8.

Figure 1–8 Browser Applet Conﬁguration

PC Browser

Applet

RTR Frontend

Web Server

Process

RTR Client

Application

LKG-11206-98WI

The RTR client application could be an ASP (Active Server Page) script or a process interfacing to the webserver through a standard interface such as CGI (Common Gateway Interface).

RTR provides automatic software failure tolerance and failure recovery in multinode environments by sustaining transaction integrity in spite of hardware, communications, application, or site failures. Automatic failover and recovery of service can exploit redundant or underutilized hardware and network links.

As you modularize your application and distribute its components on frontends and backends, you can add new nodes, identify usage bottlenecks, and provide redundancy to increase availability. Adding backend nodes can help divide the transactional load and distribute it more evenly. For example, you could have a single node conﬁguration as shown in Figure 1–9, RTR with Browser, Single Node, and Database. A

1–10Introduction

Image 20

Compaq Reliable Transaction Router 8 Browser Applet Conﬁguration, Web Server Process RTR Client Application, Introduction

Contents

Revision/Update Information This is a new manual Reliable Transaction Router Getting StartedJanuary Compaq Computer Corporation Houston, TexasUNIX and The Open Group are trademarks of The Open Group This document was prepared using VAX DOCUMENT, Version2001 Compaq Computer Corporation Contents IntroductionArchitectural Concepts 3 Reliability Features 4 RTR Interfaces5 The RTR Environment Glossary Index ExamplesFigures TablesPage Document Structure PrefacePurpose of this Document RTR Commands Router InstallationRelated Documentation For all usersReading Path Readers CommentsConventions New termFigure 1 RTR Reading Path System ManagerApplication Programmer If V2 toIntroduction Reliable Transaction RouterRTR Continuous Computing Concepts RTR Terminology Figure 1-1 Client Symbol Figure 1-2 Server Symbol Channel RTR conﬁguration RolesFE TR Figure 1-3 Roles SymbolsFigure 1-4 Facility Symbol Figure 1-5 Components in the RTR Environment Nontransactional messaging Transaction ID Transaction Controller 1-8 IntroductionFigure 1-6 Two-Tier Client/Server Environment Figure 1-7 Three-Tier Client/Server Environment1-10 Introduction Figure 1-8 Browser Applet ConﬁgurationWeb Server Process RTR Client Application Figure 1-9 RTR with Browser, Single Node, and Database Figure 1-10 RTR Deployed on Two NodesFigure 1-11 RTR Deployed on Three Nodes 1-12 IntroductionFigure 1-12 Standby Server Conﬁguration Transactional shadowing RTR JournalFigure 1-13 Transactional Shadowing Conﬁguration RTR Server Types Concurrent servers Callout servers Figure 1-15 Standby Servers Transactional shadow serverFigure 1-16 Shadow Servers Figure 1-17 Concurrent Servers User Accounts Facility Figure 1-18 A Callout ServerFigure 1-19 Bank Partitioning Example TR A partition can also have multiple standby servers RTR Networking Capabilities RouterPage Architectural Concepts The Three-Layer ModelFigure 2-1 The Three Layer Model ZKO-GS011-99AIFlexibility and Growth RTR Facilities Bridge the GapBroadcasts Transaction Integrity Flexibility and GrowthThe Partitioned Data Model Object-Oriented ProgrammingFigure 2-2 Partitioned Data Model ZKO-GS012-99AIObjects Table 2-1 Functional and Object-Oriented Programming ComparedMessages Class Relationships Example 2-1 Objects-Deﬁned SamplePolymorphism Object Implementation Beneﬁts XA Support Programmers Reference Manual and the RTR Application Design GuideReliability Features ServersFailover and Recovery Recovery ScenariosRecovery Router FailoverBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station $ RTR RTR SHOW JOURNALRTR CREATE FACILITY DESIGN/ALLROLES=NODEA RTR SHOW FACILITYRTR RTRRECEIVEMESSAGE/CHAN=S RTR show transactionRTR RTRRECEIVEMESSAGE/TIME=0 $ RTR RTR START RTRRTR RTRRECEIVEMESSAGE/CHANNEL=C/tim RTR RTRSTARTTX/CHAN=Centers commands at the server RTR show transactionApplication Programming Interfaces BrowserInterface Object-OrientedApplication Programming Interfaces Figure 4-1 RTR Browser InterfaceRTR C Example of object creation in an RTR server programinterface, see the RTR C Application Programmers Reference Manual and the RTR Application Design GuideExample of an open channel call in an RTR client program The RTR Environment The RTR System Management EnvironmentHandles all transactions and recovery Page Monitoring RTR ManagementTransaction RTR Monitor pictures or the RTR Monitor let you view theManagement The RTR Runtime EnvironmentPartition Figure 5-2 RTR Runtime Environment RTR Installation Guide Whats Next?RTR Release Notes RTR Migration Guide ifPage Glossary ACIDapplet applicationbranch broadcastcallout server channelcommon classes concurrent serverdata marshalling data objectendian frontend message primary processproperties property classesrollback routerRTR conﬁguration RTR environmentshadow standbytransaction transaction controllertransactional shadowing two-phase committransactional message Index Index-1Index-2