Information services patterns in a netcentric environment

• US 6,434,568 B1
• Filed: 08/31/1999
• Issued: 08/13/2002
• Est. Priority Date: 08/31/1999
• Status: Expired due to Term

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture LLP (Accenture PLC)
• Inventors: Bowman-Amuah, Michel K.
• Primary Examiner(s): Breene, John
• Assistant Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US09/387,071
• Time in Patent Office: 1,078 Days
• Field of Search: 707/103, 707/10, 707/104, 707/7, 707/104.1, 705/7, 705/1, 395/701, 709/203, 709/300, 709/303
• US Class Current: 1/1
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A system, method, and article of manufacture are provided for implementing information services patterns associated with a relational database management system in an object-oriented persistence architecture. An object attribute is translated to and from a database value utilizing a database. Data is controlled in the database utilizing a data retrieval mechanism encapsulated in a data handler. Data access to the database is then organized among a plurality of business entities utilizing a plurality of business objects. Multiple business objects are retrieved across a network in one access operation. Retrieved data is mapped into objects. Then a warning is provided upon retrieval of objects missing at least one attribute. The warning includes information on how to handle the at least one missing attribute.

Claims

1. A method for implementing information services patterns associated with a relational database management system in an object-oriented persistence architecture, comprising the steps of:

(a) translating an object attribute to and from a database value utilizing a database;

(b) controlling data in the database utilizing a data retrieval mechanism encapsulated in a data handler;

(c) organizing data access to the database among a plurality of business entities utilizing a plurality of business objects;

(d) retrieving multiple business objects across a network in one access operation;

(e) mapping retrieved data into objects; and

(f) providing a warning upon retrieval of objects missing at least one attribute, wherein the warning includes information on how to handle the at least one missing attribute.

2. A method as recited in claim 1, further comprising the step of separating logic and data access concerns during development of a persistent object in order to insulate development of business logic from development of data access routine.

3. A method as recited in claim 1, further comprising the steps of implementing an association of business objects without retrieving the business objects from a database on which the business objects are stored by providing a business object, storing an instance of an associated object on a database, determining an association of the business object with the instance of the associated object, generating an object identifier containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, loading the object identifier when the business object starts, determining location of the instance of the associated object on the database from the object identifier, and retrieving the instance of the associated object from the database.

4. A method as recited in claim 1, wherein the step of organizing data access to the database among a plurality of business entities includes the steps of:

retrieving data about a user;

packaging the data into a cross-functional data object;

retrieving a request for data from one of a plurality of business objects; and

directing the business object to the data object such that the business object retrieves the entire data object, wherein the business object selects the data from the data object.

5. A method as recited in claim 1, wherein the step of retrieving multiple business objects across a network in one access operation includes the steps of:

providing a business object and a plurality of remaining objects on a persistent store;

receiving a request for the business object;

establishing which of the remaining objects are related to the business object;

retrieving the related objects and the business object from the persistent store in one operation;

determining how the retrieved related objects relate to the business object and each other; and

instantiating a graph of relationships of the business and related objects in memory.

6. A method as recited in claim 1, wherein the step of translating the object value to and from the database value utilizing a database includes the steps of:

providing a database;

determining a conversion process for converting an object attribute to and from a database value;

encapsulating the conversion process in an attribute converter;

directing a first object attribute to the attribute converter for conversion to a first database value; and

directing a second database value to the attribute converter for conversion to a second object attribute.

7. A computer program embodied on a computer readable medium for implementing information services patterns associated with a relational database management system in an object-oriented persistence architecture, comprising:

(a) a code segment that translates an object attribute to and from a database value utilizing a database;

(b) a code segment that controls data in the database utilizing a data retrieval mechanism encapsulated in a data handler;

(c) a code segment that organizes data access to the database among a plurality of business entities utilizing a plurality of business objects;

(d) a code segment that retrieves multiple business objects across a network in one access operation;

(e) a code segment that maps retrieved data into objects; and

(f) a code segment that provides a warning upon retrieval of objects missing at least one attribute, wherein the warning includes information on how to handle the at least one missing attribute.

8. A computer program as recited in claim 7, further comprising a code segment that separates logic and data access concerns during development of a persistent object in order to insulate development of business logic from development of data access routine.

9. A computer program as recited in claim 7, further comprising a code segment that implements an association of business objects without retrieving the business objects from a database on which the business objects are stored by providing a business object, storing an instance of an associated object on a database, determining an association of the business object with the instance of the associated object, generating an object identifier containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, loading the object identifier when the business object starts, determining a location of the instance of the associated object on the database from the object identifier, and retrieving the instance of the associated object from the database.

10. A computer program as recited in claim 7, wherein the code segment that organizes data access to the database among a plurality of business entities includes:

a code segment that retrieves data about a user;

a code segment that packages the data into a cross-functional data object;

a code segment that retrieves a request for data from one of a plurality of business objects; and

a code segment that directs the business object to the data object such that the business object retrieves the entire data object, wherein the business object selects the data from the data object.

11. A computer program as recited in claim 7, wherein the code segment that retrieves multiple business objects across a network in one access operation includes:

a code segment that provides a business object and a plurality of remaining objects on a persistent store;

a code segment that receives a request for the business object;

a code segment that establishes which of the remaining objects are related to the business object;

a code segment that retrieves the related objects and the business object from the persistent store in one operation;

a code segment that determines how the retrieved related objects relate to the business object and each other; and

a code segment that instantiates a graph of relationships of the business and related objects in memory.

12. A computer program as recited in claim 7, wherein the code segment that translates the object value to and from the database value utilizing a database includes:

a code segment that provides a database;

a code segment that determines a conversion process for converting an object attribute to and from a database value;

a code segment that encapsulates the conversion process in an attribute converter;

a code segment that directs a first object attribute to the attribute converter for conversion to a first database value; and

a code segment that directs a second database value to the attribute converter for conversion to a second object attribute.

13. A system for implementing information services patterns associated with a relational database management system in an object-oriented persistence architecture, comprising:

(a) logic that translates an object attribute to and from a database value utilizing a database;

(b) logic that controls data in the database utilizing a data retrieval mechanism encapsulated in a data handler;

(c) logic that organizes data access to the database among a plurality of business entities utilizing a plurality of business objects;

(d) logic that retrieves multiple business objects across a network in one access operation;

(e) logic that maps retrieved data into objects; and

(f) logic that provides a warning upon retrieval of objects missing at least one attribute, wherein the warning includes information on how to handle the at least one missing attribute.

14. A system as recited in claim 13, further comprising logic that separates logic and data access concerns during development of a persistent object in order to insulate development of business logic from development of data access routine.

15. A system as recited in claim 13, further comprising logic that implements an association of business objects without retrieving the business objects from a database on which the business objects are stored by providing a business object, storing an instance of an associated object on a database, determining an association of the business object with the instance of the associated object, generating an object identifier containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, loading the object identifier when the business object starts, determining a location of the instance of the associated object on the database from the object identifier, and retrieving the instance of the associated object from the database.

16. A system as recited in claim 13, wherein the logic that organizes data access to the database among a plurality of business entities includes:

logic that retrieves data about a user;

logic that packages the data into a cross-functional data object;

logic that retrieves a request for data from one of a plurality of business objects; and

logic that directs the business object to the data object such that the business object retrieves the entire data object, wherein the business object selects the data from the data object.

17. A system as recited in claim 13, wherein the logic that retrieves multiple business objects across a network in one access operation includes:

logic that provides a business object and a plurality of remaining objects on a persistent store;

logic that receives a request for the business object;

logic that establishes which of the remaining objects are related to the business object;

logic that retrieves the related objects and the business object from the persistent store in one operation;

logic that determines how the retrieved related objects relate to the business object and each other; and

logic that instantiates a graph of relationships of the business and related objects in memory.

18. A system as recited in claim 13, wherein the logic that translates the object value to and from the database value utilizing a database includes:

logic that provides a database;

logic that determines a conversion process for converting an object attribute to and from a database value;

logic that encapsulates the conversion process in an attribute converter;

logic that directs a first object attribute to the attribute converter for conversion to a first database value; and

logic that directs a second database value to the attribute converter for conversion to a second object attribute.