Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router Application Programming Interfaces, Browser, Object-Oriented

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 55

RTR Management Station

RTR> RTR_RECEIVE_MESSAGE

%RTR-S-OK, normal successful completion channel name: S

.

.

.

msgtype: rtr_mt_accepted

.

.

.

RTR> STOP RTR

Browser	With the RTR browser interface, your management station has
Interface	a network-browser-like display from which you can view RTR
	status and issue RTR certain commands with a point-and-click
	operation, rather than by entering commands. Figure 4–1 shows
	one screen of the browser interface as you may view it from your
	management station running Microsoft Internet Explorer. Not
	all RTR CLI commands are accessible to the browser interface,
	only the most commonly used commands are available with the
	RTR browser. The browser interface provides help (for forms
	input) and logging windows, and navigational aids between
	displays.

Application Programming Interfaces

	You write application programs and management applications
	with the RTR application programming interfaces.
RTR	You can use the object-oriented programming interface to
Object-Oriented	write C++ applications that use RTR. For more information on
Programming	the object-oriented programming interface, see the RTR C++
Interface	Foundation Classes manual and the RTR Application Design
	Guide.

RTR Interfaces 4–7

Image 55

Compaq Reliable Transaction Router Application Programming Interfaces, Browser, Object-Oriented, Rtr Rtrreceivemessage

Contents

Compaq Computer Corporation Houston, Texas Revision/Update Information This is a new manualReliable Transaction Router Getting Started January2001 Compaq Computer Corporation This document was prepared using VAX DOCUMENT, VersionUNIX and The Open Group are trademarks of The Open Group Architectural Concepts IntroductionContents Glossary Index Examples 3 Reliability Features4 RTR Interfaces 5 The RTR EnvironmentTables FiguresPage Purpose of this Document PrefaceDocument Structure For all users RTR CommandsRouter Installation Related DocumentationNew term Reading PathReaders Comments ConventionsIf V2 to Figure 1 RTR Reading PathSystem Manager Application ProgrammerReliable Transaction Router IntroductionRTR Continuous Computing Concepts RTR Terminology Figure 1-1 Client Symbol Channel RTR conﬁguration Roles Figure 1-2 Server SymbolFigure 1-4 Facility Symbol Figure 1-3 Roles SymbolsFE TR 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 EnvironmentWeb Server Process RTR Client Application Figure 1-8 Browser Applet Conﬁguration1-10 Introduction 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 ModelBroadcasts RTR Facilities Bridge the GapFlexibility and Growth 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 FeaturesRouter Failover Failover and RecoveryRecovery Scenarios RecoveryBackend Recovery Router Recovery Frontend Recovery Page RTR Interfaces RTR Management Station RTR Management Station RTR SHOW FACILITY $ RTRRTR SHOW JOURNAL RTR CREATE FACILITY DESIGN/ALLROLES=NODEA$ RTR RTR START RTR RTR RTRRECEIVEMESSAGE/CHAN=SRTR show transaction RTR RTRRECEIVEMESSAGE/TIME=0RTR show transaction RTR RTRRECEIVEMESSAGE/CHANNEL=C/timRTR RTRSTARTTX/CHAN=C enters commands at the serverObject-Oriented Application Programming InterfacesBrowser InterfaceFigure 4-1 RTR Browser Interface Application Programming InterfacesManual and the RTR Application Design Guide RTR CExample of object creation in an RTR server program interface, see the RTR C Application Programmers ReferenceExample of an open channel call in an RTR client program The RTR System Management Environment The RTR EnvironmentHandles all transactions and recovery Page RTR Monitor pictures or the RTR Monitor let you view the Monitoring RTRManagement TransactionPartition The RTR Runtime EnvironmentManagement Figure 5-2 RTR Runtime Environment RTR Migration Guide if RTR Installation GuideWhats Next? RTR Release NotesPage application GlossaryACID appletchannel branchbroadcast callout serverdata object common classesconcurrent server data marshallingendian frontend message property classes primaryprocess propertiesRTR environment rollbackrouter RTR conﬁgurationtransaction controller shadowstandby transactiontransactional message two-phase committransactional shadowing Index-1 IndexIndex-2