Compaq Reliable Transaction Router manual Reliability Features, Servers

Page 45

3

Reliability Features

Reliability in RTR is enhanced by the use of:

•Concurrent servers

•Standby servers

•Shadow servers

•Callout servers

•Router failover

Servers

Note that, conceptually, servers can be contrasted as follows:

•Concurrent servers handle similar transactions which access the same data partition and run on the same node.

•Shadow servers handle the same transactions and run on different nodes.

•Standby servers provide a node that can take over processing on a data partition when the primary server or node fails.

•Callout servers run on backends or routers and receive all messages within a facility so that authentication and logging operations can be performed in parallel.

All servers are further described in the earlier section on RTR

Terminology.

Reliability Features 3–1

Image 45

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 Conﬁguration 13 Transactional Shadowing Conﬁguration 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 Conﬁgurations 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-Deﬁned Sample Messages Class RelationshipsPolymorphism Object Implementation Beneﬁts 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 conﬁguration RTR environmentStandby ShadowTransaction Transaction controllerTwo-phase commit Transactional messageTransactional shadowing Index-1 IndexIndex-2