Optimal component installation

• US 20050120344A1
• Filed: 12/02/2003
• Published: 06/02/2005
• Est. Priority Date: 12/02/2003
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jemiolo, Daniel Everett, Barta, Attila, Huddleston, Richard D., Asare, Kwasi Addo
• Application Number:
  US10/725,612
• Publication Number:
  US 20050120344A1
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 8/61 Installation

Abstract

A system for installing application components in a target platform can include a component installation engine configured to install application components and respective dependencies over a component distribution system. A script processor can be coupled to the engine and programmed to parse target specific installation scripts to identify both a listing of dependencies for the application components and at least one specified relationship between the application components and individual ones of the respective dependencies. Finally, a requirements verification processor can be programmed to enforce both target platform requirements for installing the application components and the at least one specified relationship prior to installing the application components.

Claims

1. A component installation method comprising the steps of:

identifying target platform requirements for installation a subject application component within a target specific installation script;

further identifying a listing of dependencies for said subject application and at least one specified relationship between said subject application and individual ones of said dependencies;

enforcing both said target platform requirements and said at least one specified relationship prior to installing said subject application component; and

,

aborting said installation where either one of said target platform requirements and said at least one specified relationship cannot be enforced.

2. The method of claim 1, wherein said further identifying step comprises the step of further identifying a listing of dependencies for said subject application and at least one specified relationship between said subject application and individual ones of said dependencies, wherein said at least one specified relationship is a relationship selected from the group consisting of a containment relationship, a usage relationship, a contradictory relationship and an equivalence relationship.

3. The method of claim 1, wherein said enforcing step comprises the steps of:

determining whether all required ones of said dependencies can be accessed in said target platform; and

,

for each required one of said dependencies which cannot be accessed in said target platform, locating and installing said required one of said dependencies in said target platform.

4. The method of claim 3, wherein said determining step comprises the step of querying a registry of installed components in said target platform to identify components which have been installed in said target platform.

5. The method of claim 3, wherein said enforcing step further comprises the step of updating dated ones of said required ones of said dependencies which can be accessed in said target platform with updated versions of said required ones of said dependencies.

6. The method of claim 3, wherein said enforcing step further comprises the step of patching flawed ones of said required ones of said dependencies which can be accessed in said target platform with updated versions of said required ones of said dependencies.

7. A system for installing application components in a target platform, the system comprising:

a component installation engine configured to install application components and respective dependencies over a component distribution system;

a script processor coupled to said engine and programmed to parse target specific installation scripts to identify both a listing of dependencies for the application components and at least one specified relationship between the application components and individual ones of said respective dependencies; and

,

a requirements verification processor programmed to enforce both target platform requirements for installing the application components and said at least one specified relationship prior to installing the application components.

8. The system of claim 7, wherein said at least one specified relationship comprises a relationship selected from the group consisting of a containment relationship, a usage relationship, a contradictory relationship and an equivalence relationship.

9. The system of claim 7, wherein said component installation engine further comprises a communicative coupling to a repository of updated ones of said dependencies.

10. A machine readable storage having stored thereon a computer program for component installation, the computer program comprising a routine set of instructions which when executed by the machine cause the machine to perform the steps of:

identifying target platform requirements for installation a subject application component within a target specific installation script;

further identifying a listing of dependencies for said subject application and at least one specified relationship between said subject application and individual ones of said dependencies;

enforcing both said target platform requirements and said at least one specified relationship prior to installing said subject application component; and

,

aborting said installation where either one of said target platform requirements and said at least one specified relationship cannot be enforced.

11. The machine readable storage of claim 10, wherein said further identifying step comprises the step of further identifying a listing of dependencies for said subject application and at least one specified relationship between said subject application and individual ones of said dependencies, wherein said at least one specified relationship is a relationship selected from the group consisting of a containment relationship, a usage relationship, a contradictory relationship and an equivalence relationship.

12. The machine readable storage of claim 10, wherein said enforcing step comprises the steps of:

determining whether all required ones of said dependencies can be accessed in said target platform; and

,

for each required one of said dependencies which cannot be access in said target platform, locating and installing said required one of said dependencies in said target platform.

13. The machine readable storage of claim 12, wherein said determining step comprises the step of querying a registry of installed components in said target platform to identify components which have been installed in said target platform.

14. The machine readable storage of claim 12, wherein said enforcing step further comprises the step of updating dated ones of said required ones of said dependencies which can be accessed in said target platform with updated versions of said required ones of said dependencies.

15. The machine readable storage of claim 12, wherein said enforcing step further comprises the step of patching flawed ones of said required ones of said dependencies which can be accessed in said target platform with updated versions of said required ones of said dependencies.