Automatic parallel non-dependent component deployment

• US 20050102665A1
• Filed: 11/10/2003
• Published: 05/12/2005
• Est. Priority Date: 11/10/2003
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jemiolo, Daniel E., Barta, Attila, Asare, Kwasi A., Huddleston, Richard
• Granted Patent: US 7,926,051 B2
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 8/61 Installation

Abstract

The methods, systems, data structures and computer program products for deploying software components are provided, including deploying components in an enterprise environment. Dependency relationships among components to be deployed are determined. Those components which are not dependent upon any other component may be installed first and substantially in parallel. Components which are dependent only upon the first installed components are next installed, substantially in parallel. Installation thus progresses until all components have been installed. By installing in parallel those components having a similar level of dependency, rather than installing all components sequentially, the deployment is more efficient and requires less time to complete.

Claims

1. A method for deploying software components on a computer system, comprising:

determining dependency relationships among components to be installed;

identifying a first group of the components to be installed, none of which is dependent upon any other component to be installed;

identifying a second group of the components to be installed, all of which are dependent only upon a component in the first group;

installing the components of the first group substantially in parallel; and

after the installation of the components of the first group, installing the components of the second group substantially in parallel.

2. The method of claim 1, wherein determining dependency comprises accessing a semantic model comprising references among the components to be installed identifying deployment dependencies.

3. The method of claim 2, further comprising loading an installation package including the semantic model.

4. The method of claim 1, further comprising:

identifying a third group of the components to be installed, all of which are dependent only upon a component in the second group;

after the installation of the components of the second group, installing the components of the third group substantially in parallel.

5. The method of claim 1, wherein installing the components of the first and second groups comprises installing the components on a plurality of enterprise resources.

6. A system for installing software components, comprising:

means for determining dependency relationships among components to be installed;

means for identifying a first group of the components to be installed, none of which is dependent upon any other component to be installed;

means for identifying a second group of the components to be installed, all of which are dependent only upon a component in the first group;

means for installing the components of the first group substantially in parallel; and

after the installation of the components of the first group, installing the components of the second group substantially in parallel.

7. The system of claim 6, wherein the means for determining dependency comprises after the installation of the components of the first group, means for accessing a semantic model comprising references among the components to be installed identifying deployment dependencies.

8. The system of claim 7, further comprising means for loading, an installation package including the semantic model.

9. The system of claim 6, further comprising:

means for identifying a third group of the components to be installed, all of which are dependent only upon a component in the second group;

means for installing the components of the third group substantially in parallel after the installation of the components of the second group.

10. The system of claim 6, further comprising a data structure comprising references among the components to be installed identifying deployment dependencies.

11. The system of claim 10, further comprising means for accessing the data structure.

12. The system of claim 6, further comprising means for installing the components of the first and second groups across a plurality of enterprise resources.

13. A data structure associated with a software component installation package, comprising:

an entry for each component to be installed; and

references associated with a first component to be installed identifying each other component to be installed upon which the first component is dependent;

whereby the installation package installs the components in a sequence in accordance with the dependency references.

14. The data structure of claim 13, further comprising:

a first identifier identifying the components to be installed which are not dependent upon any other component to be installed; and

a second identifier identifying the components to be installed, all of which are dependent only upon a component in the first group;

whereby the installation package installs the components identified by the first identifier substantially in parallel and subsequently installs the components identified by the second identifier substantially in parallel.

15. A computer program product of a computer readable medium usable with a programmable computer, the computer program product having computer-readable code embodied therein for installing software -components, the computer-readable code comprising instructions for:

determining dependency relationships among components to be installed;

identifying a first group of the components to be installed, none of which is dependent upon any other component to be installed;

identifying a second group of the components to be installed, all of which are dependent only upon a component in the first group;

installing the components of the first group substantially in parallel; and

after the installation of the components of the first group, installing the components of the second group substantially in parallel.

16. The computer program product of claim 15, wherein the instructions for determining dependency comprises instructions for accessing a semantic model comprising references among the components to be installed identifying deployment dependencies.

17. The computer program product of claim 16, further comprising instructions for loading an installation package including the semantic model.

18. The computer program product of claim 15, further comprising instructions for:

identifying a third group of the components to be installed, all of which are dependent only upon a component in the second group;

installing the components of the third group substantially in parallel after the installation of the components of the second group.

19. The computer program product of claim 15, wherein the instructions for installing the component'"'"'s of the first and second groups comprise instructions for installing the components on a plurality of enterprise resources.