Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router common classes, concurrent server, data marshalling, deadlock

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 69

common classes

C++ foundation classes that can be used in both client and server applications.

concurrent server

A server process identical to other server processes running on the same node.

CPU

Central processing unit.

data marshalling

The capability of using systems of different architectures (big endian, little endian) within one application.

data object

See RTRData object.

deadlock

Deadly embrace, a situation that occurs when two transactions or parts of transactions conﬂict with each other, which could violate the consistency ACID property when committing them to the database.

disk shadowing

A process by which identical data are written to multiple disks to increase data availability in the event of a disk failure. Used in a cluster environment to replicate entire disks or disk volumes. See also transactional shadowing.

dispatch

A method in the C++ API RTRData class which, when called, interprets the contents on the RTRData object and calls an appropriate handler to process the data. The handler chosen to process the data is the handler registered with the transaction controller. This method is used with the event-driven receive model.

DTC

Microsoft Distributed Transaction Coordinator.

Glossary–3

Image 69

Compaq Reliable Transaction Router common classes, concurrent server, data marshalling, data object, deadlock, dispatch

Contents

Reliable Transaction Router Getting Started Revision/Update Information This is a new manualJanuary Compaq Computer Corporation Houston, TexasThis document was prepared using VAX DOCUMENT, Version 2001 Compaq Computer CorporationUNIX and The Open Group are trademarks of The Open Group Introduction Architectural ConceptsContents 4 RTR Interfaces 3 Reliability Features5 The RTR Environment Glossary Index ExamplesTables FiguresPage Preface Purpose of this DocumentDocument 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-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 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 theThe RTR Runtime Environment PartitionManagement 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 controllertwo-phase commit transactional messagetransactional shadowing Index-1 IndexIndex-2