Method and Apparatus for Changing Software Components in an Information Handling System

• US 20080196024A1
• Filed: 02/08/2007
• Published: 08/14/2008
• Est. Priority Date: 02/08/2007
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Monroe, Kevin William, Fried, Eric Philip, Barfield, Janel Guillory, Lampitt, Joseph Vernon
• Application Number:
  US11/672,577
• Publication Number:
  US 20080196024A1
• Time in Patent Office: Days
• US Class Current: 717/177
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A client information handling system (IHS) includes a dependency database that stores both installation dependency information and operational dependency information for installed software components and candidate software components. The client IHS also includes a request handler that, in response to a request to change the software configuration of the IHS, checks the dependency database for conflicts between a candidate software component and both installation and operational dependencies that the dependency database stores.

Claims

1. A method for changing a software configuration of an information handling system (IHS), the method comprising:

installing a plurality of software components in the IHS, thus providing the IHS with a first software configuration including installed software components;

storing in the IHS a local database including installation dependencies and operational dependencies of installed software components and candidate software components;

receiving, by a request handler in the IHS, a request to change the first software configuration of the IHS to a second software configuration; and

checking, by the request handler, the local database to determine if the request to change the first software configuration to the second software configuration conflicts with an installation dependency or an operational dependency, the request handler preventing the second software configuration if the request handler finds a conflict, the request handler allowing the second software configuration if the request handier finds no conflict.

2. The method of claim 1, wherein the request to change is one of a request to install a candidate software component on the IHS, a request to update a software component already installed on the IHS with a candidate component, and a request to remove a software component already installed on the IHS.

3. The method of claim 1, wherein the plurality of software components includes a software application.

4. The method of claim 1, further comprising updating the local database with installation dependencies and operational dependencies prior to the checking step.

5. The method of claim 4, wherein the IHS performs the updating step in response to receipt of the request for change.

6. The method of claim 4, wherein the IHS periodically monitors a master dependency database in a server IHS for updates to the installation and operational dependencies in the local database.

7. The method of claim 1, wherein the installation and operational dependencies include one of a positive dependency and a negative dependency.

8. The method of claim 2, further comprising providing a notice, by the request handler, that the candidate software component conflicts with an installation dependency or an operational dependency when the request handler finds a conflict.

9. The method of claim 1, wherein the request to change is a request to install a candidate software component, and the checking step includes preventing installation of the candidate software component if the request handler finds a conflict, the request handler allowing installation of the candidate software component if the request handler finds no conflict.

10. An information handling system (IHS), comprising:

a processor;

a memory, coupled to the processor;

a data store, coupled to the processor, the data store including;

a plurality of installed software components that provide the IHS with a first software configuration;

a local database including installation dependencies and operational dependencies of installed software components and candidate software components; and

a request handler that receives a request to change the first software configuration of the IHS to a second software configuration, the request handler checking the local database to determine if the request to change the first software configuration to the second software configuration conflicts with an installation dependency or an operational dependency, the request handler preventing the second software configuration if the request handler finds a conflict, the request handler allowing the second software configuration if the request handler finds no conflict.

11. The IHS of claim 10, wherein the request to change is one of a request to install a candidate software component on the IHS, a request to update a software component already installed on the IHS with a candidate component, and a request to remove a software component already installed on the IHS.

12. The IHS of claim 10, wherein the plurality of software components includes a software application.

13. The IHS of claim 10, wherein the request handler updates the local database with installation dependencies and operational dependencies.

14. The IHS of claim 13, wherein the IHS periodically monitors a master dependency database in a server IHS for updates to the installation and operational dependencies in the local database.

15. The IHS of claim 10, wherein the installation and operational dependencies include one of a positive dependency and a negative dependency.

16. The IHS of claim 10, further comprising a display on which the request handler provides a notice that the candidate software component conflicts with an installation dependency or an operational dependency when the request handler finds a conflict.

17. The IHS of claim 11, wherein the request to change is a request to install a candidate software component, the request handler preventing installation of the candidate software component if the request handler finds a conflict, the request handler allowing installation of the candidate software component if the request handler finds no conflict.

18. A computer program product stored on a computer operable medium for handling updates to a software configuration of an information handling system (IHS), the computer program product comprising:

a local database including installation dependencies and operational dependencies of installed software components and candidate software components; and

a request handler including instructions for receiving a request to change a first software configuration of the IHS to a second software configuration, the request handler checking the local database to determine if the request to change the first software configuration to the second software configuration conflicts with an installation dependency or an operational dependency, the request handler preventing the second software configuration if the request handler finds a conflict, the request handler allowing the second software configuration if the request handler finds no conflict.

19. The computer program product of claim 18, wherein the request handler includes instructions for updating the local database with installation dependencies and operational dependencies.

20. The computer program product of claim 18, wherein the request handler includes instructions for periodically monitoring a master dependency database in a server IHS for updates to the installation and operational dependencies in the local database.