GENERATING A CUSTOMIZED SET OF TASKS FOR MIGRATION OF A DEPLOYED SOFTWARE SOLUTION

• US 20130014097A1
• Filed: 07/18/2012
• Published: 01/10/2013
• Est. Priority Date: 11/30/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Draper, Christine M., Manekar, Ashwin B., McMahon, Michael J., Sundararaman, Renganathan, Sweitzer, John W., Thomsen, Kaylee M.
• Granted Patent: US 8,938,733 B2
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A migration set list generator specifies a physical topology of a deployed software solution, wherein the software solution comprises software components and data associated with the software components integrated into a single entity. The migration set list generator specifies at least one solution change to the deployed software solution to meet at least one business requirement and specifies at least one migration strategy for migrating the deployed software solution. The migration set list generator generates migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy and generates a recommended physical topology yielded for the software solution if the physical topology is updated according to the migration tasks.

Claims

1. A method for generating a set of tasks for performing a migration of a software solution comprising:

specifying a physical topology of a deployed software solution, wherein the software solution comprises a plurality of software components and data associated with said plurality of software components integrated into a single entity;

specifying at least one solution change to the deployed software solution to meet at least one business requirement;

specifying at least one migration strategy for migrating the deployed software solution, wherein the at least one migration strategy comprises at least one of a product level strategy specified for a particular software component of the plurality of software components and at least one solution level strategy specified for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component;

generating a plurality of migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy;

generating a recommended physical topology yielded for the software solution if the physical topology is updated according to the plurality of migration tasks; and

outputting the plurality of migration tasks and recommended physical topology for providing a simulated plan for migrating the software solution according to the at least one migration strategy to meet the at least one business requirement.

2. The method according to claim 1, further comprising:

specifying the migration strategy to migrate the software solution in place; and

generating the plurality of migration tasks for making the at least one solution change to the software solution on the same machine as specified for the software solution in the physical topology.

3. The method according to claim 1, further comprising:

specifying the migration strategy to install an upgraded version of at least one software component of the plurality of software components on a new machine and migrate the data associated with the at least one software component to the new machine; and

generating the plurality of migration tasks for making the at least one solution change to the software solution on the new machine and for migrating the data associated with the at least one software component to the new machine.

4. The method according to claim 1, further comprising:

specifying the migration strategy to install an upgraded version of at least one software component of the plurality of software components on a new machine and to keep a current version of the at least one software component on a current machine specified in the physical topology; and

generating the plurality of migration tasks for making the at least one solution change to the software solution on the new machine and maintaining the current version of the at least one software component on the current machine.

5. The method according to claim 4, further comprising:

generating the plurality of migration tasks for moving a copy of the data associated with the at least one software component to the new machine, for keeping a current version of the data on the current machine, and for synchronizing the copy of the data with the current version of the data.

6. The method according to claim 4, further comprising:

generating the plurality of migration tasks for maintaining the data associated with the at least one software component on the current machine and sharing the data between the upgraded version of the at least one software component and the current version of the at least one software component.

7. The method according to claim 4, further comprising:

generating the plurality of migration tasks for moving a copy of the data associated with the at least one software component to the new machine and for keeping a current version of the data on the current machine.

8. The method according to claim 1, further comprising:

specifying the migration strategy with the product level strategy specified to migrate a particular software component from among the plurality of software components in place and with the solution level strategy specified to migrate the software solution in place;

applying the product level strategy to override the solution level strategy for the particular software component; and

generating the plurality of migration tasks for making the at least one solution change to the particular software component on the new machine and for migrating the data associated with the particular software component to the new machine and for performing the remaining changes specified in the solution change without the particular software component to the software solution on the same machine as specified for the software solution in the physical topology.

9. The method according to claim 1, further comprising:

accessing at least one recommended upgrade approach for at least one component of the software solution; and

generating the plurality of migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy to perform according to the at least one recommended upgrade approach.

10. The method according to claim 1, further comprising:

specifying the physical topology of the deployed software solution for an enterprise client comprising at least one dependency between a first software component of the plurality of software components and a second software component of the plurality of software components;

specifying at least one solution change to the first software component of the deployed software solution to meet at least one business requirement of the enterprise client;

generating the plurality of migration tasks for making the at least one solution change to the first software component of the deployed software solution comprising a first selection of tasks for migrating the first software component according to the at least one migration strategy and a second selection of tasks for migrating the second software component according to the at least one migration strategy; and

generating the recommended physical topology yielded for the software solution if the physical topology is updated according to the plurality of migration tasks comprising the dependency between the upgraded version of the first software component and the second software component.