System and method for processing transactions in an environment containing a number of object oriented applications

• US 5,854,750 A
• Filed: 09/03/1996
• Issued: 12/29/1998
• Est. Priority Date: 09/03/1996
• Status: Expired due to Term

• Current Assignee: ACI Worldwide Corporation (ACI Worldwide Incorporated)
• Original Assignee: Insession, Inc. (ACI Worldwide Incorporated)
• Inventors: Phillips, Mark, Blevins, Michael
• Primary Examiner(s): Elmore, Reba I.
• Assistant Examiner(s): Marc, McDieunel, Marc, McDieunel
• Application Number:
  US08/707,334
• Time in Patent Office: 847 Days
• Field of Search: 364/478.04, 364/200, 364/474.22, 364/401.403, 395/650, 395/614, 395/611, 395/339, 395/348, 395/352, 395/353, 395/761, 395/762, 395/763, 395/807, 395/357
• US Class Current: 700/216
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

A computer implemented transaction processing system is presented for processing transactions between an application and one or more transaction processors. The system utilizes a first 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. Transactions can be started implicitly utilizing the attributes of the service name in the service resolver database. Transactions can also be terminated implicitly at the appropriate points both for request/response and conversational interoperability.

Claims

1. A method for processing transactions between

a number of object oriented applications and one or more instances of the same transaction processor type or multiple transaction processor types, the method comprising the steps of:

(a) establishing a first communication link between the objected oriented applications and a transaction processor interoperability component;

(b) externalizing a plurality of object oriented attributes into a data format compatible with said transaction processors;

(c) internalizing a plurality of transaction processor data into a plurality of object oriented attributes;

(d) determining which of the one or more transaction processors of the same or different type will process transactions for the utilizing implicit attributes of the transaction and a service database;

(e) establishing a communication link between the transaction processor interoperability component and the transaction processor that will process transactions for the object oriented application;

(f) transmitting a transaction from the object oriented application to the transaction processor interoperability component;

(g) formatting the transaction by the transaction processor interoperability component for the transaction processor that will process transactions for the object oriented application; and

(h) transmitting the formatted transaction to the transaction processor that will process transactions for the object oriented application.

2. The method of claim 1, including the step of processing various transaction semantics utilizing explicit object oriented attributes of the transaction.

3. The method of claim 1, including the step of logging transaction attributes of each transaction.

4. A system for processing transactions between

a number of object oriented applications and one or more instances of the same transaction processor type or multiple transaction processor types, comprising:

(a) means for establishing a first communication link between the objected oriented applications and a transaction processor interoperability component;

(b) means for externalizing a plurality of object oriented attributes into a data format compatible with said transaction processors;

(c) means for internalizing a plurality of transaction processor data into a plurality of object oriented attributes;

(d) means for determining which of the one or more transaction processors of the same or different type will process transactions for the utilizing implicit attributes of the transaction and a service database;

(e) means for establishing a communication link between the transaction processor interoperability component and the transaction processor that will process transactions for the object oriented application;

(f) means for transmitting a transaction from the object oriented application to the transaction processor interoperability component;

(g) means for formatting the transaction by the transaction processor interoperability component for the transaction processor that will process transactions for the object oriented application; and

(h) means for transmitting the formatted transaction to the transaction processor that will process transactions for the object oriented application.

5. The system of claim 4, including means for processing various transaction semantics utilizing explicit object oriented attributes of the transaction.

6. The system of claim 4, including means for logging transaction attributes of each transaction.

7. A computer program embodied on a computer-readable medium for processing transactions between a number of object oriented applications and one or more instances of the same transaction processor type or multiple transaction processor types, comprising:

(a) a code segment for establishing a first communication link between the objected oriented applications and a transaction processor interoperability component;

(b) externalizing a plurality of object oriented attributes into a data format compatible with said transaction processors;

(c) internalizing a plurality of transaction processor data into a plurality of object oriented attributes,

(d) a code segment for determining which of the one or more transaction processors of the same or different type will process transactions for the utilizing implicit attributes of the transaction and a service database;

(e) a code segment for establishing a communication link between the transaction processor interoperability component and the transaction processor that will process transactions for the object oriented application;

(f) a code segment for transmitting a transaction from the object oriented application to the transaction processor interoperability component;

(g) a code segment for formatting the transaction by the transaction processor interoperability component for the transaction processor that will process transactions for the object oriented application; and

(h) a code segment for transmitting the formatted transaction to the transaction processor that will process transactions for the object oriented application.

8. The computer program of claim 7, further comprising a code segment for processing various transaction semantics utilizing explicit object oriented attributes of the transaction.

9. The computer of claim 7, further comprising a code segment for including the step of logging transaction attributes of each transaction.