Data transmission for transaction processing in a networked environment
First Claim
1. A computer-implemented method 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-implemented method 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 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;
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 manager component of the enterprise information system; and
invoking, based on the repository handle and by the transaction manager component when executed by one or more computer processors, 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.
1 Assignment
0 Petitions
Accused Products
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.
60 Citations
20 Claims
-
1. A computer-implemented method 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-implemented method 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 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; 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 manager component of the enterprise information system; and invoking, based on the repository handle and by the transaction manager component when executed by one or more computer processors, 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification