You can migrate Version 3.5.x or Version 4.0.x of WebSphere Application Server to WebSphere Application Server Network Deployment, Version 5.x.
Before you begin
Migrating WebSphere Application Server Advanced Edition to WebSphere Application Server Network Deployment requires migrating all nodes in the collection to WebSphere Application Server. When migrating a model or server group from an earlier version to a Version 5 cluster, you should first migrate the model or server group node to a Version 5 base WebSphere Application Server node, which also migrates applications that are on the previous version node. Migrated applications are in the installableapps folder in the install_root of the base WebSphere Application Server node.
Install the Network Deployment product and then follow the instructions in this task to migrate the model or server group configuration to the deployment manager. Migration creates the appropriate number of Version 5 clusters. To install a migrated application on a cluster, you copy the EAR file from the installableapps folder of the base Version 5 WebSphere Application Server node.
Why and when to perform this task
Your current configuration from a previously installed version contains one or more node configurations, one for each node in the repository. You have a choice of where to install the Network Deployment product. You can install it either:
This choice maps the single domain with multiple nodes to a single Version 5 cell with the same number of nodes. Network Deployment is on one of the nodes. This placement provides a configuration that is equivalent to the previously installed version.
This choice maps the single domain with multiple nodes to a single Version 5 cell with the same number of nodes, but with Network Deployment on an additional node.
You can vary the order in which you migrate these nodes. This task describes the most direct method.
After federating an Application Server node into a deployment manager cell, you cannot use the migration tools on the Application Server node. To use these tools again, remove the node from the cell, use the tools, and add the node to the cell again. You can, however, use the migration tools on a Network Deployment node after base Application Server nodes have been added. Use the -nodeName parameter on the WASPostUpgrade command to specify the Deployment Manager node.
You can also perform a silent migration to Network Deployment during a silent installation.
Steps for this task
You can also install the Network Deployment product silently, and migrate an earlier version configuration silently. You must supply values for silent migration options when you tailor the options response file:
You can also configure the options response file for coexistence with an earlier version by specifying non-conflicting port assignments in the file.
The deployment manager automatically propagates enterprise applications to application server nodes in the cluster.
What to do next
Occasionally, for example after rebooting an Application Server machine, you must restart the nodeagent server on the Application Server node, by running the startNode command from the bin directory of the Application Server install_root. 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.) Adding a node automatically issues the startNode command for the node.Return to Migrating configuration data to continue.