Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router manual shadow, standby, transaction controller

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 75

shadow

The state of the server process that services a copy of the data store or primary database. In the context of RTR, the shadow method is transactional shadowing, not disk shadowing. Its counterpart is primary.

SMP

Symmetric MultiProcessing.

standby

The state of the partition that can take over if the process for which it is on standby is unavailable. It is held in reserve, ready for use.

TPS

Transactions per second.

transaction

An operation performed on a database, typically causing an update to the database. Analogous in many cases to a business transaction such as executing a stock trade or purchasing an item in a store. A business transaction may consist of one or more than one RTR transaction. A transaction is classiﬁed as original, replay, or recovery, depending on how it arrives at the backend:

Original—Transaction arrived on the ﬁrst attempt from the client.

Replay—Transaction arrived after some failure as the result of a re-send from the client (that is, from the client transaction-replay buffers in the RTRACP). Recovery—Transaction arrived as the result of a backend- to-backend recovery operation (recovery from the journal).

transaction controller

A transaction controller processes transactions. A transaction controller may have 0 or 1 transactions active at any moment in time. It is through the transaction controller that messages and events are sent and received.

Glossary–9

Image 75

Compaq Reliable Transaction Router manual shadow, standby, transaction controller

Contents

Compaq Computer Corporation Houston, Texas Revision/Update Information This is a new manualReliable Transaction Router Getting Started JanuaryThis document was prepared using VAX DOCUMENT, Version 2001 Compaq Computer CorporationUNIX and The Open Group are trademarks of The Open Group Introduction Architectural ConceptsContents Glossary Index Examples 3 Reliability Features4 RTR Interfaces 5 The RTR EnvironmentTables FiguresPage Preface Purpose of this DocumentDocument Structure For all users RTR CommandsRouter Installation Related DocumentationNew term Reading PathReaders Comments ConventionsIf V2 to Figure 1 RTR Reading PathSystem Manager Application ProgrammerReliable Transaction Router IntroductionRTR Continuous Computing Concepts RTR Terminology Figure 1-1 Client Symbol Channel RTR conﬁguration Roles Figure 1-2 Server SymbolFigure 1-3 Roles Symbols Figure 1-4 Facility SymbolFE 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 EnvironmentFigure 1-8 Browser Applet Conﬁguration Web Server Process RTR Client Application1-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 ModelRTR Facilities Bridge the Gap BroadcastsFlexibility 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 FeaturesRouter Failover Failover and RecoveryRecovery Scenarios RecoveryBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station RTR SHOW FACILITY $ RTRRTR SHOW JOURNAL RTR CREATE FACILITY DESIGN/ALLROLES=NODEA$ RTR RTR START RTR RTR RTRRECEIVEMESSAGE/CHAN=SRTR show transaction RTR RTRRECEIVEMESSAGE/TIME=0RTR show transaction RTR RTRRECEIVEMESSAGE/CHANNEL=C/timRTR RTRSTARTTX/CHAN=C enters commands at the serverObject-Oriented Application Programming InterfacesBrowser InterfaceFigure 4-1 RTR Browser Interface Application Programming InterfacesManual and the RTR Application Design Guide RTR CExample of object creation in an RTR server program interface, see the RTR C Application Programmers ReferenceExample of an open channel call in an RTR client program The RTR System Management Environment The RTR EnvironmentHandles all transactions and recovery Page RTR Monitor pictures or the RTR Monitor let you view the Monitoring RTRManagement TransactionThe RTR Runtime Environment PartitionManagement Figure 5-2 RTR Runtime Environment RTR Migration Guide if RTR Installation GuideWhats Next? RTR Release NotesPage application GlossaryACID appletchannel branchbroadcast callout serverdata object common classesconcurrent server data marshallingendian frontend message property classes primaryprocess propertiesRTR environment rollbackrouter RTR conﬁgurationtransaction controller shadowstandby transactiontwo-phase commit transactional messagetransactional shadowing Index-1 IndexIndex-2