Multi-object identifier system and method for information service pattern environment

• US 6,539,396 B1
• Filed: 08/31/1999
• Issued: 03/25/2003
• 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): Mizrahi, Diane D.
• Assistant Examiner(s): PARDO, THUY N
• Application Number:
  US09/386,714
• Time in Patent Office: 1,302 Days
• Field of Search: 707/103, 707/102, 707/101, 707/202, 707/203, 711/118
• US Class Current: 707/769
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/944 Business related
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A system and method for implementing an association of business objects without retrieving said objects from a database on which they are stored. A business object in the business cache is provided and an instance of an associated object is stored on a database. An association of the business object with the instance of the associated object is determined. An object identifier is generated containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, wherein the object identifier includes a unique row identifier, an identifier generated by a utility, and a unique string generated from one or more attributes. The object identifier is loaded when the business object starts. A location of the instance of the associated object on the database is determined from the object identifier and the instance of the associated object is retrieved from the database.

Claims

1. A method for implementing an association of business objects without retrieving the business objects from a database on which the business objects are stored, comprising the steps of:

(a) providing a business object;

in the business cache

(b) storing an instance of an associated object in a database;

(c) determining an association of the business object with the instance of the associated object;

(d) generating an object identifier containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, wherein the object identifier includes at a unique row identifier generated by the database, an identifier generated by a utility, and a unique string generated from one or more attributes;

(e) loading the object identifier when the business object starts;

(f) determining a location of the instance of the associated object in the database from the object identifier; and

(g) retrieving the instance of the associated object from the database.

2. A method as recited in claim 1, wherein the object identifier is used to provide a unique identity that is required for implementing caching and identity management.

3. A method as recited in claim 1, further comprising the step of providing different types of business objects, wherein a different class of object identifier is generated for each type of business object.

4. A method as recited in claim 1, wherein the steps of determining a location of the instance and retrieving the instance of the associated object include taking the object identifier as an argument and returning the instance of the associated object.

5. A computer program embodied on a computer readable medium for implementing an association of business objects without retrieving the business objects from a database on which the business objects are stored, comprising:

(a) a code segment that provides a business object;

in the business cache

(b) a code segment that stores an instance of an associated object on a database;

(c) a code segment that determines an association of the business object with the instance of the associated object;

(d) a code segment that generates an object identifier containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, wherein the object identifier includes a unique row identifier generated by the database, an identifier generated by a utility, and a unique string generated from one or more attributes;

(e) a code segment that loads the object identifier when the business object starts;

(f) a code segment that determines a location of the instance of the associated object on the database from the object identifier; and

(g) a code segment that retrieves the instance of the associated object from the database.

6. A computer program as recited in claim 5, wherein the object identifier is used to provide a unique identity that is required for implementing caching and identity management.

7. A computer program as recited in claim 5, wherein the object identifier includes at least one of a unique row identifier generated by the database, an identifier generated by a utility, and a unique string generated from one or more attributes.

8. A computer program as recited in claim 5, further comprising a code segment that provides different types of business objects, wherein a different class of object identifier is generated for each type of business object.

9. A computer program as recited in claim 5, wherein the code segments that determine a location of the instance and retrieve the instance of the associated object include taking the object identifier as an argument and returning the instance of the associated object.

10. A system for implementing an association of business objects without retrieving the business objects from a database on which the business objects are stored, comprising:

(a) logic that provides a business object;

in the business cache

(b) logic that stores an instance of an associated object on a database;

(c) logic that determines an association of the business object with the instance of the associated object;

(d) logic that generates an object identifier containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, wherein the object identifier includes a unique row identifier generated by the database, an identifier generated by a utility, and a unique string generated from one or more attributes;

(e) logic that loads the object identifier when the business object starts;

(f) logic that determines a location of the instance of the associated object on the database from the object identifier; and

(g) logic that retrieves the instance of the associated object from the database.

11. A system as recited in claim 10, wherein the object identifier is used to provide a unique identity that is required for implementing caching and identity management.

12. A system as recited in claim 10, wherein the object identifier includes at least one of a unique row identifier generated by the database, wherein the object identifier includes a unique row identifier generated by the database, an identifier generated by a utility, and a unique string generated from one or more attributes, an identifier generated by a utility, and a unique string generated from one or more attributes.

13. A system as recited in claim 10, further comprising logic that provides different types of business objects, wherein a different class of object identifier is generated for each type of business object.

14. A system as recited in claim 10, wherein the logic that determines a location of the instance and retrieves the instance of the associated object include taking the object identifier as an argument and returning the instance of the associated object.

15. A method for implementing an association of business objects in a computer system having an object cache and a database without retrieving the business objects from the database on which the business objects are stored, comprising:

providing a parent business object and at least a first and a second child business object in the database;

in the business cache

retrieving the instance of the parent business object from the database and storing it in the object cache;

generating a first object identifier that uniquely references the first child object stored in the database;

storing the first object identifier in the parent business object generating a second object identifier that uniquely references the second child object stores in the database;

and storing the second object identifier in the parent business object.