Browse Prior Art Database

Reusable Consumer-centric Configurable Data Relationship Technique Disclosure Number: IPCOM000213568D
Publication Date: 2011-Dec-21
Document File: 4 page(s) / 98K

Publishing Venue

The Prior Art Database


A method for configuring consumer-centric data relationships for querying data by a consumer from a provider is disclosed. The method includes managing the data relationships using configuration profiles. This is accomplished by using a framework called Data Access Framework.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 4

Reusable Consumer-centric Configurable Data Relationship Technique

During data querying, the entity which consumes or queries for the data is a consumer and the entity which provides the data or owns the data is a provider. Currently, when one software component (consumer) requires data from a database (provider), it needs to provide a database access method or interact with another software component that embeds a database access method to retrieve the desired data. Such a database access method requires writing code for the database access method. This needs to be updated or re-written when new requirements need to be implemented. The re-writing operation is expensive since it requires a complete software life-cycle worth of changes and activities.

Disclosed is a method for utilizing a Data Access Framework for querying data from a provider by a consumer regardless of the platform of the provider. The Data Access Framework may be implemented in any programming language and used to define new consumer-centric relationships or modify consumer-centric relationships during run-time. The data access framework includes a configuration profile subsystem, a Consumer API Function subsystem and a Data Access Engine subsystem as illustrated in Figure 1.

Figure 1

The configuration profile subsystem is used to manage the data relationships. The data relationships that reflect the entity relationships as defined in the database are referenced. This is accomplished by establishing a reference data hierarchy (RDH) based on the entity relationship defined in the database. Further, the RDH configuration profile is created by the provider to track the database structural relationships. Still further, the RDH configuration profile also works as a reference for the Data Access Engine subsystem. The RDH configuration profile may be created in advance since data relationships are known in advance.


Page 02 of 4

Further, the profiles in the configuration profile subsystem may be changed for consumer centric access based on consumer requirements. This is accomplished by establishing a list of entities required for accessing a consumer application. Thereafter, consumer data hierarchy (CDH) that is based on the entity rela...