US7974965B2ActiveUtilityA1
Federated pagination management
Est. expiryDec 17, 2027(~1.4 yrs left)· nominal 20-yr term from priority
G06F 16/2471G06F 16/256Y10S707/971
52
PatentIndex Score
3
Cited by
22
References
12
Claims
Abstract
A method of processing a plurality of instances in a federated deployment of SOA applications can include the steps of receiving a transaction request to retrieve data, the request specifying retrieving the data stored according to range of indices of the federated deployment, processing each of the instances in a predetermined order to retrieve the data; and calculating a total number of records in the federated deployment.
Claims
exact text as granted — not AI-modified1. A method of processing a plurality of instances in a federated database, the method comprising:
receiving a first transaction request to retrieve data, the request specifying retrieving the data stored according to a range of indices of the federated database, and wherein the federated database comprises a local instance and one or more remote instances;
processing the local instance to identify whether data responsive to the request is stored in the local instance;
processing each of the remote instances in a predetermined order to retrieve the requested data, wherein the local instance is processed prior to the one or more remote instances, and wherein the processing includes, for each remote instance:
comparing a total number of records in a current remote instance being processed to a lower limit and an upper limit of the range of indices,
retrieving data from the current remote instance when the lower limit is less than the total number of records in the instances that have been processed, wherein the data is retrieved from the current remote instance using a range of indices specified by the lower limit and a lesser one of the upper limit and the total number of records in the remote instance, and
prior to processing a subsequent remote instance identified according to the predetermined order, decrease values of the upper and lower limits when the upper limit is greater than the total number of records in the current remote instance, wherein the decreased values specify an expected range of indices associated with data in the subsequently processed remote instance; and
calculating a total number of records in the federated database.
2. The method of claim 1 , wherein the range of indices used to retrieve the data fails to retrieve at least a portion of the data, the step of processing further comprising:
calculating a targeted range of indices for the instance; and
retrieving the data from the instance using the targeted range of indices.
3. The method of claim 1 , wherein the step of decreasing further comprises decreasing the values of the range of indices to a default value.
4. The method of claim 1 , further comprising the steps of:
receiving at least a second transaction request; and
repeating the steps of processing and calculating for the second transaction request, wherein the predetermined order is the same for the first transaction request and the second transaction request.
5. A system for managing data, comprising
a plurality of storage elements, the storage elements comprising instances of a federated database; and
a processing element configured to:
receive a first transaction request to retrieve data from the federated database, wherein the request specifies retrieving the data stored according to a range of indices for the federated database, and wherein the federated database comprises a local instance and one or more remote instances,
process the local instance to identify whether data responsive to the request is stored in the local instance,
process each of the remote instances in a predetermined order to retrieve the requested data, wherein the local instance is processed prior to the one or more remote instances, and wherein the processing includes, for each remote instance:
compare a total number of records in a current remote instance being processed to a lower limit and an upper limit of the range of indices;
retrieve data from the current remote instance when the lower limit is less than the total number of records in the instances that have been processed, wherein the data is retrieved from the instance using a range of indices specified by the lower limit and a lesser one of the upper limit and the total number of records in the remote instance; and
prior to processing a subsequent remote instance identified according to the predetermined order, decrease values of the upper and lower limits when the upper limit is greater than the total number of records in the current remote instance, wherein the decreased values specify an expected range of indices associated with data in the subsequently processed remote instance; and
calculate a total number of records in the federated database.
6. The system of claim 5 , wherein the range of indices used to retrieve the data fails to retrieve at least a portion of the data, and wherein the processing element is further configured to:
prior to the decreasing step, calculate a targeted range of indices for the instance; and
retrieve the data from the instance using the targeted range of indices.
7. The system of claim 5 , and wherein the step of decreasing further comprises decreasing the values of the range of indices to a default value.
8. The system of claim 5 , wherein the processing element is further configured to:
receive at least a second transaction request; and
repeat the steps of processing and calculating for the second transaction request, wherein the predetermined order is the same for the first transaction request and the second transaction request.
9. A computer-readable storage medium, having stored thereon a computer program for searching a plurality of instances in a federated database, the computer program comprising a plurality of code sections executable by a computer for causing the computer to perform the steps of:
receiving a first transaction request to retrieve data, the request specifying retrieving the data stored according to range of indices of the federated database, and wherein the federated database comprises a local instance and one or more remote instances;
processing the local instance to identify whether data responsive to the request is stored in the local instance;
processing of the remote instances in a predetermined order to retrieve the requested data, wherein the local instance is processed prior to the one or more remote instances, and wherein the processing includes, for each remote instance:
comparing a total number of records in a current remote instance being processed to a lower limit and an upper limit of the range of indices,
retrieving data from the current remote instance when the lower limit is less than the total number of records in the instances that have been processed, wherein the data is retrieved from the current remote instance using a range of indices specified by the lower limit and a lesser one of the upper limit and the total number of records in the remote instance, and
prior to processing a subsequent remote instance identified according to the predetermined order, decreasing values of the upper and lower limits when the upper limit is greater than the total number of records in the current remote instance, wherein the decreased values specify an expected range of indices associated with data in the subsequently processed instance; and calculating a total number of records in the federated database.
10. The computer-readable storage of claim 9 , wherein the range of indices used to retrieve the data fails to retrieve at least a portion of the data, and further comprising code sections for:
prior to the decreasing step, calculating a targeted range of indices for the instance; and
retrieving the data from the instance using the targeted range of indices.
11. The computer-readable storage of claim 9 , wherein the step of decreasing further comprises decreasing the values of the range of indices to a default value.
12. The computer-readable storage of claim 9 , wherein the plurality of code sections further includes code sections for:
receiving at least a second transaction request; and
repeating the steps of processing and calculating for the second transaction request, wherein the predetermined order is the same for the first transaction request and the second transaction request.Join the waitlist — get patent alerts
Track US7974965B2 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.