Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router manual Rtr Rtrreceivemessage/Chan=S, RTR show transaction

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 53

				RTR Management Station
RTR> RTR_RECEIVE_MESSAGE/CHAN=S
%RTR-S-OK, normal successful completion
channel name: S
msgsb
msgtype:		rtr_mt_msg1
msglen:		19
usrhdl:		0
Tid:		63b01d10,0,0,0,0,2e59,43ea2002
message
offset	bytes			text
000000	4B 61		74 68 79 27 73 20 74 65 78 74 20 74 6F 64	Kathy's text tod
000010	61 79		00	ay.
reason:		Ox00000000

RTR> RTR_REPLY_TO_CLIENT/CHAN=S "And this is my response." %RTR-S-OK, normal successful completion

RTR> show transaction

Frontend transactions on node NodeA in group "username" at Mon Aug 28 15:12:10 2000

Tid	Facility	FE-User	State
63b01d10,0,0,0,0,2e59,43ea2002	DESIGN	username.	SENDING

Router transactions on node NodeA in group "username" at Mon Aug 28 15:12:10 2000:

63b01d10,0,0,0,0,2e59,43ea2002 DESIGN username. SENDING

Backend transactions on node NodeA in group "username" at Mon Aug 28 15:12:10 2000:

63b01d10,0,0,0,0,2e59,43ea2002 DESIGN		username.	RECEIVING
RTR> RTR_RECEIVE_MESSAGE/CHAN=S
%RTR-S-OK, normal successful completion
channel name: S
msgsb
msgtype:	rtr_mt_prepare
[if OK, use: RTR_ACCEPT_TX
else, use: RTR_REJECT_TX]
RTR> RTR_RECEIVE_MESSAGE/TIME=0
RTR> STOP RTR	[Ends example test.]

[Commands and system response at client.]

$ RTR

RTR> START RTR

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

RTR> RTR_OPEN_CHANNEL/CHANNEL=C/CLIENT/fac=DESIGN %RTR-S-OK, normal successful completion

RTR Interfaces 4–5

Image 53

Compaq Reliable Transaction Router manual Rtr Rtrreceivemessage/Chan=S, RTR show transaction, RTR RTRRECEIVEMESSAGE/TIME=0

Contents

Reliable Transaction Router Getting Started Revision/Update Information This is a new manualJanuary 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 4 RTR Interfaces 3 Reliability Features5 The RTR Environment Glossary Index ExamplesTables FiguresPage Document Structure PrefacePurpose of this Document Router Installation RTR CommandsRelated Documentation For all usersReaders Comments Reading PathConventions New termSystem Manager Figure 1 RTR Reading PathApplication Programmer If V2 toReliable Transaction Router IntroductionRTR Continuous Computing Concepts RTR Terminology Figure 1-1 Client Symbol Channel RTR conﬁguration Roles Figure 1-2 Server SymbolFE TR Figure 1-3 Roles SymbolsFigure 1-4 Facility Symbol Figure 1-5 Components in the RTR Environment 1-8 Introduction Nontransactional messaging Transaction ID Transaction ControllerFigure 1-7 Three-Tier Client/Server Environment Figure 1-6 Two-Tier Client/Server Environment1-10 Introduction Figure 1-8 Browser Applet ConﬁgurationWeb Server Process RTR Client Application Figure 1-10 RTR Deployed on Two Nodes Figure 1-9 RTR with Browser, Single Node, and Database1-12 Introduction Figure 1-11 RTR Deployed on Three NodesTransactional shadowing RTR Journal Figure 1-12 Standby Server ConﬁgurationFigure 1-13 Transactional Shadowing Conﬁguration RTR Server Types Concurrent servers Callout servers Transactional shadow server Figure 1-15 Standby ServersFigure 1-16 Shadow Servers Figure 1-17 Concurrent Servers Figure 1-18 A Callout Server User Accounts FacilityFigure 1-19 Bank Partitioning Example TR A partition can also have multiple standby servers Router RTR Networking CapabilitiesPage The Three-Layer Model Architectural ConceptsZKO-GS011-99AI Figure 2-1 The Three Layer ModelFlexibility and Growth RTR Facilities Bridge the GapBroadcasts Flexibility and Growth Transaction IntegrityObject-Oriented Programming The Partitioned Data ModelZKO-GS012-99AI Figure 2-2 Partitioned Data ModelTable 2-1 Functional and Object-Oriented Programming Compared ObjectsExample 2-1 Objects-Deﬁned Sample Messages Class RelationshipsPolymorphism Object Implementation Beneﬁts Programmers Reference Manual and the RTR Application Design Guide XA SupportServers Reliability FeaturesRecovery Scenarios Failover and RecoveryRecovery Router FailoverBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station RTR SHOW JOURNAL $ RTRRTR CREATE FACILITY DESIGN/ALLROLES=NODEA RTR SHOW FACILITYRTR show transaction RTR RTRRECEIVEMESSAGE/CHAN=SRTR RTRRECEIVEMESSAGE/TIME=0 $ RTR RTR START RTRRTR RTRSTARTTX/CHAN=C RTR RTRRECEIVEMESSAGE/CHANNEL=C/timenters commands at the server RTR show transactionBrowser Application Programming InterfacesInterface Object-OrientedFigure 4-1 RTR Browser Interface Application Programming InterfacesExample of object creation in an RTR server program RTR Cinterface, 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 System Management Environment The RTR EnvironmentHandles all transactions and recovery Page Management Monitoring RTRTransaction RTR Monitor pictures or the RTR Monitor let you view theManagement The RTR Runtime EnvironmentPartition Figure 5-2 RTR Runtime Environment Whats Next? RTR Installation GuideRTR Release Notes RTR Migration Guide ifPage ACID Glossaryapplet applicationbroadcast branchcallout server channelconcurrent server common classesdata marshalling data objectendian frontend message process primaryproperties property classesrouter rollbackRTR conﬁguration RTR environmentstandby shadowtransaction transaction controllertransactional shadowing two-phase committransactional message Index-1 IndexIndex-2