Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router $ Rtr, Rtr Show Journal, Rtr Show Facility, RTR Interfaces

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 52

rtr_mt_opened

normal successful completion

RTR Management Station

[The user issues the following commands on the server application where RTR is running on the backend.]

$ RTR

Copyright Compaq Computer Corporation 1994. RTR> set mode/group

%RTR-I-STACOMSRV, starting command server on node NODEA %RTR-I-GRPMODCHG, group changed from " " to "username" %RTR-I-SRVDISCON, server disconnected on node NODEA RTR> CREATE JOURNAL

%RTR-I-STACOMSRV, starting command server on node NODEA in group "username" %RTR-S-JOURNALINI, journal has been created on device D:

RTR> SHOW JOURNAL

Journal configuration on NODEA in group "username" at Mon Aug 28 14:54:11 2000:-

Disk: D:\ Blocks: 1000

RTR> start rtr %RTR-I-NOLOGSET, logging not set

%RTR-S-RTRSTART, RTR started on node NODEA in group "username"

RTR> CREATE FACILITY DESIGN/ALL_ROLES=(NODEA)

[- or /all=NODEA,NODEB] %RTR-S-FACCREATED, facility DESIGN created

RTR> SHOW FACILITY

Facilities on node NODEA in group "username" at Mon Aug 28 15:00:28 2000:

Facility	Frontend	Router	Backend
DESIGN	yes	yes	yes

RTR> rtr_open/server/accept_explicit/prepare_explicit/chan=s/fac=DESIGN %RTR-S-OK, normal successful completion

RTR> RTR_RECEIVE_MESSAGE/CHAN=S %RTR-S-OK, normal successful completion channel name: S

.

.

.

msgtype:

.

.

.

status:

[When the next command is issued, RTR waits for a message from the client.]

4–4RTR Interfaces

Image 52

Compaq Reliable Transaction Router $ Rtr, Rtr Show Journal, Rtr Create Facility Design/Allroles=Nodea, Rtr Show Facility

Contents

Revision/Update Information This is a new manual Reliable Transaction Router Getting StartedJanuary Compaq Computer Corporation Houston, Texas2001 Compaq Computer Corporation This document was prepared using VAX DOCUMENT, VersionUNIX and The Open Group are trademarks of The Open Group Architectural Concepts IntroductionContents 3 Reliability Features 4 RTR Interfaces5 The RTR Environment Glossary Index ExamplesFigures TablesPage Purpose of this Document PrefaceDocument Structure RTR Commands Router InstallationRelated Documentation For all usersReading Path Readers CommentsConventions New termFigure 1 RTR Reading Path System ManagerApplication Programmer 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 RolesFigure 1-4 Facility Symbol Figure 1-3 Roles SymbolsFE TR 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 EnvironmentWeb Server Process RTR Client Application Figure 1-8 Browser Applet Conﬁguration1-10 Introduction 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-99AIBroadcasts RTR Facilities Bridge the GapFlexibility and Growth 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 ServersFailover and Recovery Recovery ScenariosRecovery Router FailoverBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station $ RTR RTR SHOW JOURNALRTR CREATE FACILITY DESIGN/ALLROLES=NODEA RTR SHOW FACILITYRTR RTRRECEIVEMESSAGE/CHAN=S RTR show transactionRTR RTRRECEIVEMESSAGE/TIME=0 $ RTR RTR START RTRRTR RTRRECEIVEMESSAGE/CHANNEL=C/tim RTR RTRSTARTTX/CHAN=Centers commands at the server RTR show transactionApplication Programming Interfaces BrowserInterface Object-OrientedApplication Programming Interfaces Figure 4-1 RTR Browser InterfaceRTR C Example of object creation in an RTR server programinterface, see the RTR C Application Programmers Reference 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 Monitoring RTR ManagementTransaction RTR Monitor pictures or the RTR Monitor let you view thePartition The RTR Runtime EnvironmentManagement Figure 5-2 RTR Runtime Environment RTR Installation Guide Whats Next?RTR Release Notes RTR Migration Guide ifPage Glossary ACIDapplet applicationbranch broadcastcallout server channelcommon classes concurrent serverdata marshalling data objectendian frontend message primary processproperties property classesrollback routerRTR conﬁguration RTR environmentshadow standbytransaction transaction controllertransactional message two-phase committransactional shadowing Index Index-1Index-2