Skip to main content

Migration Use Cases with the Migration Manager

Web Doc

thumbnail 

Published on 26 December 2012

  1. View in HTML
  2. .PDF (0.2 MB)

Share this page:   

IBM Form #: TIPS0945


Authors: Vasfi Gucer and Sampath Sriramadhesikan

menu icon

Abstract

Migration Manager is a feature of Tivoli® process automation engine that enables you to migrate configuration content from one product environment to another. The typical use is to migrate configuration content from a development environment to test and then on to production. The goal of migration is to ensure your production environment fully meets the needs of your end users. This IBM® Redbooks® Solution Guide provides an overview and architecture of the Migration Manager provided by the Tivoli process automation engine and describes typical migration scenarios.

Contents

Migration Manager is a feature of the Tivoli® process automation engine that enables you to migrate configuration content from one product environment to another. The typical use is to migrate configuration content from a development environment to test and then on to production. The goal of migration is to ensure your production environment fully meets the needs of your end users. The following figure shows the Migration Manager menus in a Tivoli process automation engine based application.

Migration Manager menu
Figure 1. Migration Manager menu

This IBM® Redbooks® Solution Guide provides an overview and architecture of the Migration Manager that is provided by Tivoli process automation engine and includes typical migration scenarios.

Did you know?

The Migration Manager is heavily used in migrating system configurations prior to the production environment going live. But did you know that it is also used in migrating changes to system configurations after the production environment is live? This tool is not intended to help migrate from one version of a product to a newer release.

Business value

Migration Manager offers a standardized, repeatable set of migration steps (define, create, distribute, and deploy) regardless of the content in the package. This allows development teams to focus on actual development activities and assembling the desired content into the right set of packages.


Solution overview

Configuration content represents the metadata required to execute business applications and automation. This includes information related to system configuration, integration, reporting, and security. Examples of configuration content migrated with Migration Manager include artifacts created through the database configuration, application designer, workflow, escalations and security groups. Using the Migration Manager, you can migrate configuration content from one product environment to another.

Migration Manager implements a four-step migration process that users can perform in planned and controlled manner. The process operates on a unit of migration called a package. The package is a container for product configuration data. As illustrated in Figure 2, every package has a lifecycle wherein it is:

 

Others who read this also read

Special Notices

The material included in this document is in DRAFT form and is provided 'as is' without warranty of any kind. IBM is not responsible for the accuracy or completeness of the material, and may update the document at any time. The final, published document may not include any, or all, of the material included herein. Client assumes all risks associated with Client's use of this document.