Method for managing a plurality of data processes residing in heterogeneous data repositories

• US 5,966,707 A
• Filed: 12/02/1997
• Issued: 10/12/1999
• Est. Priority Date: 12/02/1997
• Status: Expired due to Term

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Van Huben, Gary Alan, Mueller, Joseph Lawrence
• Primary Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/982,724
• Time in Patent Office: 679 Days
• Field of Search: 707/10, 707/8, 707/102, 707/200, 395/200.31, 395/200.53, 395/840, 395/849, 395/682
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A Data Management System has a plurality of data managers and is provided with a plurality of data managers in one or more layers of a layered architecture The system performs with a data manager and with a user input via an API a plurality of processs on data residing in heterogeneous data repositories of the computer system including promotion, check-in, check-out, locking, library searching, setting and viewing process results, tracking aggregations, and managing parts, releases and problem fix data under management control of a virtual control reposisitory having one or more physical heterogeneous repositories. The system provides for storing, accessing, tracking data residing in the one or more data repositories managed by the virtual control repository. User Interfaces provide a combination of command line, scripts, GUI, Menu, WebBrowser maps of the user'"'"'s view to a PFVL paradigm. Configurable Managers include a query control repository for existence of peer managers and provide logic switches to dynamically interact with peers. A control repository layer provides a common process interface across all managers data view maps to a relational table paradigm and maps control repository layer (CRL) calls to sequences of SQL queries. A command translator for a relations data base provides pass through of SQL queries. Table files map SQL Queries into a set of FILE I/O'"'"'s with appropriate inter I/O processing, and meta data maps SQL Queries into Meta data API calls with appropriate inter I/O processing. PFVL paradigm calls are mapped into DataManager(s)/Control Repository calls.

Claims

1. A method for a data management system having a plurality of data managers, comprising the steps of

providing said plurality of data managers in one or more layers of a layered architecture, and

performing with a data manager and with a user input via an API a plurality of processes on data residing in heterogeneous data repositories of said computer system including promotion, check-in, check-out, locking, library searching, setting and viewing process results, tracking aggregations, and managing parts, releases and problem fix data under management control of a virtual control repository having one or more physical heterogeneous repositories, and

storing, accessing, tracking data residing in said one or more data repositories managed by said virtual control repository, and

wherein said virtual control repository comprises virtual tables and all virtual control repository access functions are implemented as transactions constructed using a generic SOL-based structure, and

command translators are employed to map generic SQL-based virtual control repository transactions into any required command interface needed to interact with the corresponding physical implementation of said virtual control repository.

2. The method according to claim 1 wherein any type of data can be mapped into a package, Filetype, variance and a PFVL Level whereby within a variance there exists one or moire data objects of a given type residing at one or more levels with one or more versions.

3. The method according to claim 2 wherein packages are hierarchical and contain other Packages, and wherein a given package can contain any combination of data objects and/or packages.

4. The method according to claim 1 wherein said plurality of to claim 1 comprising a plurality of data managers are configurable and can be dynamically or statically combined as modules of a scalable system ranging up to a high-end enterprise wide DMS.

5. The method according to claim 1 wherein is provided a User Interface Layer for interaction with said user via said API which enables mapping of a methodology, process, use-model or environment into a generic PFVL paradigm using tools which can be manipulated by said user, including menus, GUIs, Web Browsers, command line interfaces, and scripts.

6. The method according to claim 1 wherein is provided with one or more DMS application layers which contains utilities that a user requires to interact with the DMS processes of promotion, check-in, check-out, locking, library searching, setting and viewing process results, tracking aggregations, and managing parts, releases and problem fix data.

7. The method according to claim 1 wherein data is stored in one or more data repositories constructed with one or more tools including simple directory trees, commercially available PDMs (storage engines), and the WWW and each repository may employ a common or unique storage and data access method.

8. The method according to claim 7 wherein each data object is classified by PFVL and unique File Reference regardless of the physical data repository in which the data object resides.

9. The method according to claim 6 wherein said DMS application layers contain applications, each of which is composed of one or more application modules which interact with the data managers in one or more ways of interaction including:

non-manager interaction;

single manager interaction;

multiple manager interaction; and

control repository access coupled with manager interaction.

10. The method according to claim 9 wherein said DMS applications and data manager functions can be accessed using a common API based on the PFVL paradigm whereby all functions require a minimum of package, Filetype, variance, and level but may permit additional optional parameters, and any combination of wildcards or placeholder characters may be used on any of the parameters.

11. The method according to claim 1 wherein complex applications are constructed using state tables to invoke pre-defined functions contained in one or more data managers thus permitting applications to be to be executed in an interpretive manner and allowing them to be customized or altered in the field without the need to recompile any object code.

12. The method according to claim 1 wherein said virtual control repository'"'"'s physical repositories include relational databases, object oriented databases, flat files, table formatted files, meta data files and proprietarily formatted files and said Control Repository classifies all data according to the PFVL paradigm.

13. The method according to claim 1 further comprising a scalable client/server interface permitting the DMS to use local services to run in a client-only mode and permitting a combination of local &

remote services to run in a fully secure distributed client/server mode.

14. The method according to claim 1 wherein said virtual control repository is accessed by an application via an access layer which segregates transactions used to store, access or modify CR information from the DMS Applications this permitting a library of transactions to be shared among a plurality of DMS Applications and wherein said transactions may reside within one or more Managers.