Dependency management when upgrading application components

• US 8,312,446 B2
• Filed: 12/17/2002
• Issued: 11/13/2012
• Est. Priority Date: 12/17/2002
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Kaminsky, David Louis, Ogle, David M., Telford, Richard Dean
• Primary Examiner(s): NGUYEN BA, HOANG VU A
• Application Number:
  US10/321,356
• Publication Number:
  US 20040117783A1
• Time in Patent Office: 3,619 Days
• Field of Search: 717168-173, 717174-178, 715/235, 715/237, 709/223, 709/209, 703/20, 707/106.1
• US Class Current: 717/175
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

An autonomic component installation system. The system can include a catalog of host components installed within a computing system and an autonomic installer coupled to the catalog and programmed to determine, when installing an upgraded component, whether the upgraded component provides component capabilities required by the host components in the catalog. The catalog can include both host components and respective publicly accessible data, method implementations and method prototypes provided by the host components. Consequently, the autonomic installer can determine whether the upgraded component will have access to required publicly accessible data and method implementations. The autonomic installer further can be configured to determine whether modifications included in the upgraded component have caused changes in associated method prototypes which differ from the method prototypes in the catalog. Finally, a machine-readable ReadMe file processor can be coupled to the autonomic installer to identify the required publicly accessible data and methods implementations.

Claims

1. An autonomic component installation system comprising:

a catalog of host components installed within a computing system;

an autonomic installer coupled to said catalog and programmed to determine, when installing an upgraded component, whether said upgraded component provides component capabilities required by the host components in said catalog.

2. The autonomic component installation system of claim 1, wherein said catalog comprises entries of host components and respective publicly accessible data, method implementations and method prototypes provided by said host components.

3. The autonomic component installation system of claim 2, wherein said autonomic installer comprises an autonomic installer coupled to said catalog to determine when installing an upgraded component whether said upgraded component will have access to required ones of said publicly accessible data and method implementations, and whether modifications included in said upgraded component have caused changes in associated method prototypes which differ from said method prototypes in said catalog.

4. The autonomic component installation system of claim 3, further comprising a machine readable ReadMe file processor coupled to said autonomic installer and configured to identify said required ones of said publicly accessible data and methods implementations.

5. The autonomic component installation system of claim 4, wherein said machine readable ReadMe file is an XML formatted file.

6. The autonomic component installation system of claim 4, further comprising:

a code analysis engine configured to identify within component code, publicly accessible data utilized by said component code, dependent methods utilized by said component code, and methods and data provided by said component code; and

,

a machine readable ReadMe file production module coupled both to said code analysis engine and also to an integrated development environment configured to create said upgraded component, said production module creating said machine readable ReadMe file based upon said identified publicly accessible data utilized by said component code, dependent methods utilized by said component code, and methods and data provided by said component code.

7. The autonomic component installation system of claim 6, wherein said code analysis engine comprises a byte-code analysis engine.

8. The autonomic component installation system of claim 6, wherein said code analysis engine comprises a source-code analysis engine.

9. A dependency management method comprising the steps of:

parsing a machine readable ReadMe file associated with an upgraded component to an application to identify both data and method dependencies of said upgraded component, and interface prototype information regarding methods implemented in said upgraded component; and

,

prior to installing said upgraded component, ensuring that said identified data and method dependencies can be accessed by said upgraded component upon installation of said upgraded component, and further ensuring that other components which rely upon said methods implemented in said upgraded component will not be affected by said installation in consequence of changes reflected by said interface prototype information.

10. The method of claim 9, wherein said step of ensuring comprises the steps of:

determining that at least one of said identified data and method dependencies are missing; and

,

locating and loading said at least one identified data and method dependency so that no one of said identified data and method dependencies remain missing.

11. The method of claim 9, wherein said step of further ensuring comprises the step of further ensuring by reference to a catalog of expected interface prototype information that other components which rely upon said methods implemented in said upgraded component will not be affected by said installation in consequence of changes reflected by said interface prototype information.

12. The method of claim 11, wherein said step of further ensuring comprises the steps of:

comparing said catalog of expected interface prototype information upon which other components rely to said methods implemented in said upgraded component to detect prototype mismatches; and

,

for each prototype mismatch detected, locating an upgrade to a corresponding one of said other components, and replacing said corresponding one of said other components with said located upgrade.

13. The method of claim 11, further comprising the steps of:

inspecting all components of said application to identify both required public data and methods, and also prototype information expected by said components for all invoked methods; and

,

storing said identified required public data and methods and prototype information in said catalog.

14. A machine readable storage having stored thereon a computer program for performing dependency management, said computer program comprising a routine set of instructions which when executed cause the machine to perform the steps of:

parsing a machine readable ReadMe file associated with an upgraded component to an application to identify both data and method dependencies of said upgraded component, and interface prototype information regarding methods implemented in said upgraded component; and

,

prior to installing said upgraded component, ensuring that said identified data and method dependencies can be accessed by said upgraded component upon installation of said upgraded component, and further ensuring that other components which rely upon said methods implemented in said upgraded component will not be affected by said installation in consequence of changes reflected by said interface prototype information.

15. The machine readable storage of claim 14, wherein said step of ensuring comprises the steps of:

determining that at least one of said identified data and method dependencies are missing; and

,

locating and loading said at least one identified data and method dependency so that no one of said identified data and method dependencies remain missing.

16. The machine readable storage of claim 14, wherein said step of further ensuring comprises the step of further ensuring by reference to a catalog of expected interface prototype information that other components which rely upon said methods implemented in said upgraded component will not be affected by said installation in consequence of changes reflected by said interface prototype information.

17. The machine readable storage of claim 16, wherein said step of further ensuring comprises the steps of:

comparing said catalog of expected interface prototype information upon which other components rely to said methods implemented in said upgraded component to detect prototype mismatches; and

,

for each prototype mismatch detected, locating an upgrade to a corresponding one of said other components, and replacing said corresponding one of said other components with said located upgrade.

18. The machine readable storage of claim 16, further comprising the steps of:

inspecting all components of said application to identify both required public data and methods, and also prototype information expected by said components for all invoked methods; and

,

storing said identified required public data and methods and prototype information in said catalog.