Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router primary, process, properties, property classes, quorate, roles

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 73

primary

The state of the partition servicing the original data store or database. A primary has a secondary or shadow counterpart.

process

The basic software entity, including address space, scheduled by system software, that provides the context in which an image executes.

properties

Application, transaction and system information.

property classes

Classes used for obtaining information about facilities, partitions, and transactions.

quorate

Nodes/roles in a facility that has quorum are quorate.

quorum

The minimum number of routers and backends in a facility, usually a majority, who must be active and connected for the valid completion of processing.

quorum node

A node, deﬁned speciﬁed in a facility as a router, whose purpose is not to process transactions but to ensure that quorum negotiations are possible.

quorum threshold

The minimum number of routers and backends in a facility required to achieve quorum.

roles

Roles are deﬁned for each node in an RTR conﬁguration based on the requirements of a speciﬁc facility. Roles are frontend, router, or backend.

Glossary–7

Image 73

Compaq Reliable Transaction Router manual primary, process, properties, property classes, quorate, quorum node, roles

Contents

Reliable Transaction Router Getting Started Revision/Update Information This is a new manualJanuary Compaq Computer Corporation Houston, Texas2001 Compaq Computer Corporation This document was prepared using VAX DOCUMENT, VersionUNIX and The Open Group are trademarks of The Open Group Architectural Concepts IntroductionContents 4 RTR Interfaces 3 Reliability Features5 The RTR Environment Glossary Index ExamplesTables FiguresPage Purpose of this Document PrefaceDocument Structure Router Installation RTR CommandsRelated Documentation For all usersReaders Comments Reading PathConventions New termSystem Manager Figure 1 RTR Reading PathApplication Programmer If V2 toReliable Transaction Router IntroductionRTR Continuous Computing Concepts RTR Terminology Figure 1-1 Client Symbol Channel RTR conﬁguration Roles Figure 1-2 Server SymbolFigure 1-4 Facility Symbol Figure 1-3 Roles SymbolsFE TR Figure 1-5 Components in the RTR Environment 1-8 Introduction Nontransactional messaging Transaction ID Transaction ControllerFigure 1-7 Three-Tier Client/Server Environment Figure 1-6 Two-Tier Client/Server EnvironmentWeb Server Process RTR Client Application Figure 1-8 Browser Applet Conﬁguration1-10 Introduction Figure 1-10 RTR Deployed on Two Nodes Figure 1-9 RTR with Browser, Single Node, and Database1-12 Introduction Figure 1-11 RTR Deployed on Three NodesTransactional shadowing RTR Journal Figure 1-12 Standby Server ConﬁgurationFigure 1-13 Transactional Shadowing Conﬁguration RTR Server Types Concurrent servers Callout servers Transactional shadow server Figure 1-15 Standby ServersFigure 1-16 Shadow Servers Figure 1-17 Concurrent Servers Figure 1-18 A Callout Server User Accounts FacilityFigure 1-19 Bank Partitioning Example TR A partition can also have multiple standby servers Router RTR Networking CapabilitiesPage The Three-Layer Model Architectural ConceptsZKO-GS011-99AI Figure 2-1 The Three Layer ModelBroadcasts RTR Facilities Bridge the GapFlexibility and Growth Flexibility and Growth Transaction IntegrityObject-Oriented Programming The Partitioned Data ModelZKO-GS012-99AI Figure 2-2 Partitioned Data ModelTable 2-1 Functional and Object-Oriented Programming Compared ObjectsExample 2-1 Objects-Deﬁned Sample Messages Class RelationshipsPolymorphism Object Implementation Beneﬁts Programmers Reference Manual and the RTR Application Design Guide XA SupportServers Reliability FeaturesRecovery Scenarios Failover and RecoveryRecovery Router FailoverBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station RTR SHOW JOURNAL $ RTRRTR CREATE FACILITY DESIGN/ALLROLES=NODEA RTR SHOW FACILITYRTR show transaction RTR RTRRECEIVEMESSAGE/CHAN=SRTR RTRRECEIVEMESSAGE/TIME=0 $ RTR RTR START RTRRTR RTRSTARTTX/CHAN=C RTR RTRRECEIVEMESSAGE/CHANNEL=C/timenters commands at the server RTR show transactionBrowser Application Programming InterfacesInterface Object-OrientedFigure 4-1 RTR Browser Interface Application Programming InterfacesExample of object creation in an RTR server program RTR Cinterface, 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 System Management Environment The RTR EnvironmentHandles all transactions and recovery Page Management Monitoring RTRTransaction RTR Monitor pictures or the RTR Monitor let you view thePartition The RTR Runtime EnvironmentManagement Figure 5-2 RTR Runtime Environment Whats Next? RTR Installation GuideRTR Release Notes RTR Migration Guide ifPage ACID Glossaryapplet applicationbroadcast branchcallout server channelconcurrent server common classesdata marshalling data objectendian frontend message process primaryproperties property classesrouter rollbackRTR conﬁguration RTR environmentstandby shadowtransaction transaction controllertransactional message two-phase committransactional shadowing Index-1 IndexIndex-2