Compaq Reliable Transaction Router manual Database Server, Application Presentation

Page 19

RTR Terminology

Figure 1–6 Two-Tier Client/Server Environment

DM

								Database Server


	Application Presentation
	Application Presentation
	and Business Logic
	(ODBC Model)							LKG-11204-98WI

Figure 1–7 Three-Tier Client/Server Environment

DB

Server

Database

Application

Presentation/	Application Server/ Database Server
User Interface	Business Logic	LKG-11205-98WI
		LKG-11205-98WI

RTR provides a multicomponent software model where clients running on frontends, routers, and servers running on backends cooperate to provide reliable service and transactional integrity. Application users interact with the client (presentation layer) on the frontend node that forwards messages to the current router. The router in turn routes the messages to the current, appropriate backend, where server applications reside, for processing. The connection to the current router is maintained until the current router fails or connections to it are lost.

Introduction 1–9

Image 19

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 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 IntegrityObject-Oriented Programming Partitioned Data ModelPartitioned Data Model 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 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 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 message Two-phase commitTransactional shadowing Index-1 IndexIndex-2