Compaq Reliable Transaction Router manual Monitoring RTR

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 file 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
Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Document Structure PrefacePurpose of this Document Related Documentation For all usersReading Path Readers Comments= Tutorial System Manager Application ProgrammerIf V2 to 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 Business Logic Odbc Model Database ServerApplication Presentation 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 ModelFlexibility and Growth RTR Facilities Bridge the GapBroadcasts RTR Facilities Bridge the GapTransaction Integrity Flexibility and GrowthPartitioned Data Model Partitioned Data ModelObject-Oriented Programming 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 Failover and RecoveryRecovery Scenarios 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 Optional External Applet Not Running RTR Runtime EnvironmentClient Application Whats Next? Whats Next?Page Glossary Callout server BranchBroadcast ChannelData marshalling Common classesConcurrent server Data objectEvent Fault tolerantEndian Event drivenJournal FrontendInquorate Key rangeMultichannel MessageMessage handler MultithreadedProperties PrimaryProcess Property classesRTR configuration RollbackRouter RTR environmentTransaction ShadowStandby Transaction controllerTransactional shadowing Two-phase commitTransactional message Index Index-1Index-2