Compaq Reliable Transaction Router manual RTR Environment, RTR System Management Environment

Page 59

5

The RTR Environment

The RTR environment has two parts:

The system management environment

The runtime environment

The RTR System Management Environment

You manage your RTR environment from a management station, which can be on a node running RTR or on some other node. You can manage your RTR environment either from your management station running a network browser, or from the command line using the RTR CLI. From a managment station using a network browser, processes use the http protocol for communication.

The RTR system management environment contains four processes:

The RTR Control Process, RTRACP

The RTR Command Line Interface, RTR CLI

The RTR Command Server Process, RTRCOMSERV

The RTR daemon, RTRD

The RTR Control Process, RTRACP, is the master program. It resides on every node where RTR has been installed and is running. RTRACP performs the following functions:

Manages network links

Sends messages between nodes

The RTR Environment 5–1

Image 59
Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Document Structure PrefacePurpose of this Document For all users Related DocumentationReaders Comments Reading Path= Tutorial System Manager Application ProgrammerIf V2 to 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 Business Logic Odbc Model Database ServerApplication Presentation RTR Frontend PC BrowserJournal Browser11 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 Server1 Server2 Server3 Server4 17 Concurrent ServersPartition a Transaction19 Bank Partitioning Example Standby Server Configurations 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 IntegrityPartitioned Data Model Partitioned Data ModelObject-Oriented Programming Partitioned Data Model Object-Oriented ProgrammingFunctional and Object-Oriented Programming Compared ObjectsExample 2-1 Objects-Defined Sample Messages Class RelationshipsPolymorphism Object Implementation Benefits XA Support XA SupportServers Reliability FeaturesFailover and Recovery Failover and RecoveryRecovery Scenarios 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 Optional External Applet Not Running RTR Runtime EnvironmentClient Application 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 configurationTransaction controller ShadowStandby TransactionTransactional shadowing Two-phase commitTransactional message Index-1 IndexIndex-2