Services for data access based on a data ownership directory in distributed system landscapes
First Claim
1. A computer program product, tangibly embodied on computer-readable media, the computer program product being operable to cause a data processing apparatus to:
- receive a request for data from a system;
determine, from a directory, a provider system that can provide the requested data;
determine, from the directory, whether there is a subscription process caching data that includes the requested data;
get the requested data from at least one of the provider system and the cached data; and
provide the requested data to the system.
2 Assignments
0 Petitions
Accused Products
Abstract
A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information. The directory may define existing systems, corresponding locations by address, and corresponding semantic names. The directory may also specify the role of each system, e.g., a consumer or provider role. The directory may also define a scope of data a provider system can provide. As such, the directory may also include information about whether and how such data is being replicated. When a user requests data, a service may, based on the directory, determine and select an appropriate provider system for the data. The service may further create a subscription process to provide the user a local cache of the requested data. With such directory information, a service can provide data access services that integrate subscription processes.
-
Citations
20 Claims
-
1. A computer program product, tangibly embodied on computer-readable media, the computer program product being operable to cause a data processing apparatus to:
-
receive a request for data from a system;
determine, from a directory, a provider system that can provide the requested data;
determine, from the directory, whether there is a subscription process caching data that includes the requested data;
get the requested data from at least one of the provider system and the cached data; and
provide the requested data to the system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A computer program product, tangibly embodied on computer-readable media, the computer program product being operable to cause a data processing apparatus to:
-
determine that a subscription process has been requested that includes a request for data but not an identification of a provider system;
determine a scope of data associated with the request for a subscription process;
determine, from a directory containing data ownership information, a provider system that can provide the scope of data; and
storing a routing rule for caching the requested data from the determined provider system to a cache. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A computer program product, tangibly embodied on computer-readable media, the computer program product being operable to cause a data processing apparatus to:
-
receive a request for data from a system;
determine, from a directory, a first provider system that can provide a first portion of the requested data;
determine, from the directory, a second provider system that can provide a second portion of the requested data, the first portion of requested data and the second portion of requested data, in combination, forming at least the requested data;
request the first portion of data from the first provider system;
request the second portion of data from the second provider system;
receive the first portion of data from the first provider system;
receive the second of data from the second provider system;
assemble the received first portion of data and the received second portion of data; and
provide the assembled data to the system. - View Dependent Claims (17, 18, 19, 20)
-
Specification