Method and apparatus for shared management information via a common repository

• US 5,787,437 A
• Filed: 10/29/1996
• Issued: 07/28/1998
• Est. Priority Date: 10/29/1996
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Company (HP Inc.)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Bartz, Thomas G., Potterveld, Robert A.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Mizrahi, Diane D.
• Application Number:
  US08/741,152
• Time in Patent Office: 637 Days
• Field of Search: 395/601-9, 395/614, 707/103
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: Y02P 90/80 Management or planning
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A method and associated data constructs for sharing management information, stored in a common repository among multiple application programs. The present invention provides methods and structures for maintaining consistency and integrity of information shared among multiple application programs while allowing easier integration of management information relating to disparate aspects of enterprise management. Standard server programs are provided to serve client application programs by manipulating and retrieving information stored in the common repository. A meta-schema defines the structure of information stored in the common repository and permits extension of the information to incorporate data relevant to new application programs. In addition, tools are defined to permit developers to automate the creation of new server programs which manipulate and retrieve information stored in the common repository. The automatic generation of new server programs helps retain the consistency and integrity of management information achieved by application of the meta-schema structures.

Claims

1. A computer based data management system for managing information regarding objects, each object belonging to an object class and utilized by application programs;

said data management system comprising;

memory means for storing said information;

a meta-schema for defining standard structures for storing said information managed by said system in said memory means, said information comprising attributes of said objects and relationships between said objects;

a plurality of integrated server programs for servicing requests received by said plurality of integrated server programs from said application programs to manipulate said information regarding objects stored in said memory means in accordance with the standard structures defined by said meta-scheme and in accordance with standard object class definitions; and

server program generation means, independent of the application programs, but cooperative with said meta-schema and standard object class definitions, for generating additional ones of said server programs and integrating said additional ones of said server programs with said plurality of integrated server programs so as to maintain information integrity within the memory means and reduce unintended duplication of information within the memory means.

2. The data management system of claim 1 wherein said server program generation means is responsive to said meta-schema to control the structure of server programs generated by said server program generation means.

3. The data management system of claim 1 further comprising:

database schema generation means for generating database schemas used by said server programs and by said application programs to manipulate information stored in said memory means.

4. The data management system of claim 3 wherein said database schema generation means is responsive to said meta-schema to control the structure of said database schemas generated by said database schema generation means.

5. A computer based data management method for managing information regarding objects, each belonging to an object class and utilized by application programs;

said data management method comprising the steps of;

(a) providing a memory means for storing said information;

(b) providing a meta-schema;

(c) defining, according to the meta-schema, standard structures for storing said information managed by said method in said memory means, said information comprising attributes of said objects and relationships between said objects;

(d) providing an object model;

(e) defining, according to the object model, standard object classes of objects utilized by said application programs according to the structure defined by said meta-schema;

(f) providing a plurality of integrated server programs;

(g) operating said server programs to service application program requests to manipulate said information regarding objects stored in said memory means in accordance with the standard structures provided by said meta-schema and in accordance with the standard object class definitions;

(h) generating additional ones of said server programs, independently of the application programs, but cooperatively with said meta-schema and with said standard object class definitions; and

(i) integrating said additional ones of said server programs with said plurality of integrated server programs so as to maintain information integrity within the memory means and reduce unintended duplication of information within the memory means.

6. The data management method of claim 5 wherein the server program generation step is responsive to said meta-schema to control the structure of server programs generated by said server program generation means.

7. The data management method of claim 5 further comprising the step of:

generating database schemas used by said server programs and by said application programs to manipulate information stored in said memory means.

8. The data management method of claim 7 wherein the database schema generation step is responsive to said meta-schema to control the structure of the generated database schemas.

9. In a computer based environment comprising multiple application programs needing access to information stored in a common repository, access to the common repository being provided via a database management system, apparatus for ensuring that information in the common repository is stored and manipulated in a consistent manner, thereby facilitating improved data integrity and improved sharing of information between the multiple application programs, comprising:

a) a meta-schema defining rules and constructs pertaining to storage and manipulation of information stored in the common repository;

b) a plurality of integrated server programs through which all of the multiple application programs gain access to the database management system, each server program providing access, via the database management system, to a particular managed aspect of information stored in the common repository, each server program adhering to the rules and constructs of the meta-schema;

c) means for generating;

i) additional server programs, said additional server programs being integrated with the plurality of integrated server programs, said additional server programs providing access, via the database management system, to additional managed aspects of information stored in the common repository, and said additional server programs adhering to the rules and constructs of the meta-schema;

ii) DBMS schemas, said DBMS schemas adhering to the rules and constructs of the meta-schema; and

iii) code segments, adhering to the rules and constructs of the meta-schema, which can be incorporated into one or more application programs which require access, via the additional server programs and the database management system, to the additional managed aspects of information stored in the common repository; and

d) means for incorporating the DBMS schemas into DBMS tables of the database management system.

10. Apparatus for developing new server programs when it is determined that an application program requires storage or manipulation of information in a common repository which is not supported by standard server programs, comprising:

a) a server generation tool having an input for accepting a preliminary object class definition of information to be manipulated by an application program;

an input for accepting a meta-schema; and

outputs for generating, in response to its inputs, database (DBMS) schemas for the information to be manipulated;

an IDL which adheres to the constructs and rules defined by the meta-schema; and

first source code segments for a server program to perform basic manipulations of objects defined by the preliminary object class definition;

b) an IDL compiler having an input for accepting the IDL; and

an output for generating second source code segments for a server program to perform basic manipulations of objects defined by the preliminary object class definition; and

c) a build server process which compiles the first and second source code segments for a server program to create an executable server program.

11. Apparatus as in claim 10, wherein the preliminary IDL object class definition is compiled by the IDL compiler to generate source code segments to be integrated into an application program to access the executable server program.

12. Apparatus as in claim 10, wherein the first and second source code segments for a server program only provide for creating, destroying, updating and retrieving information.

13. In a system wherein application programs access information stored in a common repository via defined, integrated server programs, a method of providing an application program with access to information in the common repository which is not supported by the defined server programs, the method comprising the steps of:

a) generating an IDL, a skeleton server, and DBMS schemas in response to a preliminary object class IDL and standards defined by a meta-schema;

compiling the IDL;

c) generating an executable server from the compiled IDL and the skeleton server;

d) creating a DBMS from the DBMS schemas; and

e) providing, via the executable server, access to the information in the common repository which is not supported by the defined server programs.