Use the migration tools to migrate a Version 5.x application server
configuration instance to a Version 6.0.x application server profile.
Procedure
- Stop the Version 5.x deployment
manager and start the Version 6.0.x migrated deployment manager if the deployment
manager is not already running and if the node is federated.
During
migration the Version 6.0.x deployment manager must be running for the migration
tools to:
- Update the configuration for each federated node
- Request full synchronization
If the Version 6.0.x deployment manager is not running, failures can
occur.
- Stop all of the Version 5.x application servers that are running
on the node.
Use the
stopServer command
from the
app_server_root/bin directory.
See
stopServer command
. For example,
issue the following commands to stop server1 and server2 on a Linux platform:
./stopServer.sh server1
./stopServer.sh server2
If security is enabled, specify
the -user and -password parameters on the stopServer command.
You
can migrate a Version 5.x node without stopping it. But it is not necessary
to have the node running to migrate its configuration. The migration tools
can retrieve all the configuration data while the node is stopped. You must
stop the node before you can start the Version 6.0.x node that you are installing.
- Stop the node agent process.
Run the
stopNode command from the
app_server_root/bin directory
of the Version 5.x application server. See
stopNode command
. For example, issue the following command to stop
the node agent process on a Linux platform:
./stopNode.sh
If
security is enabled, specify the -user and -password parameters on the stopNode command.
- Install the Version 6.0.x product.
See Installing the product and additional software
.
- Run the WASPreUpgrade script.
From
the Version 6.0.x node's profile_name/bin directory,
run the following command:
./WASPreUpgrade.sh backupDirectory V5_location
WASPreUpgrade.bat backupDirectory V5_location
where backupDirectory is the name of the directory you want the output
of WASPreUpgrade to
be stored, and V5_location is the location where the Version
5.x node is installed.
- Run the WASPostUpgrade script.
From the Version 6.0.x node's profile_name/bin directory,
run the following command:
./WASPostUpgrade.sh backupDirectory -oldProfile host_instance_name -profileName profile_name
WASPostUpgrade.bat backupDirectory -oldProfile host_instance_name -profileName profile_name
where backupDirectory is the same directory you specified in WASPreUpgrade, and profile_name is
the name of the Version 6.0.x profile. (See WASPostUpgrade command
for more information
on the WASPostUpgrade command.)
- Start the Version 6.0.x node.
- Optional: Uninstall
the Version 5.x node. Perform this step only after you are
certain that you have successfully migrated the configuration of the node
that you intend to delete.
Results
You have upgraded a Version 5.x configuration instance to a Version
6.0.x profile.