Manuals / Compaq / Computer Equipment / Network Router

Compaq Reliable Transaction Router Objects, 1 Functional and Object-Oriented Programming Compared

Models: Reliable Transaction Router

1 78

Download 78 pages 48.87 Kb

Page 41

Table 2–1 Functional and Object-Oriented Programming Compared

Object-Oriented Programming

Table 2–1 Functional and Object-Oriented Programming Compared

Functional Programming

Object-Oriented Programming

A program consists of data structures and algorithms.

The basic programming unit is the function, that when run, implements an algorithm.

Functions operate on elemental data types or data structures.

An application's architecture consists of a hierarchy of functions and sub-functions.

A program consists of a team of cooperating objects.

The basic programming unit is the class, that when instantiated, implements an object.

Objects communicate by sending messages.

An applications architecture consists of objects that model entities of the problem domain. Objects' relationships can vary.

Objects	In the object-oriented environment, a program or application
	is a grouping of cooperating objects. The basic programming
	unit is the class. Instantiating, or declaring an instance of,
	a class implements an object. RTR provides object-oriented
	programming capabilities with the C++ API, described in the
	C++ Foundation Classes manual. Objects are instances of a
	class. In a transaction class, each transaction is an object. An
	object is an instantiated (declared) class. Its state and behavior
	are determined by the attributes and methods deﬁned in the
	class. An object or class is deﬁned by its:
	•	State (attributes)
	•	Behavior (methods)
	• Identity (name at instantiation)

The name given at object declaration is its identity. In Example 2–1, the two dog objects King and Fiﬁ are instances of Dog. The Dog class is declared in a header (Dog.h) ﬁle and implemented in a .cpp ﬁle.

Architectural Concepts 2–7

Image 41

Compaq Reliable Transaction Router manual Objects, 1 Functional and Object-Oriented Programming Compared

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