Compaq Reliable Transaction Router manual Transactional Shadowing Configuration

Page 24

RTR Terminology

Figure 1–13 Transactional Shadowing Configuration

FE

TR

BE

Server

BE

Server

Primary

Server

Shadow

Server

LKG-11211-98WI

With transactional shadowing, there is no requirement that hardware, the data store, or the operating system at different sites be the same. You could, for example, have one site running OpenVMS and another running Windows NT; the RTR transactional commit process would be the same at each site.

Note

Transactional shadowing shadows only transactions controlled by RTR.

For full redundancy to assure maximum availability, a configuration could employ both disk shadowing in clusters at separate sites coupled with transactional shadowing across sites with standby servers at each site. This configuration is shown in Figure 1–14. For clarity, not all possible connections are shown. In the figure, backends running standby servers are shaded, connected to routers by dashed lines. Only one site (the upper site) does full disk shadowing; the lower site is the shadow for transactions, shadowing all transactions being done at the upper site.

1–14Introduction

Image 24
Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Preface Purpose of this DocumentDocument Structure Related Documentation For all usersReading Path Readers CommentsSystem Manager Application Programmer If V2 to= 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 Database Server Application PresentationBusiness 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 GrowthPartitioned Data Model Object-Oriented ProgrammingPartitioned 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 ServersFailover and Recovery Recovery ScenariosFailover 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 RTR Runtime Environment Client ApplicationOptional 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 controllerTwo-phase commit Transactional messageTransactional shadowing Index Index-1Index-2