Use the migration tools to migrate WebSphere Application Server product configurations.
Before you begin
You can migrate your product configurations using the Migration wizard or the command-line migration tools.
If you use an earlier version of WebSphere Application Server, the system administrator might have fine-tuned various application and server settings for your environment. It is important to have a strategy for migrating these settings with maximum efficiency and minimal loss.
You can perform incremental migration of WebSphere Application Server Version 4.0.x nodes by calling the migration tools multiple times, each time specifying a different configuration file. Various reasons exist for having multiple configuration files. Whatever the reason, migrating one configuration file at a time lets you test applications incrementally before continuing to the next configuration file. You can also perform incremental migration of Version 5.x instances in the same manner.
Before using the migration tools, consult the WebSphere Application Server Version 6.0 Release Notes document to understand what fixes you must apply to earlier versions. Applying fixes to an earlier version might also apply fixes to files that have a role in the migration. Apply any fixes to ensure the most effective migration of configurations and applications possible.
The migration tools in WebSphere Application Server Version 6.0.x support migration from WebSphere Application Server Version 4.0.x, Version 5.0.x, and Version 5.1.x.
Why and when to perform this task
IBM provides a set of migration tools for migrating administrative configurations from Version 4.0.x, 5.0.x, or 5.1.x to the Version 6.0.x Network Deployment product.
The Migration wizard calls the WASPostUpgrade command. The WASPostUpgrade command uses the backupConfig command to save the existing Version 6.0.x configuration before performing migration. The results are stored in the profile_name/temp directory. You can use the restoreConfig command to restore the backup if required.
Steps for this task
Select one of the following migration scenarios for information about how to migrate configuration data from a Version 4.0.x or 5.x Express node or a Version 4.0.x or 5.x base node to a Version 6.0.x stand-alone application server:
Use the startNode script from the profile_name/bin directory of each application server to start the node agent process. See startNode command.
Occasionally, for example after rebooting an application server machine, you must restart the node agent server on the application server node, by running the startNode command from the profile_name/bin directory. To keep your application server nodes running without having to access the bin directory of each one, use the operating system to monitor and restart the node agent process on each application server node. (You can also set up the dmgr server as a managed process on the deployment manager node.) For more information, see Automatically restarting server processes.
Result
You can use the migration tools to migrate from one version of WebSphere Application Server to another.What to do next
Return to Migrating and coexisting to continue.