Data transmission for transaction processing in a networked environment

• US 9,473,561 B2
• Filed: 03/15/2013
• Issued: 10/18/2016
• Est. Priority Date: 03/15/2013
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cameron, David A., Ho, Shyh-Mei F., Hung, Jenny C., Yuan, Jack C.
• Primary Examiner(s): Moise, Emmanuel L
• Assistant Examiner(s): Chang, Julian
• Application Number:
  US13/841,665
• Publication Number:
  US 20140280759A1
• Time in Patent Office: 1,313 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1865 Transactional file systems
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/50 of still image data
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

Techniques are disclosed to transmit arbitrarily large data units for transaction processing in a networked environment. A request is received to store a data unit of a size exceeding an allocated memory address space of a transaction gateway component of the networked environment. A predefined store function, provided by a repository interface component, is invoked to store the data unit to a data repository component of the networked environment and without segmenting the data unit. A repository handle of the stored data unit is identified. A predefined load function, provided by the repository interface component, is invoked to load a portion of the stored data unit, based on the identified repository handle, where the portion is smaller than the stored data unit.

Claims

1. A computer program product to manage arbitrarily large transactional data structures for transaction processing, by an enterprise information system having a transaction gateway component, a transaction manager component, and a repository interface component, the computer program product comprising:

a non-transitory computer-readable medium having program code embodied therewith, the program code executable by one or more computer processors to;

receive, the transaction gateway component of the enterprise information system, a first request to store a first transactional data structure of a size exceeding an allocated memory address space of the transaction gateway component;

invoke, by the transaction gateway component, a first predefined store function provided by the repository interface component of the enterprise information system, in order to store the first transactional data structure to a data repository component of the enterprise information system and without segmenting the first transactional data structure;

identify, by the repository interface component, a repository handle of the stored transactional data structure, wherein the repository handle is passed from the transaction gateway component to the transaction manager component of the enterprise information system; and

invoke, by the transaction manager component and based on the repository handle, a first predefined load function provided by the repository interface component, in order to load, to the transaction manager component, only a portion of the stored transactional data structure, wherein the portion is smaller than the stored transactional data structure.

2. The computer program product of claim 1, wherein the transaction manager component is provided with the portion of the first transactional data structure without requiring the portion of the first data unit to be transmitted from the transaction gateway component to the transaction manager component.

3. The computer program product of claim 2, wherein the program code is further executable to:

receive, from a requesting entity external to the networked environment, a second request to retrieve the portion of the stored transactional data structure, wherein the repository handle of the stored transactional data structure is identified by the transaction manager component, based on the second request; and

send the loaded portion to the requesting entity, responsive to the second request and without combining any segments of the first transactional data structure.

4. The computer program product of claim 3, wherein the program code is further executable to receive, from the requesting entity, a third request to retrieve the entirety of the stored transactional data structure, wherein the repository handle of the stored transactional data structure is identified by the transaction manager component, based on the third request;

invoke a second predefined load function provided by the repository interface component in order to load the entirety of the stored transactional data structure from the data repository component to the transaction gateway component, wherein the first predefined load function and the second predefined load function are distinct functions; and

send the loaded entirety of the first transactional data structure unit to the requesting entity, responsive to the third request and without combining any segments of the first transactional data structure.

5. The computer pro rare product of claim 4, wherein the repository interface component further provides:

a second predefined store function configured to append data to the stored transactional data structure, wherein the first predefined store function and the second predefined, store function are distinct functions; and

a predefined delete function configured to remove the first transactional data structure from the data repository component.

6. The computer program product of claim 5, wherein the first predefined store function specifies a first set of formal parameters consisting of a pointer to a desired transactional data structure, a size of the desired transactional data structure, and a property set of the desired transactional data structure;

wherein the second predefined store function specifies a second set of formal parameters consisting of a pointer to a desired transactional data structure, a size of the desired transactional data structure, a repository handle of the desired transactional data structure, and a property set of the desired transactional data structure;

wherein the first predefined load function specifies a third set of formal parameters consisting of a repository handle of the desired transactional data structure, an offset into the desired transactional data structure, a size of the desired transactional data structure, and a property set of the desired transactional data structure;

wherein the second predefined load function specifies a fourth set of formal parameters consisting of;

(i) a repository handle of the desired transactional data structure and (ii) a property set of the desired transactional data structure;

wherein the predefined delete function specifies a fifth set of formal parameters consisting of;

(i) a repository handle of the desired transactional data structure and (ii) a property set of the desired transactional data structure;

wherein each property set includes repository access information, a browse option, a discard option, and a retrieval option.

7. The computer program product of claim 6,

wherein the first request is received from the requesting entity, wherein the transaction gateway component comprises an enterprise gateway component, wherein the allocated memory address space comprises control region memory of the transaction gateway component;

wherein each request is selected from a provider-type request and a consumer type request, wherein each request is not a web service request, wherein the first request, the second request, and the third request are distinct requests, wherein the requesting entity comprises a distributed client application;

wherein storing the first transactional data structure to the data repository component without segmenting the first transactional data structure comprises storing the first transactional data structure to the data repository component while bypassing a message queue component of the enterprise information system, wherein the message queue component is configured to segment transactional data structures;

wherein the loaded portion, which is sent to the requesting entity without combining any segments of the first transactional data structure, is retrieved by bypassing the message queue component of the enterprise information system, wherein the message queue component is further configured to combine transactional data structure segments.

8. The computer program product of claim 1, wherein the repository interface component further provides a second predefined store function configured to append data to the stored transactional data structure.

9. The computer program product of claim 1, wherein the repository interface component further provides a predefined delete function configured to remove the first transactional data structure from the data repository component.

10. The computer program product of claim 1, wherein the first transactional data structure is stored to the data repository component while bypassing a message queue component of the enterprise information system.

11. The computer program product of claim 1, wherein the portion of the first transactional data structure is loaded while bypassing a message queue component of the enterprise information system.

12. A system to manage arbitrarily large transactional data structures for transaction processing, by an enter rise information s stem having a transaction gateway component, a transaction manager component, and a repository interface component, the system comprising:

one or more computer processors;

a memory containing a program which, when executed by the one or more computer processors, is configured to perform an operation comprising;

receiving, by the transaction gateway component of the enterprise information system, a first request to store a first transactional data structure of a size exceeding an allocated memory address space of the transaction gateway component;

invoking, by the transaction gateway component, a first predefined store function provided by the repository interface component of the enterprise information s stem, in order to store the first transactional data structure to a data repository component of the enterprise information, system and without segmenting the first transactional data structure;

identifying, by the repository interface component, a repository handle of the stored transactional data structure, wherein the repository handle is passed from the transaction gateway component to the transaction Tanager component of the enterprise information system; and

invoking, by the transaction manager component and based on the repository handle, a first predefined load function provided by the repository interface component, in order to load, to the transaction manager component, only a portion of the stored transactional data structure, wherein the portion is smaller than the stored transactional data structure.

13. The system of claim 12, wherein the transaction manager component is provided with the portion of the first transactional data structure without requiring the portion of the first transactional data structure to be transmitted from the transaction gateway component to the transaction manager component.

14. The system of claim 13, wherein the operation further comprises:

receiving, from a requesting entity external to the networked environment, a second request to retrieve the portion of the stored transactional data structure, wherein the repository handle of the stored transactional data structure is identified by the transaction manager component, based on the second request; and

sending the loaded portion to the requesting entity, responsive to the second request and without combining any segments of the first transactional data structure.

15. The system of claim 14, wherein the operation further comprises:

receiving, from the requesting entity, a third request to retrieve the entirety of the stored transactional data structure, wherein the repository handle of the stored transactional data structure is identified by the transaction manager component, based on the third request;

invoking a second predefined load function provided by the repository interface component in order to load the entirety of the stored transactional data structure from the data repository component to the transaction gateway component, wherein the first predefined load function and the second predefined load function are distinct functions; and

,

sending the loaded entirety of the first transactional data structure unit to the requesting entity responsive to the third request and without combining any segments of the first transactional data structure.

16. The system of claim 15, wherein the repository interface component further provides:

a second predefined store function configured to append data to the stored transactional data structure, wherein the first predefined store function and the second predefined store function are distinct functions; and

a predefined delete function configured to remove the first transactional data structure from the data repository component.

17. The system of claim 12, wherein the repository interface component further provides a second predefined store function configured to append data to the stored transactional data structure.

18. The system of claim 12, wherein the repository interface component further provides a predefined delete function configured to remove the first transactional data structure from the data repository component.

19. The system of claim 12, wherein the first transactional data structure is stored to the data repository component while bypassing a message queue component of the enterprise information system.

20. The system of claim 12, wherein the portion of the first transactional data structure is loaded while bypassing a message queue component of the enterprise information system.