DATA TRANSMISSION FOR TRANSACTION PROCESSING IN A NETWORKED ENVIRONMENT

• US 20140280680A1
• Filed: 03/25/2014
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• 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.
• Granted Patent: US 9,473,565 B2
• Time in Patent Office: Days
• US Class Current: 709/213
• 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-implemented method to transmit arbitrarily large data units for transaction processing in a networked environment, the method comprising:

receiving a first request to store a first data unit of a size exceeding an allocated memory address space of a transaction gateway component of the networked environment;

invoking a first predefined store function provided by a repository interface component, to store the first data unit to a data repository component of the networked environment and without segmenting the first data unit;

identifying a repository handle of the stored data unit; and

invoking a first predefined load function provided by the repository interface component, to load a portion of the stored data unit, based on the identified repository handle and by operation of one or more computer processors, wherein the portion is smaller than the stored data unit.

2. The computer-implemented method of claim 1, wherein the invoking of the first predefined load function based on the identified repository handle causes the repository interface component to load the portion of the stored data unit to a transaction manager component of the networked environment, thereby providing the transaction manager component with the portion of the first data unit 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-implemented method of claim 2, further comprising:

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

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

4. The computer-implemented method of claim 3, further comprising:

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

invoking a second predefined load function provided by the repository interface component to load the entirety of the stored data unit 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 data unit to the requesting entity, responsive to the third request and without combining any segments of the first data unit.

5. The computer-implemented method of claim 4, wherein the repository interface component further provides:

a second predefined store function configured to append data to the stored data unit, 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 data unit from the data repository component.

6. The computer-implemented method of claim 5, wherein the first predefined store function specifies a first set of formal parameters consisting of a pointer to a desired data unit, a size of the desired data unit, and a property set of the desired data unit;

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

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

wherein the second predefined load function specifies a fourth set of formal parameters consisting of a repository handle of the desired data unit and a property set of the desired data unit;

wherein the predefined delete function specifies a fifth set of formal parameters consisting of a repository handle of the desired data unit and a property set of the desired data unit;

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

7. The computer-implemented method of claim 6, wherein the method is to manage arbitrarily large file attachments for transaction processing in the networked environment, wherein the first data unit comprises a first file attachment;

wherein the first request is received from the requesting entity, wherein the networked environment comprises an enterprise information system (EIS), wherein the transaction gateway comprises an enterprise gateway, wherein the repository interface component comprises a repository application programming interface (API), wherein the memory comprises control region memory;

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.