Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router manual Monitoring RTR, Management

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 62

The RTR System Management Environment

Monitoring RTR	RTR Monitor pictures or the RTR Monitor let you view the
	status and activities of RTR and your applications. A monitor
	picture is dynamic, its data periodically updated. RTR SHOW
	commands that also let you view status are snapshots, giving
	you a view at one moment in time. A full list of RTR Monitor
	pictures is available in the RTR System Manager's Manual ``RTR
	Monitoring'' chapter and in the help ﬁle under RTR_Monitoring.
	Many RTR Monitor pictures are available using the RTR browser
	interface.
Transaction	The RTR transaction is the heart of an RTR application,
Management	and transaction state characterizes the current condition of a
	transaction. As a transaction passes from one state to another, it
	undergoes a state transition. Transaction states are maintained
	in memory, and some are stored in the RTR journal for use in
	recovery.
	RTR uses three transaction states to track transaction status:
	•	transaction runtime state
	•	transaction journal state
	•	transaction server state

Transaction runtime state describes how a transaction progresses from the point of view of RTR roles (FE, TR, BE). A transaction, for example, can be in one state as seen from the frontend, and in another as seen from the router.

Transaction journal state describes how a transaction progresses from the point of view of the RTR journal. The transaction journal state, not seen by frontends and routers, managed by the backend, is used by RTR for recovery replay of a transaction after a failure.

Transaction server state, also managed by the backend, describes how a transaction progresses from the point of view of the server. RTR uses this state to determine if a server is available to process a new transaction, or if a server has voted on a particular transaction.

The RTR SHOW TRANSACTION command shows transaction status, and the RTR SET TRANSACTION command can be used, under certain well-constrained circumstances, to change the state of a live transaction. For more details on use of SHOW and SET commands, see the RTR System Manager's Manual.

5–4The RTR Environment

Image 62

Compaq Reliable Transaction Router Monitoring RTR, Management, RTR Monitor pictures or the RTR Monitor let you view the

Contents

January Revision/Update Information This is a new manualReliable Transaction Router Getting Started Compaq Computer Corporation Houston, TexasUNIX and The Open Group are trademarks of The Open Group This document was prepared using VAX DOCUMENT, Version2001 Compaq Computer Corporation Contents IntroductionArchitectural Concepts 5 The RTR Environment 3 Reliability Features4 RTR Interfaces Glossary Index ExamplesFigures TablesPage Document Structure PrefacePurpose of this Document Related Documentation RTR CommandsRouter Installation For all usersConventions Reading PathReaders Comments New termApplication Programmer Figure 1 RTR Reading PathSystem Manager If V2 toIntroduction Reliable Transaction RouterRTR Continuous Computing Concepts RTR Terminology Figure 1-1 Client Symbol Figure 1-2 Server Symbol Channel RTR conﬁguration RolesFE TR Figure 1-3 Roles SymbolsFigure 1-4 Facility Symbol Figure 1-5 Components in the RTR Environment Nontransactional messaging Transaction ID Transaction Controller 1-8 IntroductionFigure 1-6 Two-Tier Client/Server Environment Figure 1-7 Three-Tier Client/Server Environment1-10 Introduction Figure 1-8 Browser Applet ConﬁgurationWeb Server Process RTR Client Application Figure 1-9 RTR with Browser, Single Node, and Database Figure 1-10 RTR Deployed on Two NodesFigure 1-11 RTR Deployed on Three Nodes 1-12 IntroductionFigure 1-12 Standby Server Conﬁguration Transactional shadowing RTR JournalFigure 1-13 Transactional Shadowing Conﬁguration RTR Server Types Concurrent servers Callout servers Figure 1-15 Standby Servers Transactional shadow serverFigure 1-16 Shadow Servers Figure 1-17 Concurrent Servers User Accounts Facility Figure 1-18 A Callout ServerFigure 1-19 Bank Partitioning Example TR A partition can also have multiple standby servers RTR Networking Capabilities RouterPage Architectural Concepts The Three-Layer ModelFigure 2-1 The Three Layer Model ZKO-GS011-99AIFlexibility and Growth RTR Facilities Bridge the GapBroadcasts Transaction Integrity Flexibility and GrowthThe Partitioned Data Model Object-Oriented ProgrammingFigure 2-2 Partitioned Data Model ZKO-GS012-99AIObjects Table 2-1 Functional and Object-Oriented Programming ComparedMessages Class Relationships Example 2-1 Objects-Deﬁned SamplePolymorphism Object Implementation Beneﬁts XA Support Programmers Reference Manual and the RTR Application Design GuideReliability Features ServersRecovery Failover and RecoveryRecovery Scenarios Router FailoverBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station RTR CREATE FACILITY DESIGN/ALLROLES=NODEA $ RTRRTR SHOW JOURNAL RTR SHOW FACILITYRTR RTRRECEIVEMESSAGE/TIME=0 RTR RTRRECEIVEMESSAGE/CHAN=SRTR show transaction $ RTR RTR START RTRenters commands at the server RTR RTRRECEIVEMESSAGE/CHANNEL=C/timRTR RTRSTARTTX/CHAN=C RTR show transactionInterface Application Programming InterfacesBrowser Object-OrientedApplication Programming Interfaces Figure 4-1 RTR Browser Interfaceinterface, see the RTR C Application Programmers Reference RTR CExample of object creation in an RTR server program Manual and the RTR Application Design GuideExample of an open channel call in an RTR client program The RTR Environment The RTR System Management EnvironmentHandles all transactions and recovery Page Transaction Monitoring RTRManagement RTR Monitor pictures or the RTR Monitor let you view theManagement The RTR Runtime EnvironmentPartition Figure 5-2 RTR Runtime Environment RTR Release Notes RTR Installation GuideWhats Next? RTR Migration Guide ifPage applet GlossaryACID applicationcallout server branchbroadcast channeldata marshalling common classesconcurrent server data objectendian frontend message properties primaryprocess property classesRTR conﬁguration rollbackrouter RTR environmenttransaction shadowstandby transaction controllertransactional shadowing two-phase committransactional message Index Index-1Index-2