Generating a customized set of tasks for migration of a deployed software solution

• US 8,938,733 B2
• Filed: 07/18/2012
• Issued: 01/20/2015
• Est. Priority Date: 11/30/2010
• Status: Expired due to Fees

• 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.
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): KEPNANG, GILLES R
• Application Number:
  US13/552,626
• Publication Number:
  US 20130014097A1
• Time in Patent Office: 916 Days
• Field of Search: 705/28, 707/203, 717/102, 717168-174, 717177-178
• US Class Current: 717/174
• 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, by at least one computer system, a current physical topology of a deployed software solution, wherein the deployed software solution comprises a plurality of software components and data associated with the plurality of software components integrated into a single entity;

specifying, by the at least one computer system, at least one solution change to the deployed software solution to meet at least one business requirement;

specifying, by the at least one computer system, at least one migration strategy for migrating the deployed software solution, wherein the at least one migration strategy comprises at least one product level strategy applicable for a particular software component of the plurality of software components and at least one solution level strategy applicable for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component, wherein each of the product level strategy and the solution level strategy are selected from among;

a first strategy that requires performing the at least one solution change on at least one new machine for a future physical topology and migrating data associated with an upgraded version of at least one software component from among the plurality of software components to the at least one new machine; and

a second strategy that requires performing the at least one solution change on the at least one new machine for the future physical topology and maintaining a current version of the at least one software component on at least one original machine in the current physical topology;

generating, by the at least one computer system, a plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the current physical topology, wherein the plurality of migration tasks apply the at least one migration strategy;

generating, by the at least one computer system, a recommendation of the future physical topology for the received software solution, wherein the recommended future physical topology is updated according to the plurality of migration tasks that comprise at least one task for at least one of the at least one new machine or the at least one original machine; and

outputting, by the at least one computer system, the plurality of migration tasks and recommended future physical topology, the outputting further illustrating 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 performing the at least one solution change to the software solution on a same machine currently comprising the software solution, 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 the upgraded version of the at least one software component of the plurality of software components on the at least one new machine and migrate the data associated with the at least one software component to the at least one new machine; and

generating the plurality of migration tasks, wherein the plurality of migration tasks comprise at least one task for;

performing the at least one solution change to the software solution on the at least one new machine; and

migrating the data associated with the at least one software component to the at least one new machine.

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

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

generating the plurality of migration tasks, wherein the plurality of migration tasks comprise at least one task for;

performing the at least one solution change to the software solution on the at least one 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, wherein the plurality of migration tasks comprise at least one additional task for;

moving a copy of the data associated with the at least one software component to the at least one new machine;

keeping a current version of the data on the current machine; and

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, wherein the plurality of migration tasks comprise at least one additional task 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, wherein the plurality of migration tasks comprise at least one additional task for;

moving a copy of the data associated with the at least one software component to the at least one new machine; and

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 and its associated data to another machine 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, wherein the plurality of migration tasks comprise at least one task for;

performing the at least one solution change to the particular software component on the at least one new machine;

migrating the data associated with the particular software component to the at least one new machine, excluding the particular software component from at least one remaining change specified in the at least one solution change; and

performing the at least one remaining change on a same machine originally comprising the software solution, as specified for the software solution as originally specified in the current 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 performing the at least one solution change to the deployed software solution specified in the physical topology, wherein the at least one solution change is based on the at least one migration strategy to perform in accordance with the at least one recommended upgrade approach.

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

specifying the current 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;

receiving specifications for 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 performing 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 future physical topology yielded for the software solution if the physical topology is updated according to the plurality of migration tasks, wherein the recommended future physical topology comprises the dependency between an upgraded version of the first software component and the second software component, wherein the upgraded version of the first software component is based on the first selection of tasks.

11. A computer system for generating a set of tasks for performing a migration of a software solution, the system comprising:

a migration task list generator coupled to at least one processor and memory;

the migration task list generator programmed to;

receive specifications for a current physical topology of a deployed software solution, wherein the deployed software solution comprises a plurality of software components and data associated with the plurality of software components integrated into a single entity;

receive specifications for at least one solution change to the deployed software solution to meet at least one business requirement;

receive specifications for at least one migration strategy for migrating the deployed software solution, wherein the at least one migration strategy comprises;

at least one a product level strategy applicable for a particular software component of the plurality of software components and at least one solution level strategy applicable for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component, wherein each of the product level strategy and the solution level strategy are selected from among;

a first strategy that requires performing the at least one solution change on at least one new machine for a future physical topology and migrating data associated with an upgraded version of at least one software component from among the plurality of software components to the at least one new machine; and

a second strategy that requires performing the at least one solution change on the at least one new machine for the future physical topology and maintaining a current version of the at least one software component on at least one original machine in the current physical topology;

generate a plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the current physical topology, wherein the plurality of migration tasks apply the at least one specified migration strategy;

generate a recommendation of the future physical topology for the received software solution, wherein the recommended future physical topology is updated according to the plurality of migration tasks that comprise at least one task for at least one of the at least one new machine or the at least one original machine; and

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

12. The system according to claim 11, said migration task list generator further programmed to:

receive specifications for the migration strategy to migrate the software solution in place; and

generate the plurality of migration tasks for performing the at least one solution change to the software solution on a same machine currently comprising the software solution, as specified for the software solution in the current physical topology.

13. The system according to claim 11, said migration task list generator further programmed to:

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

generate the plurality of migration tasks, the plurality of migration tasks comprising least one task for;

performing the at least one solution change to the software solution on the at least one new machine; and

migrating the data associated with the at least one software component to the at least one new machine.

14. The system according to claim 11, said migration task list generator further programmed to:

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

generate the plurality of migration tasks, the plurality of migration tasks comprising at least one task for;

performing the at least one solution change to the software solution on the at least one new machine; and

maintaining the current version of the at least one software component on the current machine.

15. The system according to claim 14, said migration task list generator further programmed to:

generate the plurality of migration tasks, the plurality of migration tasks comprising least one task for;

moving a copy of the data associated with the at least one software component to the at least one new machine;

keeping a current version of the data on the current machine; and

synchronizing the copy of the data with the current version of the data.

16. The system according to claim 14, said migration task list generator further programmed to:

generate the plurality of migration tasks, the plurality of migration tasks comprising least one task 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.

17. The system according to claim 14, said migration task list generator further programmed to:

generate the plurality of migration tasks, the plurality of migration tasks comprising at least one task for;

moving a copy of the data associated with the at least one software component to the at least one new machine; and

keeping a current version of the data on the current machine.

18. The system according to claim 11, said migration task list generator further programmed to:

receive specifications for the migration strategy with the product level strategy to migrate a particular software component and its associated data to another machine and with the solution level strategy specified to migrate the software solution in place;

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

generate the plurality of migration tasks, the plurality of migration tasks comprising at least one task for;

performing the at least one solution change to the particular software component on the at least one new machine;

migrating the data associated with the particular software component to the at least one new machine, excluding the particular software component from at least one remaining change specified in the at least one solution change; and

performing the at least one remaining change on a same machine originally comprising the software solution, as specified for the software solution as originally specified in the current physical topology.

19. The system according to claim 11, said migration task list generator further programmed to:

receive specifications for the current 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;

receive specifications for 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;

generate the plurality of migration tasks for performing 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;

generate the recommended future physical topology yielded for the software solution if the physical topology is updated according to the plurality of migration tasks, wherein the recommended future physical topology comprises the dependency between an upgraded version of the first software component and the second software component, wherein the upgraded version of the first software component is based on the first selection of tasks.

20. A computer program product for generating a set of tasks for performing a migration of a software solution, the computer program product comprising:

one or more non-transitory computer-readable tangible storage devices;

program instructions, stored on at least one of the one or more storage devices, to receive specifications for a current physical topology of a deployed software solution, wherein the deployed software solution comprises a plurality of software components and data associated with the plurality of software components integrated into a single entity;

program instructions, stored on at least one of the one or more storage devices, to receive specifications for at least one solution change to the deployed software solution to meet at least one business requirement;

program instructions, stored on at least one of the one or more storage devices, to receive specifications for at least one migration strategy for migrating the deployed software solution, wherein the at least one migration strategy comprises;

at least one product level strategy applicable for a particular software component of the plurality of software components and at least one solution level strategy applicable for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component, wherein each of the product level strategy and the solution level strategy are selected from among;

a first strategy that requires performing the at least one solution change on at least one new machine for a future physical topology and migrating data associated with an upgraded version of at least one software component from among the plurality of software components to the at least one new machine; and

a second strategy that requires performing the at least one solution change on the at least one new machine for the future physical topology and maintaining a current version of the at least one software component on the at least one original machine in the current physical topology;

program instructions, stored on at least one of the one or more storage devices, to generate a plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the current physical topology, wherein the plurality of migration tasks apply the at least one specified migration strategy;

program instructions, stored on at least one of the one or more storage devices, to generate a recommendation of the future physical topology for the received software solution, wherein the recommended future physical topology is updated according to the plurality of migration tasks that comprise at least one task for at least one of the at least one new machine or the at least one original machine; and

program instructions, stored on at least one of the one or more storage devices, to output the plurality of migration tasks and recommended future physical topology, the outputting further illustrating a simulated plan for migrating the software solution according to the at least one migration strategy to meet the at least one business requirement.