The migration tools of WebSphere Application Server, Version 6 support migrating Version 5.x managed nodes to Version 6 managed nodes.
Before you begin
Migrating a V5 managed node to a V6 managed node requires that you first migrate the V5 deployment manager node to a V6 deployment manager node. Migrating Network Deployment V5.x to V6 is described in Migrating Network Deployment, V5.x to a V6 deployment manager.
Before starting the migration of a managed node from V5 to V6, you must create a V6 profile for either a stand-alone Application Server or a managed node. If you create a V6 managed node profile, do not federate the node before migration. The migration tools federate the V6 node during migration.
The migration procedure is the same for either type of V6 profile. The end result can vary slightly. Each stand-alone Application Server has a server1 Application Server process. A V5 managed node might not have a server1 process. This task describes migrating to a V6 managed node that has not been federated.
Why and when to perform this task
After migrating a V5 deployment manager to a V6 deployment manager, the V6 deployment manager runs in compatibility mode by default, where it can manage both V5 nodes and V6 nodes. The managed nodes of the V5 deployment manager are now running as V5 managed nodes in the V6 deployment manager.
Over time, migrate each V5 managed node in the V6 cell to a V6 managed node. After migrating all V5 managed nodes, use the compatibility script, convertScriptCompatibility, to change the deployment manager from a node that supports backward compatibility of V5.x administration scripts to a node that supports only V6.
Steps for this task
See WASPreUpgrade command for a description of the currentWebSphereDirectory parameter.
Specifying “true” causes any ports of matching VirtualHosts to first be removed from the new configuration before adding the new values.
Specifying “false” for this parameter will just add new port values.
See WASPostUpgrade command for a description of the replacePorts parameter.
See WASPreUpgrade command for a description of the backupDirectory parameter.
See WASPostUpgrade command for a description of the profileName parameter.
The Migration wizard copies the configuration and applications from the V5 managed node to the V6 managed node. After migrating all of the data, the Migration wizard federates the V6 managed node into the deployment manager cell.
What to do next
Occasionally (e.g., after rebooting an Application Server machine), you must restart the nodeagent 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 nodeagent 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.
Adding a node automatically issues the startNode command for the node.
Related tasks
Using the Migration wizard