Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router manual RTR Facilities Bridge the Gap, Broadcasts

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 37

RTR Facilities Bridge the Gap

RTR Facilities Bridge the Gap

RTR Facilities Bridge the Gap

Many applications can use RTR at the same time without interfering with one another. This is achieved by deﬁning a separate facility for each application.

When an application calls the rtr_open_channel( ) routine to declare a channel as a client or server, it speciﬁes the name of the facility it will use.

See the RTR System Manager's Manual for information on how to deﬁne facilities.

Broadcasts

Sometimes an application has a requirement to send unsolicited messages to multiple recipients.

An example of such an application is a commodity trading system, where the clients submit orders and also need to be informed of the latest price changes.

The RTR broadcast capability meets this requirement.

Recipients subscribe to a class of broadcasts; a sender broadcasts a message in this class, all interested recipients receive the message.

RTR permits clients to broadcast messages to one or more servers, or servers to broadcast to one or more clients. If a server needs to broadcast a message to another server, it must open a second channel as a client.

Flexibility and Growth

RTR allows you to cope easily with changes in:

•Network demand

Architectural Concepts 2–3

Image 37

Compaq Reliable Transaction Router manual RTR Facilities Bridge the Gap, Broadcasts, Flexibility and Growth

Contents

Reliable Transaction Router Getting Started Revision/Update Information This is a new manualJanuary 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 4 RTR Interfaces 3 Reliability Features5 The RTR Environment Glossary Index ExamplesTables FiguresPage Purpose of this Document PrefaceDocument Structure 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 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 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 thePartition The RTR Runtime EnvironmentManagement 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 message two-phase committransactional shadowing Index-1 IndexIndex-2