Before you begin
Read Overview of migration, coexistence, and interoperability and Premigration considerations. For resources to help you plan and perform
your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.
Tip: When migrating a
WebSphere Application Server Version 5.1.x
or Version 6.x federated node, you must perform the following actions
if you want to be able to roll it back to its previous state after
migration:
- Back up your existing configuration.
- Run the backupConfig command or your own preferred
utility to back up the Version 7.0 deployment
manager configuration.
Important: Make sure that you note
the exact name and location of this backed-up configuration.
Read
the "backupConfig command" article in the information center for more
information.
- Run the backupConfig command or your own preferred
utility to back up the Version 5.1.x or Version 6.x federated node
configuration.
Important: Make sure that you note the exact
name and location of this backed-up configuration.
Read the
"backupConfig command" article in the information center for more
information.
- Migrate the federated node.
- If necessary, you can now roll back the federated node that you
just migrated.
Read Rolling back a federated node for
more information.
About this task
The Migration wizard was introduced in WebSphere Application Server Version 6.0. The
wizard is the graphical interface to the primary Version 7.0 command-line migration
tools, which are the WASPreUpgrade command and
the WASPostUpgrade command.
For help
in troubleshooting problems when migrating, see Troubleshooting migration.
- Perform a typical or custom WebSphere Application Server Version 7.0 installation.
- Migrate the WebSphere Application Server Version
5.1.x or Version 6.x deployment manager to Version 7.0 as described in Migrating to a Version 7.0 deployment manager using the Migration wizard.
- Collect the information that the Migration wizard will
prompt you for during the migration.
Read WASPreUpgrade command and WASPostUpgrade command for descriptions of the parameters
related to the information that you need to collect.
- Optional: Use the WebSphere Application Server Version 7.0 Profile Management
tool or the manageprofiles command to create a
application server or custom profile, but do not federate the node.
Restriction: You cannot use the Profile Management
Tool to create profiles for WebSphere Application Server installations
on 64-bit architectures except on the Linux for zSeries platform.
However, you can use the Profile Management Tool on other 64–bit architectures
if you use a WebSphere Application Server 32–bit
installation.
You can first use the Profile Management tool
or the manageprofiles command to create a valid
new target Version 7.0 application
server profile if one does not already exist, or you can create a
target profile later using the Migration wizard. Read the "Creating
profiles using the graphical user interface" article in the information
center for more information.
For migration to be successful,
you must use the same node names and cell names for each node that
you migrate from Version 5.1.x or Version 6.x to Version 7.0.
Tip: If you make any cell-level changes to the new Version 7.0 node before migration,
such as changes to virtual-host information, these changes will be
lost during migration. Therefore, you should wait until after the
node has been migrated before making any such changes. Otherwise,
you will have to manually remake all of the changes to the new cell
after migration using the administrative console running on the deployment
manager. This tip is reflected in message MIGR0444W.
- Ensure that the Version 7.0 deployment
manager is up and running.
Note: You can migrate a Version
5.1.x or Version 6.x node whether the node is running or stopped.
The migration tools can retrieve all the configuration data either
way. You must stop the Version 5.1.x or Version 6.x node before you
can start the Version 7.0 node
that you are installing, however, so it makes sense to stop it now.
- Start the Migration wizard.
Perform one of
the following actions to access the Migration wizard:
- Go to Start > Programs > IBM® WebSphere Application Server Version 7.0 WebSphere Application Server, Network Deployment, and click Migration
wizard.
- Run the following command:
- app_server_root/bin/migration.sh
- app_server_root\bin\migration.bat
- Read the Welcome panel to learn about the migration process,
and then click Next.
- Select or specify a previous version of WebSphere Application Server from which to
migrate, and then click Next.
Select the check
box and enter the location of the previous installation if it does
not display in the selection list.
- Select the source profile or instance that you want to
migrate, and then click Next.
- Select the target profile to which you want to migrate
from the list of valid profiles for the installation or select Create
new profile, and then click Next.
Select
the check box to create a backup copy of the target profile's configuration
before migrating the source profile. If you select the check box,
the backup copy of the target profile will be written to profile_root/temp/MigrationBackup.time_stamp.zip.
You can use the restoreConfig command to restore
the configuration after migration if necessary.
- If you selected Create new profile on the last panel,
enter the parameters for creating the new profile and then click Next.
- Specify a migration backup directory in which to place
a backup copy of the configuration from the previous version, and
then click Next.
The directory is created if
it does not already exist. If the directory exists, it should be empty
because the backup operation might overwrite existing backup files.
- Select one of the options for migrating the applications
installed on the source profile, and then click Next.
You
can choose to do either one of the following with the applications:
- If you selected the option to install your applications,
specify where the migrated applications should be located and then
click Next.
You can choose any one of the following
options:
- Keep the applications in the same directories in which they are
currently located.
Restrictions: If
you choose this option, the location is shared by the existing
WebSphere Application Server Version 5.1.x
or Version 6.x installation and the
Version 7.0 installation. If
you keep the migrated applications in the same locations as those
of the previous version, the following restrictions apply:
- The WebSphere Application Server Version 7.0 mixed-node support
limitations must be followed. This means that the following support
cannot be used when evoking the wsadmin command:
- Precompile JSP
- Use Binary Configuration
- Deploy EJB
- You risk losing the migrated applications unintentionally if you
later delete applications from these locations when administering
(uninstalling for example) your Version 5.1.x or Version 6.x installation.
- Choose to install the applications in the default directory of
the target version.
- Specify the directory in which to install the migrated applications.
- Select one of the options for setting port values, optionally
specify a starting port value for resolving port conflicts, and then
click Next.
You can choose to do any one of the
following with the port values:
- Use the port values assigned to the previous (source) installation.
- Use the port values assigned to the target profile.
By default, a port conflict is resolved by incrementing
the port number by one until an unused port number is found. Instead,
you can specify a starting port number to be used when a conflict
is detected. If the starting port number is in use, it will be incremented
by one until an unused port number is found.
- Select the check box if you want to migrate to support
script compatibility, and then click Next.
If
you select this option, migration creates the following Version 5.1.x
or Version 6.x configuration definitions:
- Transports
- ProcessDef
- Version 5.1.x or Version 6.x SSL
- Version 5.1.x or Version 6.x ORB service threadpool
instead of the following
Version 7.0 configuration definitions:
- Channels
- ProcessDefs
- Version 7.0 SSL
- Version 7.0 ORB service
threadpool
Select this option in order to minimize impacts to existing
administration scripts. If you have existing wsadmin scripts
or programs that use third-party configuration APIs to create or modify
the Version 5.1.x or Version 6.x configuration definitions, for example,
you might want to select this option during migration.
Note: This is meant to provide a temporary transition until
all of the nodes in the environment are at the
Version 7.0 level. When they
are all at the
Version 7.0 level,
you should perform the following actions:
- Modify your administration scripts to use all of the Version 7.0 settings.
- Use the convertScriptCompatability command
to convert your configurations to match all of the Version 7.0 settings.
Read convertScriptCompatibility command for more information.
- Specify the administrative console workspace user root
directory where the "My Tasks" user information is stored in the previous
installation, and then click Next.
This panel
displays only if you are migrating from Version 6.1.x.
- Enter the administrative security credentials for the source WebSphere Application Server installation,
and then click Next.
This panel only displays
if security is enabled and if the server user identity is not stored
in the repository.
- Verify that the Version 7.0 deployment
manager is running, and then click Next.
- Check the information in the summary panel and make sure
that it is correct, and then click Next to start the migration.
- If the wizard indicates that the profile-creation process
was successful, click Next.
This panel displays
only if you selected the option to create a new target profile.
If
the process is not successful, the wizard displays a failure panel.
If the process is partially successful, the wizard displays a warning
panel. Correct any problems and retry the migration.
- If the wizard indicates that the pre-upgrade process was
successful, click Next.
If the process is not
successful, the wizard displays a failure panel. If the process is
partially successful, the wizard displays a warning panel. Correct
any problems and retry the migration.
- If the wizard indicates that the post-upgrade process was
successful, click Next.
If the process is not
successful, the wizard displays a failure panel. If the process is
partially successful, the wizard displays a warning panel. Correct
any problems and retry the migration.
- If the wizard indicates that the migration was successful,
click Next.
If the process is not successful,
the wizard displays a failure panel. If the migration is partially
successful, the wizard displays a warning panel. Correct any problems
and retry the migration.
- Click Next to migrate another profile, or click Cancel to
exit the Migration wizard.
- Stop and restart each of the application servers on the
migrated nodes.