Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router rollback, router, RTR conﬁguration, RTR environment, secondary

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 74

rollback

When a transaction has been committed on the primary database but cannot be committed on its shadow, the committed transaction must be removed or rolled back to restore the database to its pre-transaction state.

router

The RTR role that manages trafﬁc between RTR clients and servers.

RTR conﬁguration

The set of nodes, disk drives, and connections between them used by RTR.

RTR environment

The RTR run-time and system management areas.

RTRData object

An instance of the C++ API RTRData class. This object contains either a message or an event. It is used for both sending and receiving data between client and server applications.

secondary

See shadow.

server

A server is always a server application or process, one that reacts to a client application's units of work and carries them through to completion. This may involve updating persistent storage such as a database ﬁle, toggling the switch on a device, or performing another pre-deﬁned task. In the context of RTR, a server must run on a node deﬁned to have the backend role.

In other contexts, a server may be a physical node, but in RTR and in this document, physical servers are called backends or nodes.

server classes

C++ foundation classes used for implementing server applications.

Glossary–8

Image 74

Compaq Reliable Transaction Router rollback, router, RTR conﬁguration, RTR environment, RTRData object, secondary, server

Contents

January Revision/Update Information This is a new manualReliable Transaction Router Getting Started 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 5 The RTR Environment 3 Reliability Features4 RTR Interfaces Glossary Index ExamplesFigures TablesPage Document Structure PrefacePurpose of this Document Related Documentation RTR CommandsRouter Installation For all usersConventions Reading PathReaders Comments New termApplication Programmer Figure 1 RTR Reading PathSystem Manager 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 ServersRecovery Failover and RecoveryRecovery Scenarios Router FailoverBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station RTR CREATE FACILITY DESIGN/ALLROLES=NODEA $ RTRRTR SHOW JOURNAL RTR SHOW FACILITYRTR RTRRECEIVEMESSAGE/TIME=0 RTR RTRRECEIVEMESSAGE/CHAN=SRTR show transaction $ RTR RTR START RTRenters commands at the server RTR RTRRECEIVEMESSAGE/CHANNEL=C/timRTR RTRSTARTTX/CHAN=C RTR show transactionInterface Application Programming InterfacesBrowser Object-OrientedApplication Programming Interfaces Figure 4-1 RTR Browser Interfaceinterface, see the RTR C Application Programmers Reference RTR CExample of object creation in an RTR server program 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 Transaction Monitoring RTRManagement RTR Monitor pictures or the RTR Monitor let you view theManagement The RTR Runtime EnvironmentPartition Figure 5-2 RTR Runtime Environment RTR Release Notes RTR Installation GuideWhats Next? RTR Migration Guide ifPage applet GlossaryACID applicationcallout server branchbroadcast channeldata marshalling common classesconcurrent server data objectendian frontend message properties primaryprocess property classesRTR conﬁguration rollbackrouter RTR environmenttransaction shadowstandby transaction controllertransactional shadowing two-phase committransactional message Index Index-1Index-2