Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router manual 2 Server Symbol, Channel RTR conﬁguration Roles

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 15

Channel

RTR conﬁguration

Roles

RTR Terminology

Figure 1–2 Server Symbol

RTR expects client and server applications to identify themselves before they request RTR services. During the identiﬁcation process, RTR provides a tag or handle that is used for subsequent interactions. This tag or handle is called an RTR channel. A channel is used by client and server applications to exchange units of work with the help of RTR. An application process can have one or more client or server channels.

An RTR conﬁguration consists of nodes that run RTR client and server applications. An RTR conﬁguration can run on several operating systems including OpenVMS, Tru64 UNIX, and Windows NT among others (for the full set of supported operating systems, see the title page of this document, and the appropriate SPD). Nodes are connected by network links.

A node that runs client applications is called a frontend (FE), or is said to have the frontend role. A node that runs server applications is called a backend (BE). Additionally, the transaction router (TR) contains no application software but acts as a trafﬁc cop between frontends and backends, routing transactions to the appropriate destinations. The router also eliminates any need for frontends and backends to know about each other in advance. This relieves the application programmer from the need to be concerned about network conﬁguration details.

Introduction 1–5

Image 15

Compaq Reliable Transaction Router manual 2 Server Symbol, Channel RTR conﬁguration Roles

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