Use the Migration wizard to migrate from a WebSphere Application
Server Version 5.x or 6.0.x deployment manager to Version 6.1.
Before you begin
See Overview of migration, coexistence, and interoperability and Premigration considerations.
Collect
the following information before you begin this procedure (the Migration wizard
prompts you for the information during the migration):
- Installation root directory
- See WASPreUpgrade command for a description of
the -currentWebSphereDirectory parameter.
- Migration backup directory name
- See WASPreUpgrade command for a description of
the -backupDirectory parameter.
- Source profile name
- See WASPostUpgrade command for a description of
the -oldProfile parameter.
- Target profile name
- See WASPostUpgrade command for a description of
the -profileName parameter.
- Applications to be migrated
- See WASPostUpgrade command for a description of
the -includeApps parameter.
- Port value assignments
- See WASPostUpgrade command for a description of
the -replacePorts parameter.
Before using the Migration wizard, you must have access
to the existing WebSphere Application Server Version 5.x or 6.0.x deployment
manager. You can first use the Profile Management tool to create a valid new
target Version 6.1 deployment manager profile if one does not already exist,
or you can create a target profile later using the Migration wizard.
During
installation, the WebSphere Application Server Network Deployment product
gives you the choice of creating a standalone application server, a deployment
manager profile, a cell, a custom profile, or no profile. The Installation
wizard also prompts you to use the Profile Management tool at the end of installing
the core product files; however, using the Profile Management tool at that
time is optional. If the deployment manager profile was not created during
the installation, you can create one using the Profile Management tool.
The
Migration wizard was introduced in WebSphere Application Server Version 6.0.
It is the graphical interface to the primary Version 6.1 command-line migration
tools, which are the WASPreUpgrade command and
the WASPostUpgrade command.
After
gathering all of the information that is required during the migration, use
the wizard to migrate a WebSphere Application Server Version 5.x or 6.0.x
deployment manager to the Version 6.1 deployment manager.
For help in
troubleshooting problems when migrating, see Troubleshooting migration.
Tip: Before migrating a WebSphere Application Server Version 5.x or
6.0.x deployment manager, use the backupConfig command
or your own preferred backup utility to back up your existing configuration
if you want to be able to restore it to its previous state after migration.
Make sure that you note the exact name and location of this backed-up
configuration.
- Start the Migration wizard.
- 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
appear in the selection list.
- 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 the source profile that you want to migrate, and then click Next.
- Select the target profile 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.
- If you selected Create new profile on the last panel, enter
the parameters for creating the new profile and then click Next.
- Select one of the options for migrating the applications installed
on the source profile, and then click Next.
You can choose
to do any 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.x or 6.0.x installation and the Version 6.1 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 6.1 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.x or 6.0.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 the check box if you want to prevent migration processing
from disabling the existing WebSphere Application Server Version 5.x or 6.0.x
deployment manager, and then click Next.
If this is selected,
you can use the existing Version 5.x or 6.0.x deployment manager while the
migration is being completed.
Caution: Select
this option with care.
- The reason that WebSphere Application Server Version 5.x or 6.0.x deployment
manager configurations normally are stopped and disabled is to prevent multiple
deployment managers from managing the same nodes. You must stop the Version
5.x or 6.0.x deployment manager before you start using the Version 6.1 deployment
manager. The most likely error conditions that will occur if this is not done
are port conflicts when the second instance of the deployment manager is started.
- Selecting this option means that any configuration changes made in the
old configuration during migration might not be migrated.
- Select one of the options for assigning port values, and then click Next.
You can choose to do any one of the following with the port values:
- 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.x or 6.0.x configuration definitions:
- Transport
- ProcessDef
- Version 5.x or 6.0.x SSL
- Version 5.x or 6.0.x ORB service threadpool
instead of the following Version 6.1 configuration definitions:
- Channels
- ProcessDefs
- Version 6.1 SSL
- Version 6.1 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.x or 6.0.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 6.1 level. When they are all at the Version 6.1 level, you should
perform the following actions:
- Modify your administration scripts to use all of the Version 6.1 settings.
- Use the convertScriptCompatability command to
convert your configurations to match all of the Version 6.1 settings.
See convertScriptCompatibility command.
- Check the information in the summary panel and make sure that it
is correct, and then click Next to start the migration.
If
you selected the option to create a new target profile, panels show the beginning
and results of that creation.
Panels show the progress of the migration
process.
If the migration 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.
If the post-migration
is successful, the wizard displays an indication of success.
- Click Finish to exit the Migration wizard.