Compaq Reliable Transaction Router Frontend, Inquorate, Journal, Key range, Key segment, Link

Page 71

frontend

FE, the physical node in an RTR facility where the client application runs.

FTP

File transfer protocol.

inquorate

Nodes/roles that cannot participate in a facility's transactions are inquorate.

journal

A ﬁle containing transactional messages used for recovery.

key range

An attribute of a key segment, for example a range A to E or F to K.

key segment

An attribute of a partition that deﬁnes the type and range of values that the partition handles.

LAN

Local area network.

link

A communications path between two nodes in a network.

local node

The node on which a C++ API client or server application runs. The local node is the computer on which this instance of the RTR application is executing.

management classes

C++ API classes used by new or existing applications to manage RTR.

member

See facility member.

Glossary–5

Image 71

Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Document Structure PrefacePurpose of this Document For all users Related DocumentationReaders Comments Reading Path= Tutorial System Manager Application ProgrammerIf V2 to 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 Business Logic Odbc Model Database ServerApplication Presentation 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 ModelRTR Facilities Bridge the Gap RTR Facilities Bridge the GapBroadcasts Flexibility and GrowthFlexibility and Growth Transaction IntegrityPartitioned Data Model Partitioned Data ModelObject-Oriented Programming 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 Failover and RecoveryRecovery Scenarios 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 Optional External Applet Not Running RTR Runtime EnvironmentClient Application Whats Next? Whats Next?Page Glossary Channel BranchBroadcast Callout serverData object Common classesConcurrent server Data marshallingEvent driven Fault tolerantEndian EventKey range FrontendInquorate JournalMultithreaded MessageMessage handler MultichannelProperty classes PrimaryProcess PropertiesRTR environment RollbackRouter RTR conﬁgurationTransaction controller ShadowStandby TransactionTransactional shadowing Two-phase commitTransactional message Index-1 IndexIndex-2