page-brochureware.php
Configuration Migration of WebSphere Application Server Traditional WebSphere Support Team instructions, strategies, tools, and other resources for migration. Support Help

Basic Migration Concepts

Migration is the process of moving the configuration from an older release to a new release, such that the new configuration behaves as closely as possible to the old configuration. The main unit for a migration is the profile, which is migrated in 3 basic steps:

 1. Take a snapshot of the source profile from the old installation.
 2. Create a compatible target profile in the new installation.
 3. Merge the data from the snapshot into the target profile.


Migration Strategies


When you plan your migration, consider the following possible migration strategies:

Standard vs. clone migration
 • Standard: The source configuration is disabled after it is migrated to the target configuration.
 • Clone: The source configuration remains functional after it is migrated to the target configuration.

Local vs. remote migration
 • Local: The configuration is migrated on the same machine. For clone migrations, the result is two coexisting environments.
 • Remote: The configuration is migrated to virtual machines hosted by the IBM Cloud® using remote and clone migration strategies.

On-prem vs. cloud migration
 • On-prem: The configuration is migrated to locally-owned machines using any of the previous migration strategies.
 • Cloud: The configuration is migrated to a new machine.

Taken from:
Overview of migration, coexistence, and interoperability


WebSphere Migration Tools



WASPreUpgrade:

Takes a snapshot of the source profile from the old installation and places it in a backup directory. For remote migrations, the WASPreUpgrade command collects additional artifacts that are referenced by your configuration in the backup directory.
 • Reference: WASPreUpgrade command

manageprofiles:

Creates the target profile. The target profile must be the same type as the source profile; for example, you cannot migrate a deployment manager profile to a stand-alone application server profile. Depending on the type of profile, you must also match the cell name, node name, or both of the source profile.
 • Reference: manageprofiles command

WASPostUpgrade:

Merges the data in the migration backup directory into the target profile. You can specify additional options control whether the old configuration is disabled, whether to postpone installing the applications, and more.
 • Reference: WASPostUpgrade command

Migration Wizard:

The Configuration Migration Management Tool, or migration wizard, is a graphical user interface (GUI) tool that guides you through running the command-line tools.
 • Reference: Migrating profiles by using the migration wizard



Overview

WebSphere Migration Knowledge Collection: Getting Started

Overview of migration, coexistence, and interoperability

Migration Troubleshooting and MustGather

Troubleshooting Migration

MustGather: Migration problems

Migration Tools

WASPreUpgrade command

manageprofiles command

WASPostUpgrade command

Migrating profiles by using the migration wizard

Using the Command-Line Tools

Clone migrating cells using the command-line tools

Migrating cells using the command-line tools (same host)

Migrating cells to new host machines using the command-line tool

Miscellaneous

Migrating WebSphere 9.0 Cells to a new Machine Using -allowSameRelease

How to Migrate WebSphere Application Server V9 with parameter \”-allowSameRelease true\” from Windows to Linux


image

IBM prides itself on delivering world class software support with highly skilled, customer-focused people.


Return to 101 home

Contact Support

Asia Pacific Europe Latin America North America Middle East and Africa