Compaq Reliable Transaction Router Primary, Process, Properties, Property classes, Quorate, Roles

Page 73

primary

The state of the partition servicing the original data store or database. A primary has a secondary or shadow counterpart.

process

The basic software entity, including address space, scheduled by system software, that provides the context in which an image executes.

properties

Application, transaction and system information.

property classes

Classes used for obtaining information about facilities, partitions, and transactions.

quorate

Nodes/roles in a facility that has quorum are quorate.

quorum

The minimum number of routers and backends in a facility, usually a majority, who must be active and connected for the valid completion of processing.

quorum node

A node, defined specified in a facility as a router, whose purpose is not to process transactions but to ensure that quorum negotiations are possible.

quorum threshold

The minimum number of routers and backends in a facility required to achieve quorum.

roles

Roles are defined for each node in an RTR configuration based on the requirements of a specific facility. Roles are frontend, router, or backend.

Glossary–7

Image 73
Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Purpose of this Document PrefaceDocument Structure For all users Related DocumentationReaders Comments Reading PathIf V2 to System Manager Application Programmer= 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 Application Presentation Database ServerBusiness 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 IntegrityObject-Oriented Programming Partitioned Data ModelPartitioned 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 FeaturesRecovery Scenarios Failover and RecoveryFailover 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 Client Application RTR Runtime EnvironmentOptional 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 controllerTransactional message Two-phase commitTransactional shadowing Index-1 IndexIndex-2