Method for encapsulating logical units of work using business objects

• US 9,110,712 B2
• Filed: 06/10/2005
• Issued: 08/18/2015
• Est. Priority Date: 06/10/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Kalavacharla, Muralidhar, Khan, Zafrulla, Lee, Peter Bow Kwong, Louis, Danyiel Amii, Raghav, Sandeep, Wintroub, Alan Michael
• Primary Examiner(s): KUDDUS, DANIEL A
• Application Number:
  US11/149,647
• Publication Number:
  US 20060282400A1
• Time in Patent Office: 3,721 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1834 implemented based on peer-to-peer networks, e.g. gnutella p2p communication protocols H04L67/104
• CPC Class Codes: G06F 16/90 Details of database functions independent of the retrieved data types
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

A method for processing a data transaction using a single business object includes providing a transaction business object encapsulating multiple function calls for completing a data transaction. The transaction business object includes an execution sequence indicating the order the function calls should be executed. In certain embodiments, the transaction business object is assigned an operation indicating an action to be taken on data in the transaction business object. This operation is used, in selected embodiments, to determine the function calls and execution sequence that are used to process the transaction business object.

Claims

1. A computer implemented method, the method implemented on a processor and a memory programmed for processing a data transaction using a single business object, the method comprising:

receiving a business object;

identifying the business object as a transaction business object, the transaction business object comprising a prefix, a suffix, or both the prefix and the suffix appended to a name of the business object that identifies the business object as a transaction business object, the transaction business object further comprising a single business object encapsulating a plurality of business objects corresponding respectively to a plurality of function calls to heterogeneous applications for performing an entire atomic transaction, the atomic transaction comprising an indivisible set of operations forming a logical unit of work that must be executed in the atomic transaction'"'"'s entirety on the heterogeneous applications;

identifying unused parameters for the single business object;

determining an execution sequence for the plurality of function calls encapsulated in the single business object, the execution sequence defined by at least one operation designated by metadata encapsulated by the transaction business object;

removing function calls for the unused parameters;

inserting a COMMIT operation after at least one of the function calls of the plurality of function calls in the execution sequence, wherein two COMMIT operations are not successive;

mapping data from a source function call of the plurality of function calls to a target function call of the plurality of function calls in the execution sequence;

executing each of the function calls according to the execution sequence, wherein the plurality of business objects corresponding to the plurality of function calls to the heterogeneous applications are passed though an integration broker as a single business object; and

executing one of the commit operation and a roll back operation to either commit or roll back each operation of the logical unit of work.

2. The method of claim 1, wherein identifying further comprises determining a type associated with the business object, the type identifying the business object as a transaction business object.

3. The method of claim 1, wherein the at least one operation designated by the metadata is selected from the group consisting of a create, retrieve, update, and delete operation.

4. The method of claim 3, the method further identifying the plurality of function calls corresponding to the at least one operation, the plurality of function calls stored in a transaction business object definition.

5. The method of claim 4, further comprising storing the transaction business object definition in an XML schema file.

6. The method of claim 1, wherein executing further comprises executing each of the plurality of function calls in the execution sequence during a single communication connection.

7. The method of claim 1, further comprising rolling back the plurality of function calls in the execution sequence in response to at least one of the plurality of function calls failing.

8. An apparatus for providing a transaction business object to an end user, the apparatus comprising:

a non-transitory computer readable storage medium storing computer usable program code;

a processor executing the computer usable program code, the computer usable program code comprising;

an integration adapter that receives a business object by way of the processor;

an identification module that identifies the business object as a transaction business object, the transaction business object comprising a prefix, a suffix, or both the prefix and the suffix appended to a name of the business object that identifies the business object as a transaction business object, the transaction business object further comprising a single business object encapsulating a plurality of business objects corresponding respectively to a plurality of function calls to heterogeneous applications for performing an entire atomic transaction, the atomic transaction comprising an indivisible set of operations forming a logical unit of work that must be executed in the atomic transaction'"'"'s entirety on the heterogeneous applications, the function calls corresponding to an application interface for at least one of the heterogeneous applications, and the identification module identifies unused parameters for the single business object;

an sequencing module that determines an execution sequence for the plurality of function calls, the execution sequence defined by at least one operation designated by metadata in the transaction business object, inserts a COMMIT operation after at least one of the function calls of the plurality of function calls in the execution sequence, wherein two COMMIT operations are not successive, removes function calls for the unused parameter, and maps data from a source function call of the plurality of function calls to a target function call of the plurality of function calls in the execution sequence;

an execution module that executes each of the function calls according to the execution sequence, wherein the plurality of business objects corresponding to the plurality of function calls to the heterogeneous applications are passed though an integration broker as a single business object; and

executing one of the commit operation and a roll back operation to either commit or roll back each operation of the logical unit of work.

9. The apparatus of claim 8, wherein identifying further comprises determining a type associated with the business object, the type identifying the business object as a transaction business object.

10. The apparatus of claim 9, wherein the at least one operation designated by the metadata is selected from the group consisting of a create, retrieve, update, and delete operation.

11. The apparatus of claim 8, wherein the transaction business object definition is stored in an XML schema file.

12. The apparatus of claim 8, wherein executing further comprises executing each of the plurality of function calls in the execution sequence during a single communication connection.

13. The apparatus of claim 8, further comprising rolling back the plurality of function calls in response to at least one of the plurality of function calls failing.

14. A computer program product comprising a non-transitory computer readable storage medium having computer usable program code stored thereon for processing a data transaction using a single business object, the computer program product including:

computer usable program code for receiving a business object;

computer usable program code for identifying the business object as a transaction business object, the transaction business object comprising a prefix, a suffix, or both the prefix and the suffix appended to a name of the business object that identifies the business object as a transaction business object, the transaction business object further comprising a single business object encapsulating a plurality of business objects corresponding respectively to a plurality of function calls to heterogeneous applications for performing an entire atomic transaction, the atomic transaction comprising an indivisible set of operations forming a logical unit of work that must be executed in the atomic transaction'"'"'s entirety on the heterogeneous applications, the function calls corresponding to an application interface, the transaction business object encapsulating the plurality of function calls in the single business object such that the plurality of business objects corresponding to the plurality of function calls are passed though an integration broker as a single business object;

computer usable program code for identifying unused parameters for the single business object;

computer usable program code for determining an execution sequence for the plurality of function calls encapsulated in the single business object, the execution sequence defined by at least one operation designated by metadata encapsulated by the transaction business object;

computer usable program code for removing function calls for the unused parameters;

computer usable program code for inserting a COMMIT operation after at least one of the function calls of the plurality of function calls in the execution sequence, wherein two COMMIT operations are not successive;

computer usable program code for mapping data from a source function call of the plurality of function calls to a target function call of the plurality of function calls in the execution sequence;

computer usable program code for executing each of the function calls according to the execution sequence, wherein the plurality of business objects corresponding to the plurality of function calls to the heterogeneous applications are passed though an integration broker as a single business object; and

executing one of the commit operation and a roll back operation to either commit or roll back each operation of the logical unit of work.

15. The computer program product of claim 14, wherein identifying further comprises determining a type associated with the business object, the type identifying the business object as a transaction business object.

16. The computer program product of claim 14, wherein the at least one operation designated by the metadata is selected from the group consisting of a create, update, and delete operation.

17. The computer program product of claim 16, further comprising identifying the plurality of function calls corresponding to the at least one operation, the plurality of function calls stored in a transaction business object definition.

18. The computer program product of claim 14, wherein the transaction business object definition is stored in an XML schema file.

19. The computer program product of claim 14, wherein each of the function calls in the execution sequence is executed during a single communication connection.

20. The computer program product of claim 14, further comprising rolling back the plurality of function calls in response to at least one of the plurality of function calls failing.