Consistency of routing rules 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 consumer system;
determine if the request includes a request for master data;
determine, from a directory, at least one provider system that can provide the requested data to the consumer;
determine, from the directory, if a provider system can provide master data for the requested data;
if the request for data includes a request for master data and a provider system can provide master data for the requested data, then select the provider system that can provide master data for the requested data;
if the request for data includes a request for master data and no provider system can provide master data for the requested data, then select a provider system from the at least one provider system; and
generate a warning that the selected provider system does not provide master data for the requested data; and
store an identification of the consumer system and an identification of the provider system as a routing rule for providing the requested data.
1 Assignment
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 (e.g., data scope, read-write access, master-copy, etc.) and system role information (e.g., consumer or provider role). The directory may define existing systems, corresponding locations by address, and corresponding semantic names. With such information, a service may create routing rules that may provide the requested data via a semantic-based request. The routing rule may be selected to optimize communications and/or response time.
-
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 consumer system;
determine if the request includes a request for master data;
determine, from a directory, at least one provider system that can provide the requested data to the consumer;
determine, from the directory, if a provider system can provide master data for the requested data;
if the request for data includes a request for master data and a provider system can provide master data for the requested data, then select the provider system that can provide master data for the requested data;
if the request for data includes a request for master data and no provider system can provide master data for the requested data, then select a provider system from the at least one provider system; and
generate a warning that the selected provider system does not provide master data for the requested data; and
store an identification of the consumer system and an identification of the provider system as a routing rule for providing the requested data. - View Dependent Claims (2, 3)
-
-
4. A computer program product, tangibly embodied on computer-readable media, the computer program product being operable to cause a data processing apparatus to:
-
read a routing rule, from a directory, identifying a consumer system and a corresponding provider system and identifying data to be provided from the provider system to the consumer system;
determine, from the directory, if the identified provider system exists;
determine, from the directory, a scope of data that the provider system can provide;
determine if the identified data to be provided is within the scope of data that the provider system can provide. - View Dependent Claims (5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. 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, the request including a specification of a type of data access;
determine, from a directory containing information indicating roles that systems can perform, a provider system that can provide the requested data;
determine, from a directory containing data ownership information about the provider system, whether the provider system can provide the specified type of data access; and
store, if the provider system can provide the specified type of data access, an indication of the system, an indication of the requested data, an indication of the type of data access, and an indication of the provider system, as a routing rule. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20)
-
Specification