Compaq Reliable Transaction Router manual Browser, Journal

Page 21

RTR Terminology

single node configuration can be useful during development, but would not normally be used when your application is deployed.

Figure 1–9 RTR with Browser, Single Node, and Database

Browser

FE

TR

BE

DB

LKG-11207-98WI

When creating the configuration used by an application and defining the nodes where a facility has its frontends, routers, and backends, the setup must also define which nodes will have journal files. Each backend in an RTR configuration must have a journal file to capture transactions when other nodes are unavailable. When applications are deployed, often the backend is separated from the frontend and router, as shown in Figure 1–10.

Figure 1–10 RTR Deployed on Two Nodes

Browser

FE

TR

Client

BE

Server

DB

Journal

LKG-11208-98WI

Introduction 1–11

Image 21
Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Preface Purpose of this DocumentDocument Structure For all users Related DocumentationReaders Comments Reading PathSystem Manager Application Programmer If V2 to= Tutorial Reliable Transaction Router IntroductionRTR Continuous Computing Concepts RTR Continuous Computing ConceptsRTR Terminology RTR TerminologyClient Symbol Server Symbol Roles Symbols Components in the RTR Environment Nontransactional messaging Transaction ID Controller Database Server Application PresentationBusiness Logic Odbc Model RTR Frontend PC BrowserJournal Browser11 RTR Deployed on Three Nodes 12 Standby Server Configuration 13 Transactional Shadowing Configuration RTR Server Types RTR Server TypesStandby server Standby in a cluster 15 Standby Servers 16 Shadow Servers Server1 Server2 Server3 Server4 17 Concurrent ServersPartition a Transaction19 Bank Partitioning Example Standby Server Configurations Anonymous clients Tunnel RTR Networking Capabilities RTR Networking CapabilitiesPage Three-Layer Model Architectural ConceptsThree Layer Model Three-Layer ModelBroadcasts RTR Facilities Bridge the GapFlexibility and Growth RTR Facilities Bridge the GapFlexibility and Growth Transaction IntegrityPartitioned Data Model Object-Oriented ProgrammingPartitioned Data Model Partitioned Data Model Object-Oriented ProgrammingFunctional and Object-Oriented Programming Compared ObjectsExample 2-1 Objects-Defined Sample Messages Class RelationshipsPolymorphism Object Implementation Benefits XA Support XA SupportServers Reliability FeaturesFailover and Recovery Recovery ScenariosFailover and Recovery Recovery Scenarios Backend Recovery Router Recovery Frontend RecoveryPage RTR Interfaces RTR Management Station RTR Management Station RTR Create Facility DESIGN/ALLROLES=NODEA RTR RTRRECEIVEMESSAGE/TIME=0 RTR RTRSTARTTX/CHAN=C Interface Application Programming InterfacesRTR Browser Interface Application Programming InterfacesRTR C Example of an open channel call in an RTR client program RTR System Management Environment RTR EnvironmentRtrcomserv RTR System Management EnvironmentManagement Station Running Browser Software RTR System Management EnvironmentMonitoring RTR RTR Runtime Environment RTR Runtime Environment Client ApplicationOptional External Applet Not Running Whats Next? Whats Next?Page Glossary Broadcast BranchCallout server ChannelConcurrent server Common classesData marshalling Data objectEndian Fault tolerantEvent Event drivenInquorate FrontendJournal Key rangeMessage handler MessageMultichannel MultithreadedProcess PrimaryProperties Property classesRouter RollbackRTR configuration RTR environmentStandby ShadowTransaction Transaction controllerTwo-phase commit Transactional messageTransactional shadowing Index-1 IndexIndex-2