Dynamic component activation method using a relational database as the repository for registration information

• US 6,778,990 B2
• Filed: 07/27/2001
• Issued: 08/17/2004
• Est. Priority Date: 07/27/2001
• Status: Expired due to Fees

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Hunt, Joseph R, Garcia, Julio Cesar, OʼKeefe-Hyser, Amy
• Primary Examiner(s): Corrielus, Jean M.
• Application Number:
  US09/916,545
• Publication Number:
  US 20030023599A1
• Time in Patent Office: 1,117 Days
• Field of Search: 717/107, 717/108, 717/5, 717/6, 707/10, 707/104, 705/59, 709/315, 709/332
• US Class Current: 719/315
• CPC Class Codes: G06F 9/4488 Object-oriented
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: Y10S 707/954 Relational
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/966 Distributed

Abstract

A method for allowing dynamic component activation using a database as a repository for registration information is disclosed. This method uses a Component Activation Manager (CAM), which is a singleton object that maps unique component ID'"'"'s to a Factory Creation Function (FCF). A purpose of the FCF is to create and register factories for the objects contained in a dynamic library. The factories created with the FCF are also registered with a database connection created by the CAM. Using this approach, the application only needs to create the CAM object, request a connection and then request a factory for the objects it needs. The CAM and the database connection find the dynamic library and the associated object factories through the use of database tables that contain a map of unique component ID'"'"'s and object FCF addresses.

Claims

1. A method for dynamic component activation using one or more databases as a repository for registration information in an application in a heterogeneous and distributed computing environment, comprising:

launching the application;

creating and initializing a Component Activation Manager;

opening a database connection using the Component Activation Manager;

using the database connection to request a functionality that is encapsulated in an object factory;

using the Component Activation Manager and the database connection to find and return the requested functionality; and

loading the requested functionality to extend the application,

wherein opening the database connection using the Component Activation Manager further comprises a database connection object, said database connection object containing a connection table, mapping a plurality of object identifiers to a plurality of factories for the database connection object, and wherein using the Component Activation Manager and the database connection to find and return the requested object factory, further comprises;

the database connection object looking up the requested object factory in the connection table;

the database connection object returning the requested object factory if said requested object factory is in the connection table;

the database connection object sending a message to the Component Activation Manager to obtain a Function Creation Factory for the requested object if said requested object factory is not in the connection table;

if requested factory object is not associated with the current database connection, the database connection object sending a message to the dynamic library to create an instance of the object factory using the Function Creation Factory; and

if requested factory object is not associated with the current database connection, the database connection object receiving the instance of the object factory.

2. The method of claim 1, wherein creating and initializing the Component Activation Manager occurs during launching of the distributed and heterogeneous application.

3. The method of claim 2, wherein the Component Activation Manager is contained in one or more dynamic libraries.

4. The method of claim 1, wherein the heterogeneous and distributed application resides in a Microsoft Windows NT®

operating system.

5. The method of claim 1, wherein the heterogeneous and distributed application resides in a Unix operating system.

6. The method of claim 1, wherein the heterogeneous and distributed application contains a plurality of elements using a Microsoft Windows NT ®

operating system, and a plurality of elements using a Unix operating system.

7. The method of claim 1, wherein the one or more databases may be remote databases.

8. The method of claim 1, wherein the one or more databases may be relational databases.

9. The method of claim 1, wherein each object identifier of the plurality of object identifiers are unique.

10. The method of claim 1, wherein the plurality of object identifiers is a plurality of class identifiers (ID)'"'"'s in an object-oriented environment.

11. The method of claim 1, wherein the Factory Creation Function creates a plurality of images in memory of the plurality of objects referred to in the connection table, said plurality of images then being used as a factory for the plurality of objects.

12. The method of claim 11, wherein the message between the database connection object and the Component Activation Manager contains a class ID of the requested factory object.

13. The method of claim 1, the database connection object sending a message to the Component Activation Manager to obtain the Factory Creation Function for the requested object if said requested object factory is not in the connection table, further comprising:

the Component Activation Manager CAM determining whether it has the Factory Creation Function for the requested object;

if the Component Activation Manager does not have the Factory Creation Function for the requested object, the Component Activation Manager querying the database for the current connection to obtain the dynamic library corresponding to the class ID;

if the Component Activation Manager does not have the Factory Creation Function for the requested object, the Component Activation Manager sending a message to the dynamic library to load the library and obtain the Factory Creation Function; and

the Component Activation Manager returning the Factory Creation Function to the database connection object.

14. The method of claim 13, wherein the Component Activation Manager determining whether it has the Factory Creation Function for the requested object, further comprises looking in a table that maps a plurality of class ID'"'"'s to a plurality of Factory Creation Function addresses.

15. A method for dynamic component activation using one or more databases as the repository for registration information in a heterogeneous and distributed application, comprising:

(a) launching the application;

(b) creating and initializing a Component Activation Manager object;

(c) creating and initializing a database connection object;

(d) the application opening a database connection using the Component Activation Manager object;

(e) the application requesting an object factory using the database connection object;

(f) the database connection object looking up the requested object factory in the connection table

(g) the database connection object returning the requested object factory if said requested object factory is in the connection table;

(h) if said requested object factory is not in the connection table then;

the Component Activation Manager determining whether it has the Factory Creation Function for the requested object;

if the Component Activation Manager does not have the Factory Creation Function for the requested object, the Component Activation Manager querying the database for the current connection to obtain the dynamic library corresponding to the class ID and the Component Activation Manager sending a message to the dynamic library to load the library and obtain the Factory Creation Function; and

the Component Activation Manager returning the Factory Creation Function to the database connection object; and

(i) if requested factory object is not associated with the current database connection;

the database connection object sending a message to the dynamic library to create an instance of the object factory using the Factory Creation Function;

the database connection object receiving the instance of the object factory; and

loading the requested object factory to extend the functionality of the application.