System and method for configuring software for distribution

• US 6,983,449 B2
• Filed: 03/15/2002
• Issued: 01/03/2006
• Est. Priority Date: 03/15/2002
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Electronic Data Systems Corporation (Perspecta, Inc.)
• Inventors: Newman, Patrick
• Primary Examiner(s): Das, Chameli C.
• Application Number:
  US10/099,331
• Publication Number:
  US 20050144619A1
• Time in Patent Office: 1,390 Days
• Field of Search: 717172-178, 717106-107, 717/121, 717/103, 717/120, 717/122, 709/221, 714/38, 703/27, 707/200, 707/203, 707/204, 715/500.1
• US Class Current: 717/121
• CPC Class Codes: G06F 8/61 Installation

Abstract

A method for distributing software is provided. The method includes configuring a first software system of a software suite, such as by installing it on a processor. A first set of configuration data associated with the first software system is then stored. A second software system of the software suite is then configured, and a second set of configuration data associated with the second software system is then stored. Conflict resolution rules are then applied to the first set of configuration data and the second set of configuration data. The first set of configuration data and the second set of configuration data are then compared to determine whether any conflicts exist, and the first set of configuration data and the second set of configuration data are assembled for installation on one or more processors if no conflicts exist.

Claims

1. A computer implemented method for distributing software comprising:

configuring a first software system of a software suite;

storing a first set of configuration data associated with the first software system;

configuring a second software system of the software suite;

storing a second set of configuration data associated with the second software system;

applying conflict resolution rules to the first set of configuration data and the second set of configuration data;

determining whether a conflict exists by comparing the first set of configuration data and the second set of configuration data;

creating a new conflict resolution rule if it is determined that a conflict exists;

applying the new conflict resolution rule to the first set of configuration data and the second set of configuration data; and

assembling the first set of configuration data and the second set of configuration data for installation on one or more remote processors.

2. The method of claim 1 wherein determining whether any additional conflicts exists by comparing the first set of configuration data and the second set of configuration data includes one or more of a set comprising determining whether one or more of a group comprising a hardware dependency conflict, a software dependency conflict, a file conflict, and a settings conflict exists.

3. The method of claim 1 wherein the first set of configuration data includes one or more of a set comprising file directory data, registry setting data, hardware dependency data, dynamic link library file data, executable file data, and software dependency data.

4. The method of claim 1 further comprising:

determining whether the conflict is between configuration data for a required software system and configuration data for an optional software system; and

resolving the conflict by replacing the configuration data for the optional software system with the configuration data for the required software system.

5. The method of claim 4 wherein resolving the conflict by replacing the configuration data for the optional software system with the configuration data for the required software system further comprises replacing one or more of a group comprising file directory data, registry setting data, hardware dependency data, dynamic link library file data, executable file data, or software dependency data for the optional software system with corresponding file directory data, registry setting data, hardware dependency data, dynamic link library file data, executable file data, or software dependency data of the required software system.

6. The method of claim 1 further comprising:

determining whether the conflict between the first set of configuration data and the second set of configuration data requires third party action; and

tracking a status of the third party action.

7. The method of claim 1 further comprising:

identifying a conflict between the first set of configuration data and the second set of configuration data;

notifying a third party of the identified conflict; and

receiving a rule for addressing the identified conflict from the third party.

8. A computer implemented system for distribution comprising:

two or more software components configured for installation;

a suite assembly system receiving the two or more software components and generating a software suite for installation on at least one remote device comprising at least;

a first installation component comprising one or more of a first group comprising first dependencies, first files and first settings; and

a second installation component comprising one or more of a second group comprising second dependencies, second files and second settings; and

wherein the first dependencies and second dependencies include no conflicting dependencies, the first files and the second files include no conflicting files, and the first settings and the second settings include no conflicting settings;

the suite assembly system comprises a conflict verification system determining whether any conflicts exist between the first dependencies and the second dependencies, the first files and the second files, and the first settings and the second settings;

the suite assembly system further comprises a new rules system generating one or more new conflict resolution rules if its is determined that a conflict exists; and

the one or more new conflict resolution rules are applied to the first installation component and the second installation component.

9. The system of claim 8 wherein the suite assembly system further comprises a component suite assembly configuring the first installation component and the second installation component for distribution.

10. The system of claim 8 wherein the suite assembly system further comprises a conflict resolution system resolving conflicts between the first dependencies and the second dependencies, the first files and the second files, and the first settings and the second settings.

11. The system of claim 8 wherein the suite assembly system further comprises a files/settings/dependencies system resolving conflicts between two or more sets of one or more of the group comprising files, settings, and dependencies.

12. The system of claim 8 wherein the suite assembly system further comprises an external system interface tracking a component correction by a third party.

13. The system of claim 8 wherein the first installation component is one of a required component or an optional component.

14. The system of claim 8 wherein the suite assembly system further comprises an external system interface for notifying a third party of a conflict and receiving a rule for resolving the conflict.