Compaq Reliable Transaction Router manual Roles Symbols

Page 16

RTR Terminology

Figure 1–3 Roles Symbols

FE

TR

BE

Facility

The mapping between nodes and roles is done using a facility.

 

An RTR facility is the user-defined name for a particular

 

configuration whose definition provides the role-to-node map for

 

a given application. Nodes can share several facilities. The role

 

of a node is defined within the scope of a particular facility. The

 

router is the only role that knows about all three roles. A router

 

can run on the same physical node as the frontend or backend,

 

if that is required by configuration constraints, but such a setup

 

would not take full advantage of failover characteristics.

 

Figure 1–4 Facility Symbol

A facility name is mapped to specific physical nodes and their roles using the CREATE FACILITY command.

Figure 1–5 shows the logical relationship between client application, server application, frontends (FEs), routers (TRs), and backends (BEs) in the RTR environment. The database is represented by the cylinder. Two facilities are shown (indicated by the large double-headed arrows), the user accounts facility and the general ledger facility. The user accounts facility uses three nodes, FE, TR, and BE, while the general ledger facility uses only two, TR and BE.

Clients send messages to servers to ask that a piece of work be done. Such requests may be bundled together into transactions. An RTR transaction consists of one or more messages that have been grouped together by a client application, so that the work done as a result of each message can be undone completely, if some part of that work cannot be done. If the system fails or is

1–6Introduction

Image 16
Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Purpose of this Document PrefaceDocument Structure Related Documentation For all usersReading Path Readers CommentsIf V2 to System Manager Application Programmer= Tutorial Introduction Reliable Transaction RouterRTR 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 PC Browser RTR FrontendBrowser Journal11 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 17 Concurrent Servers Server1 Server2 Server3 Server4Transaction Partition a19 Bank Partitioning Example Standby Server Configurations Anonymous clients Tunnel RTR Networking Capabilities RTR Networking CapabilitiesPage Architectural Concepts Three-Layer ModelThree-Layer Model Three Layer ModelRTR Facilities Bridge the Gap BroadcastsFlexibility and Growth RTR Facilities Bridge the GapTransaction Integrity Flexibility and GrowthObject-Oriented Programming Partitioned Data ModelPartitioned Data Model Object-Oriented Programming Partitioned Data ModelObjects Functional and Object-Oriented Programming ComparedMessages Class Relationships Example 2-1 Objects-Defined SamplePolymorphism Object Implementation Benefits XA Support XA SupportReliability Features ServersRecovery Scenarios Failover and RecoveryFailover and Recovery Backend Recovery Router Recovery Frontend Recovery Recovery ScenariosPage RTR Interfaces RTR Management Station RTR Management Station RTR Create Facility DESIGN/ALLROLES=NODEA RTR RTRRECEIVEMESSAGE/TIME=0 RTR RTRSTARTTX/CHAN=C Application Programming Interfaces InterfaceApplication Programming Interfaces RTR Browser InterfaceRTR C Example of an open channel call in an RTR client program RTR Environment RTR System Management EnvironmentRTR System Management Environment RtrcomservRTR System Management Environment Management Station Running Browser SoftwareMonitoring RTR RTR Runtime Environment Client Application RTR Runtime EnvironmentOptional External Applet Not Running Whats Next? Whats Next?Page Glossary Branch BroadcastCallout server ChannelCommon classes Concurrent serverData marshalling Data objectFault tolerant EndianEvent Event drivenFrontend InquorateJournal Key rangeMessage Message handlerMultichannel MultithreadedPrimary ProcessProperties Property classesRollback RouterRTR configuration RTR environmentShadow StandbyTransaction Transaction controllerTransactional message Two-phase commitTransactional shadowing Index Index-1Index-2