[go: up one dir, main page]

WO1999039269A1 - Systeme et procede permettant de traiter des transactions dans un environnement contenant un certain nombre d'applications objets - Google Patents

Systeme et procede permettant de traiter des transactions dans un environnement contenant un certain nombre d'applications objets Download PDF

Info

Publication number
WO1999039269A1
WO1999039269A1 PCT/US1998/001309 US9801309W WO9939269A1 WO 1999039269 A1 WO1999039269 A1 WO 1999039269A1 US 9801309 W US9801309 W US 9801309W WO 9939269 A1 WO9939269 A1 WO 9939269A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
application
name
transaction processor
transactions
Prior art date
Application number
PCT/US1998/001309
Other languages
English (en)
Inventor
Mark Phillips
Michael Blevins
Original Assignee
Insession, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Insession, Inc. filed Critical Insession, Inc.
Priority to PCT/US1998/001309 priority Critical patent/WO1999039269A1/fr
Priority to AU60380/98A priority patent/AU6038098A/en
Publication of WO1999039269A1 publication Critical patent/WO1999039269A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/466—Transaction processing

Definitions

  • the present invention relates to transaction processing in a heterogeneous transaction processing system, and more specifically, to a system, method and article of manufacture for providing interoperability between different transaction processing systems.
  • ORB Object Request Brokers
  • OOP Object oriented programming
  • OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program.
  • An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task.
  • OOP therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation.
  • OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture.
  • a component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each others capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture. It is worthwhile to differentiate between an object and a class of objects at this point.
  • An object is a single instance of the class of objects, which is often just called a class.
  • a class of objects can be viewed as a blueprint, from which many objects can be formed.
  • Object-Oriented Programming allows the programmer to create an object that is a part of another object. For example, the object 3 -
  • a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects.
  • OOP also allows creation of an object that "depends from” another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition.
  • a ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic.
  • the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it.
  • the object representing the ceramic piston engine "depends from" the object representing the piston engine. The relationship between these objects is called inheritance.
  • the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class.
  • the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines have different characteristics, but may 4 -
  • composition-relationship With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, our logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows:
  • ⁇ Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit- design program, countries in an economics model, or aircraft in an air- traffic-control system.
  • ⁇ Objects can represent elements of the computer-user environment such as windows, menus or graphics objects.
  • An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities.
  • An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane.
  • OOP allows the software developer to design - 5
  • a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future.
  • OOP enables software developers to build objects out of other, previously built, objects. This process closely resembles complex machinery being built out of assemblies and sub-assemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increased speed of its development.
  • ⁇ Objects and their corresponding classes break down complex programming problems into many smaller, simpler problems.
  • ⁇ Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures.
  • Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch.
  • Polymorphism and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways.
  • Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them.
  • ⁇ Libraries of reusable classes are useful in many situations, but they also have some limitations. For example: ⁇ Complexity. In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes.
  • ⁇ Flow of control A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library) . The programmer has to decide which functions to call at what times for which kinds of objects.
  • ⁇ Duplication of effort Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way.
  • Class libraries are very flexible. As programs grow more complex, more programmers are forced to adopt basic solutions to basic problems over and over again.
  • a relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers. - 8
  • Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others.
  • the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way.
  • Application frameworks reduce the total amount of code that a programmer has to write from scratch.
  • the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit.
  • the framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure).
  • a programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems. 10
  • a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain. It typically includes objects that provide default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times.
  • default behavior e.g., for menus and windows
  • Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program.
  • a framework provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides.
  • ⁇ Call versus override With a class library, the code the programmer instantiates objects and calls their member functions. It's possible to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework.
  • the framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together.
  • ⁇ Implementation versus design With class libraries, programmers - 11
  • a framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems.
  • a preferred embodiment of the invention utilizes an object-oriented paradigm that is seen by customers and vendors to provide significantly cheaper application development, in terms of resources required and re-usability of functions and code.
  • TP Transaction Processing
  • CICS Customer Information Control System
  • IMS Information Management System
  • Other key TP monitors are Pathway from Tandem and Tuxedo from BEA systems. TP monitoring systems are of increasing importance to major banks and airlines.
  • OMG Object Management Group
  • CORBA Common Object Request Broker Architecture
  • ORB Object Request Broker
  • OTS CORBA Object Transaction Services
  • OLE TP/ Network TP will be used to deploy distributed applications, may eventually replace today's special purpose TP monitors.
  • CORBA Common Object Request Broker Architecture
  • OMG Object Management Group
  • OMG Object Management Group
  • CORBA provides the mechanisms by which objects transparently make requests and receive responses, as defined by OMG's ORB.
  • the CORBA ORB provides interoperability between applications built in (possibly) different languages, running on (possibly) different machines in heterogeneous distributed environments. It is the cornerstone of OMG's CORBA architecture.
  • a computer implemented universal, user interface to a plurality of heterogeneous transaction processing systems which allows an application program to access transactions and data residing in an existing transaction processing system is disclosed.
  • the system utilizes a communication link between the application and a transaction processor interoperability component. Then, the system determines which of the one or more transaction processors will process transactions for the application and establishes a communication link between the transaction processor interoperability component and the transaction processor that will process transactions for the application. Then, as the application transmits a transaction from the application to the transaction processor interoperability component, the transaction is formatted by the transaction processor interoperability component for compatability with the transaction processor that will process transactions for the application, and finally transmitting the formatted transaction to the transaction processor that will process transactions for the application.
  • the implied transaction environment is determined by the attributes of the service name in the service resolver database. Implied transactions are started with the first invocation of the transaction processor interoperability component. Implied transactions are terminated at the appropriate point for request response and conversational interaction.
  • Figure 1 illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment
  • Figure 2A illustrates the three major architectural components in accordance with a preferred embodiment
  • FIGS. 2B & 2C illustrate block diagram of a system architecture in accordance with a preferred embodiment
  • Figure 3 is an object model system diagram in accordance with a preferred embodiment
  • Figure 4 is an illustration of a diagram for an application starting a transaction in accordance with a preferred embodiment
  • Figure 5 is an illustration of an application setting a default context in accordance with a preferred embodiment
  • Figure 6 is an illustration of an application invoking a service in accordance with a preferred embodiment
  • Figure 7 is an illustration of an application continuing a service conversation with a TP in accordance with a preferred embodiment
  • Figure 8 illustrates an application commit on a transaction in accordance with a preferred embodiment
  • Figure 9 illustrates a scenario where the naming context is known in - 15 -
  • Figure 10 illustrates a case where the naming context is unknown in accordance with a preferred embodiment
  • Figure 11 is a Booch diagram of an object model of TPInterop in accordance with a preferred embodiment
  • Figure 12 is a Booch diagram of externalization processing in accordance with a preferred embodiment
  • Figure 13 illustrates a simple interaction for an application object using a request object to help the TPXXX object build a request buffer, invoke the request and send back the response;
  • Figure 14 is a Booch diagram illustrating the relationship between objects in accordance with a preferred embodiment
  • Figure 15 is a Booch diagram illustrating the Interaction processing in accordance with a preferred embodiment
  • Figure 16 is a Booch diagram setting forth the architecture of the TP monitor in accordance with a preferred embodiment
  • FIGS 17 and 18 set forth some details of CICS processing in accordance with a preferred embodiment
  • FIGS. 19 and 20 set forth some details of IMS processing in accordance with a preferred embodiment
  • Figures 21 and 22 set forth some details of Pathway processing in accordance with a preferred embodiment
  • Figure 23 illustrates a Tuxedo request / response transactions within an explicit transaction in accordance with a preferred embodiment
  • Figure 24 illustrates a Tuxedo conversational transaction within an implicit transaction in accordance with a preferred embodiment.
  • a preferred embodiment of a system in accordance with the present invention is preferably practiced in the context of a personal computer such as the IBM PS/2, Apple Macintosh computer or an UNIX based workstation.
  • a representative hardware environment is depicted in Figure 1, which illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment having a central processing unit 10, such as a microprocessor, and a number of other units interconnected via a system bus 12.
  • the workstation shown in Figure 1 includes a Random Access Memory (RAM) 14, Read Only Memory (ROM) 16, an I/O adapter 18 for connecting peripheral devices such as disk storage units 20 to the bus 12, a user interface adapter 22 for connecting a keyboard 24, a mouse 26, a speaker 28, a microphone 32, and/ or other user interface devices such as a touch screen (not shown) to the bus 12, communication adapter 34 for connecting the workstation to a communication network (e.g., a data - 17
  • RAM Random Access Memory
  • ROM Read Only Memory
  • I/O adapter 18 for connecting peripheral devices such as disk storage units 20 to the bus 12
  • a user interface adapter 22 for connecting a keyboard 24, a mouse 26, a speaker 28, a microphone 32, and/ or other user interface devices such as a touch screen (not shown) to the bus 12
  • communication adapter 34 for connecting the workstation to a communication network (e.g., a data - 17
  • the workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/ 95 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system.
  • OS Microsoft Windows NT or Windows/ 95 Operating System
  • IBM OS/2 operating system the IBM OS/2 operating system
  • MAC OS the MAC OS
  • UNIX operating system the Microsoft Windows NT or Windows/ 95 Operating System
  • Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.
  • FIG. 2 A illustrates the three major architectural components in accordance with a preferred embodiment.
  • a client 200 consists of C, C++, Java and Smalltalk applications which converse with an Object Request Broker (ORB) or an Object Transaction System (OTS) to prepare transactions to the Gateway 201.
  • the Gateway 201 provides the interoperability functioning to interface with any of a number of TP monitors on the Server 202, such as CICS, IMS, Pathway and Tuxedo.
  • FIGS. 2B and 2C illustrate block diagrams of a system architecture in accordance with a preferred embodiment.
  • the application programmer is provided with a single model for accessing existing TP monitor services and data.
  • the model has a gateway side 215 and a server side 205.
  • the server side contains each of the TP servers for CICS 270, IMS 280, Tuxedo 290 and Pathway 295.
  • TP inter-operability component Underlying the TP inter-operability component are three TP monitor specific components (concrete implementations of TP monitor independent interfaces) LU 6.2 230, Tuxedo 240 and the Pathway 250 component.
  • the LU6.2 230 component is used for the CICS and IMS interaction
  • the Tuxedo 240 component is used to support both native 18 -
  • TP interoperability / externalization component 220 to the appropriate TP component (230, 240 or 250) based on application requirements.
  • FIG. 3 is an object model system diagram in accordance with a preferred embodiment.
  • the OMG naming service 300 is the principal means for objects to locate other objects.
  • the names given to the objects should be easily recognizable and readable within the problem domain of the application.
  • the naming service will map these user-defined "names" to object references.
  • the name-to- object association is called a "name binding”.
  • a "naming context" is an object that contains a set of "name bindings" in which each name is unique. Every object has a unique object ID or reference.
  • One or more names can be associated with the same object reference at the same time, however there is no requirement for all objects to be named.
  • the admin tool 305 is used to provide an interface between a human administrator and programmatic interfaces offered by internal classes. Processing comprises the following basic steps. First, get a name context from the user, then present the user with either an existing or default set of property values for modification, and finally store the name context and set of property values.
  • the property list classes 308 encapsulate property list handling for 19 -
  • TPInterop::TPmgr 320 executes on the gateway and accepts a request along with a description of the destination from front-end clients and delegates them to a specific interoperable object 340 (370)(e.g. TPCICS::CallContext 385, TPIMS: :CallContext 390, TPTux: :CallContext 380 and
  • TPPW::CallContext 395) according to the destination. Since the whole invocation is carried out in a distributed environment, parameters are passed via Extern: :Streamable objects 350.
  • the TPTX class category 360 supports a "mini" transaction interface, useful until OTS can be used.
  • a TPxxx::callMgr inherits from TxRcvr to get the transaction commit signals, and registers itself with the TxXMgr 340 using its factory name as the "id".
  • Applications 330 communicate to the various system objects via transactions.
  • Figure 4 is an illustration of a diagram for an application starting a transaction in accordance with a preferred embodiment.
  • an application request 410 is transmitted to the TP manager 410.
  • FIG. 5 is an illustration of an application setting a default context in accordance with a preferred embodiment. Processing commences when an application 500 sends a setDefaultContext transaction to the 20 -
  • FIG. 6 is an illustration of an application invoking a service in accordance with a preferred embodiment.
  • Processing commences when an application 601 transmits a write request to a TP.
  • the request generates an invoke transaction 602 to the Tpinterop which results in a resolution of the name 603.
  • the resolved name is utilized in another invoke 604 to register the name via the call manager to the TP transmit manager 605.
  • the call manager transmits the registered name 606 which results in a creation operation 607 for the particular transaction.
  • the call manager for the particular TP allocates a buffer 608 and then sets the buffer in preparation for the write operation 609.
  • the call manager externalizes the write operation 610 in preparation for the actual write operation 611 performed by the external object stream IO processor.
  • the call manager must get the buffer 612 that the external object has streamed back from the target TP.
  • the call manager performs a do operation 613 and sets the buffer 614 in preparation for internalizing 615 the information.
  • a read is requested from the application 616 and the information is read 617.
  • FIG. 7 is an illustration of an application continuing a service conversation with a TP in accordance with a preferred embodiment.
  • the invoke on the TPInterop: :TPMgr, and the subsequent invoke on the TPxxx::callMgr may return a 21
  • CallContext object For the purposes of this scenario, the invoke did return a CallContext object and the application is now invoking an operation on it 702.
  • the invoke operation 702 was initiated in response to the write request 701 and initially must create an object for streaming the information externally 703. Then a buffer must be allocated 704 and the buffer must be set 705 for the upcoming externalize 706 and write 707 operations.
  • To read the reply 713 first the buffer length must be obtained 708 and a d operation 709 must be performed to set the buffer 710 and internalize 711 the results. Then, the read 712 operation can transpire resulting in the reply being read 713.
  • FIG. 8 illustrates an application commit on a transaction in accordance with a preferred embodiment. Processing commences with a commit operation 801 from the application to the transaction manager. This action results in the TP call manager preparing 802 utilizing a prepare operation 803. Then, the TP manager commits 804 and the commit operation is performed 805.
  • the TPTX class category supports a "mini" transaction interface, useful until OTS can be used.
  • a TPxxx::callMgr inherits from TxRcvr to get the transaction commit signals, and registers itself with the TxXMgr using its factory name as the "id".
  • Source code for the module is provided below for detailed logic. 22 -
  • void rollback() void rollback_only(); char* get_transaction_name(); unsigned isTransaction(); void setLogData(const char* rcvrld, char* logData);
  • Admin is used to bridge an interface between a human administrator and programmatic interfaces offered by internal classes.
  • the general algorithm is to do the following:
  • FIG. 9 illustrates a scenario where the naming context is known in accordance with a preferred embodiment.
  • An initial transaction querying for the name context 901 triggers a get property transaction from the admin tool to the Service resolver 902 which returns the "known" property. Then the admin tool sends out another transaction to get the factory 903 from the interoperability tool. The values are returned from the admin tool to the user 904. Then, a check of the values is initiated by the admin tool 905 and the properties are set in the service resolver 906. 28
  • Figure 10 illustrates a case where the naming context is unknown in accordance with a preferred embodiment.
  • An initial transaction querying for the name context 1011 triggers a get property transaction from the admin tool to the Service resolver 1002 which returns a "unknown" property.
  • the user is queried for the factory type 1003.
  • the admin tool sends out another transaction using the factory 1003 type to the interoperability tool to get the factory 1004 and to get the defaults from the TP manager 1005.
  • the values are returned from the admin tool to the user 1006 to determine if they meet with user approval.
  • a check of the values is initiated by the admin tool 1007 and the properties are set in the service resolver 1008.
  • the property list classes encapsulate property list handling for various concrete TPInterop classes.
  • a valueList consists of
  • HelpListltemQ possibleNalues( 5 ) ⁇ ;
  • HelpListItem( const char *sh ) shortHelp( sh ), possibleNalues( 5 ) ⁇ ; RWCString shortHelp;
  • CallMgrHelpO ⁇ ; virtual -CallMgrHelpO ⁇ ; virtual const ISPropListP:: ValueList* getDefaultValueList() const 0;
  • offendingValue is the name of the property that caused the error. / / offendingValue may be NULL to stifle return value
  • CallMgrHelp should be in a file named xxxhelp.cpp, / / with no // references to external libs or DLLs.
  • the object should be created with // the / / following method.
  • TuxCallMgrProperties : ⁇ TuxCallMgrProperties() ⁇
  • const ISPropListP : ValueList* TuxCallMgrProperties: :getDefaultValueList() const
  • TuxCallMgrProperties :verifyBufferSize( const char *propValue, const char *propName )
  • TP Interoperability TPInterop::TPmgr executes on the gateway and accepts a request along with a description of the destination from front-end clients and delegates them to a specific interoperable object (e.g. TPCICS:: CallContext, TPIMS:: CallContext, TPTux:: CallContext and TPPW:: CallContext) according to the destination. Since the whole invocation is carried out in a distributed environment, parameters are passed via Extern: :Streamable objects. Externalization referred in this section is based on OMG's Object Externalization Service Specification.
  • TPInterop:: CallContext is an abstract base class. All subclasses have to override invoke method, and the method invokeObject on TPInterop: :CallMgr 1102.
  • TPInterop: :TPmgr 1104 is the interface exported to the application. Since registerCallMgr is specific for TPInterop "CallMgr,
  • TPInterop: :TPmgr_Ex is used internally. There is only one instance of TPInterop: :TPmgr 1104 per process. Each TPInterop:: CallMgr object within the process registers itself with TPInterop: :TPmgr object. - 39
  • RegisterCallMgr and unregisterCallMgr are the facilities provided by the TPInterop: :TPmgr 1104 object.
  • An externalization service is a standard service for streaming objects to and from transport streams, persistent storage, etc. It consists of two main pieces: an abstract Extern: :Streamable class 1112 which an application object inherits from, and an abstract Extern: :StreamIO class 1110 which the externalization service provides an implementation for. Externalize is called by a TPIterop:TPConversation class 1106 which passes an Extern: :StreamIO 1108 subclass object, and the object 1108 is expected to write its state out using the Extern::StreamIO::writeXxx calls 1110. When internalize is called, the object is expected to read its state from the Extern: :Streamable object 1112 using the Extern::StreamIO::readXxx calls.
  • the Extern: :StreamIO class is similar in function to a C++ iostream class, but uses explicit method calls to read and write data types rather than use operator overloading.
  • cxt is not NULL, it may be set to a returned CallContext / / whose memory is owned by the caller. If cxt is not NULL and / / if no CallContext is returned, *ctx will be set to NULL.
  • a preferred embodiment provides the application developer with two transaction models: explicit model and implicit model.
  • the syntax of the code using explicit model is similarly to the following code segment: ⁇ 42
  • tptxObject.Begin_Transaction() ; cicsObj ect. go (request 1 , response 1 ) ; cicsObject.go(request2, response2); tptxObject.End_Transaction();
  • invocation of invoke method starts and commits the transaction.
  • the syntax of the code looks as follows: tpinteropMgr.go("debitl", requestl, responsel); tpinteropMgr.go("debit2", request2, response2);
  • This section is to identify the data conversion required for a specific TP component, running on the gateway platform and the server platform on which the TP server is running.
  • ASCII and EBCDIC formats relates to the way character data is ⁇ 43
  • the IBM System/ 390 platform is the only platform that uses the EBCDIC data format.
  • Gateway Server Endian Data Representation
  • Gateway Server Endian Data Representation
  • Tuxedo workstation service performs internal little and big 44 -
  • Gateway Server Endian Data Representation Platform Platform Conversion Conversion
  • the OMG Externalization Service is a standard service for streaming objects to and from transport streams, persistent storage, etc. It consists of two main pieces an abstract Extern: :Streamable class which an application object inherits from, and an abstract Extern: :StreamIO class which the externalization service provides an implementation for.
  • the Extern: :Streamable class provides to methods: externalizeToStream, and internalizeToStream.
  • externalize When externalize is called, an Extern: :StreamIO subclass object is passed to the application object, and object is expected to write its state out using the Extern: :StreamIO::writeXxx calls.
  • internalize When internalize is called, the object is expected to read its state from the Extern: :StreamIO subclass object using the Extern: :StreamIO::readXxx calls.
  • the Extern: :StreamIO class is similar in function to a C++ iostream class, but uses explicit method calls to read and write data types rather ⁇ 45 -
  • the externalization service acts as a bridge between the TP monitor communication buffer and the ORB world.
  • the application object creates a request and reply object.
  • the request object supports the externalize function to create a request buffer for the TP link object, and the reply object supports the internalize function to read the reply buffer.
  • the request and reply object act as a bridge between the ORB world and the TP monitor world - the TP monitor buffers are never seen, but the request and reply objects know the exact order of the data in the buffer.
  • StdStreamlO's data format is OMG Object Externalization Specification compliant.
  • TPStreamlO's data format is different. It does not have data type and data length fields.
  • TPStreamlO is the class used for externalization and internalization at Stage 1 A.
  • TPStreamlO StreamlO ⁇ void setOutputBuffer(in bufPtr aBuffer, in long length); long getOutputBufferLength(); long getDataLength();
  • TPStreamlO provides methods to set up the buffer pointer, for the reason that Tuxedo needs to use buffer allocated by its own memory allocation APIs.
  • Gateway platform and Server platform might be different, and different platforms might have different scheme for data representation
  • program running on Gateway need converting the data format to be compliant with that of the server platform.
  • the following tables show what operations need to be performed for data conversion based upon different Gateway and Server platform configurations.
  • Figure 12 is a Booch diagram of externalization processing in accordance with a preferred embodiment.
  • Every Extern: :TPStreamIO 1220 object has two internal flags of bool types; they are flagLtoB and flagAtoE.
  • an Extern: :TPStreamIOFactory 1270 is asked to create an Extern: :TPStreamIO 1230, it must be given the information about Gateway platform and Server platform. According to the message, it looks up the table and sets the flags of the Extern: :TPStreamIO 1230 correspondingly.
  • the Extern: :TPStreamIO 1230 object is asked to write or read, it will check those flags also.
  • the Extern: :TPStreamIO 1220 object has two internal flags of bool types; they are flagLtoB and flagAtoE.
  • :TPStreamIOFactory 1270 is asked to create an Extern: :TPStreamIO 1230, it must be given the information about Gateway platform and Server platform. According to the message, it looks up the table and
  • :TPStreamIOFactory 1270 object is a singleton object.
  • Figure 13 illustrates a simple interaction for an application object using a request object to help the TPXXX object build a request buffer, invoke the request and send back the response.
  • the OMG naming service is the principal means for objects to locate other objects.
  • the names given to the objects should be easily recognizable and readable within the problem domain of the application.
  • the naming service will map these user-defined "names" to object references.
  • the name-to-object association is called a "name binding".
  • a "naming context" is an object that contains a set of "name bindings" in which each name is unique. Every object has a unique object ID or reference. One or more names can be associated with the same object reference at the same time, however there is no requirement for all objects to be named.
  • a naming context is an object , it too can be bound to a name in a naming context. Binding naming contexts to other naming • 49 -
  • the "naming graph" is a directed graph or tree where the nodes are naming contexts and the leaves are name bindings to non-naming context objects . Given a context in a naming graph a sequence of names can reference an object.
  • a " name component” is a structure with two attributes, an identifier which includes the object's name string, and a kind which includes a string that is a description of the objects name, ie. file type etc.
  • a name with a single "name component” is called a "simple name”
  • a name with “multiple components” is called a "compound name.”
  • Each component except the last is used to name a context; the last component denotes the bound object.
  • NameComponent The kind attribute for the Name component will be assumed to be NULL and will be omitted from the NameComponent definition.
  • Compound names will simply be defined as a unique string similar to a directory name in common PC files systems, with a "/" character delimiting each substring representing the NameComponent within the compound name. Names are specified without the trailing "/" character, the process of binding a name to a context will be equivalent to the operation of adding the "/" character to the string.
  • the SvcResoIve class provides a naming service and server for names and objects associated with the TPInterop:: TPMgr. It maintains naming contexts and name-object associations for TPInterop: : CallMgr objects and subclasses for this release.
  • Figure 14 is a Booch diagram illustrating the relationship between the TPInterop: :TPMgr 1400, TPInterop: :CallMgr 1410, TPInterop:: CallContext 1420 classes and the SvcResoIve:: Resolver 1420 naming service components.
  • IDL Classes module ISNaming ⁇ interface Name ⁇ attribute string name;
  • SvcResoIve :ObjectRef resolve( in Name name) ; void unbind(in Name name);
  • NamingContext bindNewContext(in Name name) ; void setPropertyList(in Name name, in propList: : valueList propstring); void remove Property List(in Name name, in propList:: valueList propstring); propList: : valueList getPropertyList(in Name name);
  • NamingContext get_context(in NamingContext root_cxt , in string compound_name); void buildGraph(in NamingContext root_cxt , in string compound_name) ; void de story Graph (in NamingContext root_cxt, in string compound_name) ; void bindGraph(in NamingContext cxt, in string compound_name , in SvcResoIve: :ObjectRef ref); - 52
  • ISNaming NamingContext locateGlobalNamingContext() ; void setGlobalNamingContext(in string cxt); void addTPServiceDestination(in string name, in ObjectRef Factory, in propList: : valueList pi); void deleteTPServiceDestination(in string name); void changeTPServiceDestination(in string name, in ObjectRef Factory, in propList:: valueList pi);
  • TPTux :TPCallMgr* tptux
  • TPInterop : CallMgr* tpcallmgr
  • TPInterop :TPMgr* tpMgr
  • aPropList* pi new propList(); pl->addName("requestType”, “request/ response”); pl->addName("bufferType", “VIEW”); pl->addName("startTx", "YES”);
  • aPropList* p2 new propList() ; p2->addName("trancode", "SAV002TR ");
  • NamingContext* cxt getGlobalNamingContext; graph. bindGraph(cxt, name, ref); cxt->bindWithPropertyList(name, ref , pi); - 55 -
  • TPInterop :TPMgr::invoke( const char* destination, ... ) ⁇
  • FIG. 15 is a Booch diagram illustrating the Interaction processing in accordance with a preferred embodiment.
  • the TPInterop: :TPMgr creates the SvcResoIve: :Resolver object, (during its initialization or startup), and calls the SvcResoIve:: Resolver method "setGlobalNamingContext"
  • the Application is activated, and calls the TPInterop: :TPMgr method "invoke” with the following parameters as shown at 1501.
  • Name representing the TPInterop :: CallMgr application streamable input object, application streamable output object.
  • the TPInterop: :TPMgr get the input name representing the 56
  • TPInterop CallMgr object as shown at 1502.
  • the TPInterop: :TPMgr calls resolveTPServiceDestination on the SvcResoIve:: Resolver object with the name representing the transaction as an input parameter.
  • the method returns an object reference, and the associated property list as shown at 1503.
  • the TPInterop: :TPMgr calls the getCallMgr method with the object reference obtained in 3) to locate the appropriate TPInterop:: CallMgr object as shown at 1504.
  • the property list is used as input for the invoke method on the TPInterop: :TPCallMgr object as shown at 1505.
  • This section describes a typical implementation of a set of TPxxx classes, such as TUXEDO, CICS, etc.
  • Figure 16 is a Booch diagram setting forth the architecture of the TP monitor in accordance with a preferred embodiment.
  • FIGS 17 and 18 set forth some details of CICS processing in 57
  • this component is to provide connectivity between the TP inter-operability module and a CICS system running on another computer. Connectivity to CICS is achieved through the CICS LU 6.2 service and the CICS user transaction is invoked via the CICS Program Link interface.
  • the LU 6.2 service allows a client LU 6.2 application (written to the basic LU 6.2 level or using the CPIC interface) to connect to a CICS system running on a server through the CICS LU 6.2 service.
  • a CICS LU 6.2 transaction will be provided by this project to inter-operate with the CICS LU 6.2 service and the client LU 6.2 application.
  • the CICS LU 6.2 transaction will convert the data received from an LU 6.2 client and then perform a CICS Program Link command to invoke the appropriate CICS user application.
  • processing commences at 1701 and immediately passes to 1702 to invoke a transaction and connect to a CICS LU 6.2 service.
  • a register operation occurs and a get request 1704 to allocate a StreamlO, setbuffer, externalize the transaction and obtain the buffer length.
  • a LU 6.2 allocate operation is performed and at 1706 a send operation is performed.
  • a put reply is performed to allocate StreamlO, internalize the transaction and obtain the buffer length of the transaction.
  • a second invoke operation 1708 is performed in which the first operation is a register operation 1709 which will fail since the transaction is already registered.
  • a get request 1710 is performed which initiates a send/recieve 1711 transaction which invokes a put reply 1712 and ultimately an end transaction 1713 which invokes a prepare 1714 transaction and sends a prepare message 1715 which results in a commit 1716 and a 58
  • processing commences at 1803 where an invoke operation occurs which returns a context object. Then, at 1804 a register operation is performed which fails if there is no transaction. At 1805, a get request is sent and at 1806 an LU 6.2 allocate operation is performed which is followed by an LU 6.2 send/recieve 1807 and a put reply 1808 is used to transmit the transaction to the CICS system. At 1809 another invoke operation is performed and a get request 1810 is utilized to initiate a send/receive transaction 1811 which prepares a message to send 1812 and invokes a send syncpoint message 1801 which results in an LU 6.2 deallocate operation 1802 and a put reply 1813.
  • the CICS Program Link interface requires a program name which is the name of the CICS user application that will be invoked. This program will run under CICS transaction id associated with the user program.
  • the Program Link interface also requires an input and output buffer the so called Commarea. The Commarea is used for both input and output data. The input data will be as a result of the object attributes being streamed and the output data will be the data returned by the CICS user application.
  • the connectivity between the CICS inter-operability module and CICS system will be via LU 6.2.
  • the CPIC interface can be used to perform the LU 6.2 communication using sync level 1 or confirm protocol.
  • StartTransaction property will be checked. If it is set to yes, a transaction will be committed at the end of a successful LU 6.2 send/ receive (request/ response mode) or at the end of a conversation (conversational mode) initiated by LU 6.2 allocate.
  • FIGS 19 and 20 set forth some details of IMS processing in - 60
  • the processing set forth in these figures corresponds very closely to the processing in Figures 17 and 18.
  • the purpose of this component is to provide connectivity between the TP inter-operability module and an IMS system running on another computer. Connectivity to IMS is achieved through the IMS LU 6.2 to LU 6.1 adapter which will place an IMS transaction on the IMS transaction queue.
  • the IMS adapter allows a client LU 6.2 application (written to the basic LU 6.2 level or using the CPIC interface) to connect to an IMS system running on a server through the IMS LU 6.2 to LU 6.2 adapter.
  • StartTransaction property will be checked. If it is set to yes, the conversation will be ended at the end of a successful LU 6.2 send/ receive (request/ reply mode) or at the end of a conversation initiated by LU 6.2 allocate.
  • FIGS 21 and 22 set forth details of Pathway processing in accordance with a preferred embodiment.
  • the processing set forth in these figures corresponds very closely to the processing in Figures 17 and 18.
  • the purpose of this component is to provide interoperability between the TP inter-operability module and a Pathway system running on a Tandem computer. Connectivity to Pathway is achieved through the RSC service which runs on the client and server (Tandem) side.
  • the RSC service allows a client application to connect to a Pathway system running on a server through TCP/IP.
  • StartTransaction property will be checked. If it is set to yes, a transaction will be started and committed at the end of a successful RscWrite or
  • Pathway Name of the application Char [16] Server Class Pathway server class. Name
  • Tuxedo TP interop component is a concrete implementation of several abstract classes. It supports the following features:
  • Tuxedo TP interop component will run on a machine supporting either native Tuxedo or /WS.
  • Tuxedo communication buffers CARRAY, String, VIEW and FML.
  • Figure 23 illustrates Tuxedo request / response transactions within an explicit transaction in accordance with a preferred embodiment.
  • Figure 24 illustrates a Tuxedo conversational transaction within an implicit transaction in accordance with a preferred embodiment.
  • the processing ⁇ 63 illustrates Tuxedo request / response transactions within an explicit transaction in accordance with a preferred embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

Système de traitement informatique de transactions destiné à traiter des transactions entre une application et un ou plusieurs processeurs de transactions. Ledit système utilise une première liaison de communication entre l'application et un composant d'interfonctionnement de processeur de transactions. Ensuite, le système détermine lequel parmi la pluralité éventuelle de processeurs traitera les transactions pour l'application et établit une liaison de communication entre le composant d'interfonctionnement de processeur de transactions et le processeur de transactions qui va traiter les transactions pour l'application. Ensuite, lorsque l'application transmet une transaction de l'application au composant d'interfonctionnement de processeur de transactions, la transaction est formatée par le composant d'interfonctionnement du processeur de transactions en vue de sa compatibilité avec le processeur de transactions qui traitera les transactions pour cette application, puis la transaction formatée est transmise au processeur de transactions qui traitera les transactions pour l'application. Les transactions peuvent être lancées implicitement à l'aide des attributs du nom de service dans la base de données de résolveur de service. Des transactions peuvent également être terminées implicitement aux points appropriés à la fois pour la demande/réponse et pour l'interfonctionnement de conversation.
PCT/US1998/001309 1998-01-28 1998-01-28 Systeme et procede permettant de traiter des transactions dans un environnement contenant un certain nombre d'applications objets WO1999039269A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/US1998/001309 WO1999039269A1 (fr) 1998-01-28 1998-01-28 Systeme et procede permettant de traiter des transactions dans un environnement contenant un certain nombre d'applications objets
AU60380/98A AU6038098A (en) 1998-01-28 1998-01-28 A system, method and article of manufacture for processing implied transactions in a universal transaction processing system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US1998/001309 WO1999039269A1 (fr) 1998-01-28 1998-01-28 Systeme et procede permettant de traiter des transactions dans un environnement contenant un certain nombre d'applications objets

Publications (1)

Publication Number Publication Date
WO1999039269A1 true WO1999039269A1 (fr) 1999-08-05

Family

ID=22266254

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/001309 WO1999039269A1 (fr) 1998-01-28 1998-01-28 Systeme et procede permettant de traiter des transactions dans un environnement contenant un certain nombre d'applications objets

Country Status (2)

Country Link
AU (1) AU6038098A (fr)
WO (1) WO1999039269A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2437649B (en) * 2006-04-26 2011-03-30 Hewlett Packard Development Co Compatibillity enforcement in clustered computing systems

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1993023817A1 (fr) * 1992-05-08 1993-11-25 Release Management Systems (Rms) Systeme d'echange de donnees
EP0707265A2 (fr) * 1994-10-11 1996-04-17 International Business Machines Corporation Dispositif et procédé pour la création d'un service transaction orientée objets coopérant avec des coordinateurs de transaction procédurale

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1993023817A1 (fr) * 1992-05-08 1993-11-25 Release Management Systems (Rms) Systeme d'echange de donnees
EP0707265A2 (fr) * 1994-10-11 1996-04-17 International Business Machines Corporation Dispositif et procédé pour la création d'un service transaction orientée objets coopérant avec des coordinateurs de transaction procédurale

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TAKUMA SUDO ET AL: "TRANSACTION PROCESSING IN DISTRIBUTED ENVIRONMENTS", HITACHI REVIEW, vol. 45, no. 2, April 1996 (1996-04-01), pages 55 - 60, XP000622834 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2437649B (en) * 2006-04-26 2011-03-30 Hewlett Packard Development Co Compatibillity enforcement in clustered computing systems
US8370416B2 (en) 2006-04-26 2013-02-05 Hewlett-Packard Development Company, L.P. Compatibility enforcement in clustered computing systems

Also Published As

Publication number Publication date
AU6038098A (en) 1999-08-16

Similar Documents

Publication Publication Date Title
US5854750A (en) System and method for processing transactions in an environment containing a number of object oriented applications
US6038587A (en) System, method and article of manufacture for universal transaction processing over multiple transaction processing systems
US6289393B1 (en) System, method and article of manufacture for transaction processing and monitoring of independent interacts
US6442618B1 (en) System, method and article of manufacture for universal transaction processing
US6044224A (en) Mechanism for dynamically associating a service dependent representation with objects at run time
JP4146983B2 (ja) サーバ・オブジェクトのメソッドを呼び出すプロセス方法及びデータ処理システム
US6389484B1 (en) Transport independent invocation and servant interfaces that permit both typecode interpreted and compiled marshaling
US6263498B1 (en) Method and apparatus for enabling server side distributed object modification
US6085198A (en) Integrated three-tier application framework with automated class and table generation
US6438616B1 (en) Method and apparatus for fast, local corba object references
JP3072709B2 (ja) 要求伝達方法
US6477701B1 (en) Version-adaptive serialization and deserialization of program objects in an object-oriented environment
US7721283B2 (en) Deploying a variety of containers in a Java 2 enterprise edition-based architecture
US5586312A (en) Method and apparatus for using an independent transaction processing application as a service routine
US6260078B1 (en) Using a distributed object system to find and download java-based applications
US6266666B1 (en) Component transaction server for developing and deploying transaction- intensive business applications
US6260077B1 (en) Method, apparatus and program product for interfacing a multi-threaded, client-based API to a single-threaded, server-based API
US5991823A (en) Low overhead object adaptor
US5848273A (en) Method for generating OLE automation and IDL interfaces from metadata information
US6434598B1 (en) Object-oriented system, method and article of manufacture for a client-server graphical user interface (#9) framework in an interprise computing framework system
US5857100A (en) System, method and article of manufacture for extending externalization for universal transaction processing
EP0817024A2 (fr) Procédé et dispositif pour améliorer la performance de l'appel des objets
US6697819B2 (en) Reusable database access component
US6138169A (en) System and method for creating an object oriented transaction service that achieves interoperability with encina procedural transactions
US20030151624A1 (en) Method and system to display, modify or substitute the contents of self-describing objects

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AU

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase