Compaq Reliable Transaction Router manual RTR Continuous Computing Concepts

Page 12

RTR Continuous Computing Concepts

RTR Continuous Computing Concepts

RTR provides a continuous computing environment that is particularly valuable in ﬁnancial transactions, for example in banking, stock trading, or passenger reservations systems. RTR satisﬁes many requirements of a continuous computing environment:

•Reliability

•Failure tolerance

•Data and transaction integrity

•Scalability

•Ease of building and maintaining applications

•Interoperability with multiple operating systems

RTR additionally provides the following capabilities, essential in the demanding transaction processing environment:

•Flexibility

•Parallel execution at the transaction level

•Potential for step-by-step growth

•Comprehensive monitoring tools

•Management station for single console system management

•WAN deployability

RTR also ensures that transactions have the ACID properties. A transaction with the ACID properties has the following attributes:

•Atomic

•Consistent

•Isolated

•Durable

For more details on transactional ACID properties, see the discussion later in this document, and in the RTR Application Design Guide.

1–2Introduction

Image 12

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 Conﬁguration 13 Transactional Shadowing Conﬁguration 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 Conﬁgurations 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-Deﬁned SamplePolymorphism Object Implementation Beneﬁts 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 conﬁguration RTR environmentShadow StandbyTransaction Transaction controllerTwo-phase commit Transactional messageTransactional shadowing Index Index-1Index-2