Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router manual Architectural Concepts, The Three-Layer Model

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 35

Architectural Concepts

2

Architectural Concepts

This chapter introduces concepts on basic transaction processing and RTR architecture.

The Three-Layer Model

RTR is based on a three-layer architecture consisting of frontend (FE) roles, backend (BE) roles and router (TR) roles. The roles are shown in Figure 2–1. In this and subsequent diagrams, rectangles represent physical nodes, ovals represent application software, and DB represents the disks storing the database (and usually the database software that runs on the server).

Client processes run on nodes deﬁned to have the frontend role. This layer allows computing power to be provided locally at the end-user site for transaction acquisition and presentation.

Server processes (represented by ``Server'' in Figure 2–1) run on nodes deﬁned to have the backend role. This layer:

•Allows the database to be distributed geographically.

•Permits replication of servers to cope with either network, node or site failures.

•Allows computer resources to be added to meet performance requirements.

Architectural Concepts 2–1

Image 35

Compaq Reliable Transaction Router manual Architectural Concepts, The Three-Layer Model

Contents

Compaq Computer Corporation Houston, Texas Revision/Update Information This is a new manualReliable Transaction Router Getting Started JanuaryUNIX and The Open Group are trademarks of The Open Group This document was prepared using VAX DOCUMENT, Version2001 Compaq Computer Corporation Contents IntroductionArchitectural Concepts Glossary Index Examples 3 Reliability Features4 RTR Interfaces 5 The RTR EnvironmentTables FiguresPage Document Structure PrefacePurpose of this Document 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 SymbolFE TR Figure 1-3 Roles SymbolsFigure 1-4 Facility Symbol 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 Environment1-10 Introduction Figure 1-8 Browser Applet ConﬁgurationWeb Server Process RTR Client Application 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 ModelFlexibility and Growth RTR Facilities Bridge the GapBroadcasts 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 TransactionManagement The RTR Runtime EnvironmentPartition 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 transactiontransactional shadowing two-phase committransactional message Index-1 IndexIndex-2