You can manage previous versions of WebSphere® product application servers in
the Intelligent Management administrative
console. If you have a large topology and want to automate a migration
from Version 6.1, 7.0, or 8.0 to Version 8.5, you can use the migration
toolkit to detect your configurations and import them into a Version
8.5 cell.
Before you begin
- Install and federate your Version 8.5 middleware
agents and deployment manager on your previous version machines. For
the purposes of this task, the previous version deployment manager
is referred to as the previous deployment manager. If you do
not have the middleware agent running on your previous deployment
manager, you can copy the AGENT_HOME/lib/legacycell.jar file
and AGENT_HOME/bin/Extractor.sh|.bat file from
another workstation that has the middleware agent deployed to the
previous deployment manager.
- Install or augment your deployment manager for Version 8.5.
About this task
The migration toolkit can detect previous WebSphere configurations and import them
into a Version 8.5 cell.
The
migration toolkit uses scripts to connect to one cell, read the data,
and import the data into the other cell. The scripts also function
as an adaptor or integration interface. The migration script logic
handles the routing information and environment detection. The scripts
also perform integrity checks to ensure a stable configuration.
For
more information read about the migration toolkit.
Procedure
- Generate the mappings file. The mappings file
defines additional data that cannot be gathered automatically. You
must generate the mappings file before you import the middleware deployment.
- Log in to the previous deployment manager computer.
- On the deployment manager computer, go to the AGENT_HOME/bin directory,
or the directory to which you copied the middleware agent files from
another workstation.
- Run the Extractor.sh or Extractor.bat script. For example, run the following command:
./Extractor.sh app_server_root/config
The single install_root directory is the
default for the deployment manager profile directory. If install_root does
not specify the deployment manager profile directory as the default,
add the following argument:app_server_root/profiles/deployment_manager_profile/config
When this script completes, a Mapping.dat file
is in the directory from which you ran the script.
- Copy the Mapping.dat file to the app_server_root/bin directory
on your Intelligent Management Version 8.5 deployment manager.
- Run the automation script.
- Log in to your Intelligent Management Version 8.5 deployment manager computer.
- On the deployment manager computer, navigate to the app_server_root/bin directory.
- Run the MirrorCell.bat or MirrorCell.sh script. The MirrorCell script uses the following format:
MirrorCell.* [-props PROPS] [-mode MODE] [-nosec, –nosave]
The only required parameter is the -props parameter, which specifies
the full path to the properties file. For more information about the
MirrorCell script parameters, read about the MirrorCell.bat or MirrorCell.sh script.
Avoid trouble: If you include paths that contain spaces in your
script call, surround these paths with quotation marks, for example:
"C:\Program Files"
gotcha
By default, the script connects to the previous deployment
manager and generates any necessary delta information between the
newly detected configuration and a copy of the last known configuration.
The script then uses this delta information to recreate the configuration
within the Version 8.5 cell.
Status updates are reported at each milestone.
- Log in to the Intelligent Management cell
and verify that the configuration was created properly. To
check that your servers are represented in the console, click . To check that representations of your applications
were created, click .
What to do next
You can manage your previous configurations from the Intelligent Management cell.