Before you begin
Read Overview of migration, coexistence, and interoperability and Premigration considerations.
Tip: Before migrating
from WebSphere Application Server Version 5.1.x
or Version 6.x, 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.
Read the "backupConfig command" article in the information center
for more information. Make sure that you note the exact name and location
of this backed-up configuration.
For help, read Troubleshooting migration.
- Obtain the WebSphere Application Server
Version 7.0 utilities disk.
This disk contains the migration/bin directory.
This directory contains a special environment that you can use to
run the WASPreUpgrade command without installing
Version 7.0.
- Save the current configuration using the WASPreUpgrade script
from the migration/bin directory of the WebSphere Application Server Version 7.0
utilities disk.
Read WASPreUpgrade command for more information.
Save the configuration
in the migration_specific_backup directory.
If
the WASPreUpgrade command fails because the Java Development Kit (JDK) on the Version 7.0
utilities disk is not supported on the operating system that you are
attempting to migrate, perform the following actions:
- Create a migration directory on your local system.
- Install an IBM® certified JDK that is at the
highest level that will run on your operating system.
Important: Your JDK must be version 1.6 or later if you want
to use the migration tools.
The JDK directory should be in
the same directory as the migration directory that you created on
your local system in the last step, or you should have a working symlink
that allows Java to be invoked from that path.
<directory>
- migration directory
- JDK/jre.pak/repository/package.java.jre/java/jre/bin/java
- Copy the WASPreUpgrade.bat (or WASPreUpgrade.sh)
and the setupCmdLine.bat (or setupCmdLine.sh)
files from the migration/bin directory of the WebSphere Application Server Version 7.0
utilities disk to the migration directory that you created on your
local system.
- Edit the setupCmdLine.bat or setupCmdLine.sh file
in your new migration directory.
- Change WAS_HOME to point to the fully qualified path to
the migration directory that you created
- Change JAVA_HOME to point to the fully qualified path to
your IBM Developer Kit or Java directory.
- Ensure that the executable bit is on for the setupCmdLine.sh and WASPreUpgrade.sh files
in the migration directory that you created.
- Run the command from the migration directory that you
created.
Identify the backup directory and the location
of the configuration files.
migration_directory\WASPreUpgrade migration_specific_backup_directory
file_path\WebSphere\AppServer node_name
- Shut down the WebSphere Application Server
Version 5.1.x or Version 6.x release by stopping all server nodes
in the configuration.
- Tar or zip the migration_specific_backup directory,
and FTP it to another system.
- Install WebSphere Application Server
Version 7.0 on the new operating system.
Read the "Installing
the product and additional software" article in the information center
for more information.
Install the same features as the earlier
release.
- Use the Profile Management Tool or the manageprofiles command
to create a WebSphere Application Server Version 7.0
profile.
The Version 7.0 deployment manager profile
must have the same cell name as the Version 5.1.x or Version 6.x profile
that is being migrated.
Read the "Creating profiles using the
graphical user interface" article or the "manageprofiles command"
article in the information center for more information.
- Add the WebSphere Application Server
Version 5.1.x or Version 6.x configuration to the Version 7.0 configuration.
Read WASPostUpgrade command for
more information.
Specify -keepDmgrEnabled true when
you run the WASPostUpgrade command. If you fail
to do so, the WASPostUpgrade command will fail
when it is unable to locate the Version 5.1.x or Version 6.x installation
on the same machine as the Version 7.0 installation.
Use the WASPostUpgrade command
in the app_server_root/bin directory
of the Version 7.0 installation to add the Version 5.1.x or Version
6.x configuration to the Version 7.0 configuration.
./WASPostUpgrade.sh /filepath/migration_specific_backup
-keepDmgrEnabled true
WASPostUpgrade C:\filepath\migration_specific_backup
-keepDmgrEnabled true
The WASPostUpgrade tool
records information specific to each enterprise bean it deploys in
the migration_specific_backup/WASPostUpgrade.log file.
- Modify the configuration using the WebSphere Application
Server Version 7.0 administrative console.
- Change user IDs and passwords to match security requirements.
If you make any changes to the security configuration, you
must then resynchronize all federated nodes in the configuration.
If you fail to do so, the nodes will not be able to communicate with
the deployment manager and migration will not be able to upgrade the
federated nodes.
You might have to change user IDs and passwords
if they are not identical to those in use on the Version 5.1.x or
Version 6.x machine.
- Change other machine-specific information.
The
configuration might refer to other software products or configurations
that do not exist on the new machine. For example, the old machine
might have a database. Modify the data source to point to the database
on the old machine.
- Manually synchronize all federated nodes with the migrated
deployment manager.
If you fail to do so, the nodes
will not be able to communicate with the deployment manager and migration
will not be able to upgrade the federated nodes.