AUTOMATED DEPLOYMENT OF DEFINED TOPOLOGY IN DISTRIBUTED COMPUTING ENVIRONMENT

• US 20100058331A1
• Filed: 08/28/2008
• Published: 03/04/2010
• Est. Priority Date: 08/28/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Swanke, John E., Blancett, Brad L., Elder, Michael D., Berg, Daniel C., Pouyer, Timothy A., Holliday, Chad M., Makin, Narinder
• Granted Patent: US 8,302,093 B2
• Time in Patent Office: Days
• US Class Current: 717/177
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A method for deploying a software product comprising a plurality of components is provided. The method can include reading a topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components. The method can further include reading characteristics of a plurality of publishers and matching each of the plurality of components to one of the plurality of publishers according to the characteristics and dependencies of the components and the characteristics of the plurality of publishers. A publisher may be a computer connected to a network. The method can further include distributing the plurality of components among the plurality of publishers responsive to the step of matching and validating each set of components distributed to each publisher.

Claims

1. A method for deploying a software product comprising a plurality of components, comprising:

reading a topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components;

reading characteristics of a plurality of publishers;

matching each of the plurality of components to one of the plurality of publishers according to the characteristics and dependencies of the components and the characteristics of the plurality of publishers;

distributing the plurality of components among the plurality of publishers responsive to the step of matching; and

validating each set of components distributed to each publisher.

2. The method of claim 1, wherein the first step of reading further comprises:

reading the topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components, and wherein a characteristic of a component includes a type.

3. The method of claim 2, wherein the first step of reading further comprises:

reading the topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components, and wherein a dependency includes any one of a hosting dependency and an access dependency.

4. The method of claim 1, wherein the second step of reading further comprises:

reading characteristics of a plurality of publishers, wherein a publisher comprises a server.

5. The method of claim 1, wherein the second step of reading further comprises:

reading characteristics of a plurality of publishers, wherein a characteristic of a publisher comprises a type of publisher, a hosting capability.

6. The method of claim 1, wherein the step of validating further comprises:

confirming, for each set of components distributed to each publisher, that the set of components can compile and execute on the corresponding publisher.

7. A computer program product comprising a computer usable medium embodying computer usable program code for deploying a software product comprising a plurality of components comprising:

computer usable program code for reading a topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components;

computer usable program code for reading characteristics of a plurality of publishers;

computer usable program code for matching each of the plurality of components to one of the plurality of publishers according to the characteristics and dependencies of the components and the characteristics of the plurality of publishers;

computer usable program code for distributing the plurality of components among the plurality of publishers responsive to the computer usable program code for matching; and

computer usable program code for validating each set of components distributed to each publisher.

8. The computer program product of claim 7, wherein the first computer usable program code for reading further comprises:

computer usable program code for reading the topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components, and wherein a characteristic of a component includes a type.

9. The computer program product of claim 8, wherein the first computer usable program code for reading further comprises:

computer usable program code for reading the topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components, and wherein a dependency includes any one of a hosting dependency and an access dependency.

10. The computer program product of claim 7, wherein the second computer usable program code for reading further comprises:

computer usable program code for reading characteristics of a plurality of publishers, wherein a publisher comprises a server.

11. The computer program product of claim 7, wherein the second computer usable program code for reading further comprises:

computer usable program code for reading characteristics of a plurality of publishers, wherein a characteristic of a publisher comprises a type of publisher, a hosting capability.

12. The computer program product of claim 7, wherein the computer usable program code for validating further comprises:

computer usable program code for confirming, for each set of components distributed to each publisher, that the set of components can compile and execute on the corresponding publisher.

13. A server for deploying a software product comprising a plurality of components, comprising:

a data repository for storing a topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components, and for storing characteristics of a plurality of publishers;

a processor configured for matching each of the plurality of components to one of the plurality of publishers according to the characteristics and dependencies of the components and the characteristics of the plurality of publishers;

a transmitter for distributing the plurality of components among the plurality of publishers responsive to the step of matching; and

a receiver for validating each set of components distributed to each publisher.

14. The server of claim 13, wherein a characteristic of a component includes a type.

15. The server of claim 14, wherein a dependency includes any one of a hosting dependency and an access dependency.

16. The server of claim 13, wherein a publisher comprises a server.

17. The server of claim 13, wherein a characteristic of a publisher comprises a type of publisher, and a hosting capability.

18. The server of claim 13, wherein validating comprises:

confirming, for each set of components distributed to each publisher, that the set of components can compile and execute on the corresponding publisher.