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

Patent metadata

Field	Value
Publication number	US-8938733-B2
Application number	US-201213552626-A
Country	US
Kind code	B2
Filing date	Jul 18, 2012
Priority date	Nov 30, 2010
Publication date	Jan 20, 2015
Grant date	Jan 20, 2015

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.

First claim

What is claimed is:

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 s

Assignees

• Draper Christine M
• Manekar Ashwin B
• Mcmahon Michael J
• Sundararaman Renganathan
• Sweitzer John W
• Thomsen Kaylee M
• IBM

Inventors

• Draper Christine M
• Manekar Ashwin B
• Mcmahon Michael J
• Sundararaman Renganathan
• Sweitzer John W
• Thomsen Kaylee M

Classifications

• G06F8/10

  Requirements analysis; Specification techniques · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F8/71

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title