Migrate V4.0.x to a V6 deployment manager

You can migrate V4.0.x of WAS to WebSphere Application Server Network Deployment, V6.0.

 

Before you begin

Migrating WAS Advanced Edition to WAS Network Deployment requires migrating all nodes in the collection to stand-alone WAS nodes. When migrating a server group from an earlier version to a V6 cluster, you should first migrate the server group node to a V6 stand-alone WAS node, which also migrates applications that are on the previous version node. Migrated applications are in the installableapps folder in the profile of the stand-alone WAS node.

Install the Network Deployment product and then follow the instructions in this task to migrate the server group configuration to the deployment manager. Migration creates the appropriate number of V6.0 clusters. To install a migrated application on a cluster, you copy the EAR file from the installableapps folder of the V6 stand-alone WAS node.

 

Overview

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:

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, one cannot migrate the managed node. To migrate the managed node, remove the node from the cell, use the wizard, and add the node to the cell again. You can migrate a deployment manager node after the stand-alone WAS nodes have been added to the cell.

 

Procedure

  1. Perform a typical or custom installation of the Network Deployment product on all nodes in the repository. The installation procedure is described in Installing the product and additional software.

  2. Create a V6 stand-alone WebSphere Application Server profile on each node in the V4 repository, as described in Using the Profile creation wizard.

    Note: You must use the same cell name in V6 that you used in V4.0.x. It is recommended, though not required, that you use the same node name as well.

  3. Migrate each V4 node to the stand-alone WebSphere Application Server nodes, as described in Using the Migration wizard. You must migrate each node that you intend to add to the Network Deployment configuration.

  4. Create a deployment manager, as described in Using the Profile creation wizard.

    • When installing the deployment manager on a V6 stand-alone WebSphere Application Server node that you migrated and the previous version is no longer installed, perform a manual migration against the WASPreUpgrade backup directory on this or another migrated node. Issue the WASPostUpgrade backupDirectory command from the bin directory of the profile.

    • When installing the deployment manager on a machine that did not have an earlier version of WebSphere Application Server, perform a manual migration against the WASPreUpgrade backup directory on another node that you migrated from the previous domain. Issue the WASPostUpgrade backupDirectory command from the bin directory of the profile.

  5. Start the deployment manager. Start the deployment manager in either of these ways:

    • Click All Programs > IBM WebSphere > Application Server Network Deployment v6 > Profiles >deployment_manager_profile > Start the deployment manager from the Start menu on a Windows platform.

    • Issue the startManager command from the bin directory of the deployment manager profile.

  6. Use the addNode command to add each stand-alone WAS node to a cell. The following procedure supports adding migrated nodes to a deployment manager cell, whether the nodes are cloned, stand-alone, or a combination of the two.

    1. Use the addNode command to add each node to the cell.

    2. Install any clustered applications on the appropriate cluster, using either the administrative console or the wsadmin command. Use the EAR file that the migration tools create when migrating the earlier version to the V6 stand-alone Application Server. You can find the EAR file in the installableApps directory that is in the stand-alone Application Server profile.

      The deployment manager automatically propagates enterprise applications to Application Server nodes in the cluster.

    Federating a stand-alone Application Server node into the cell creates a managed node. The configuration repository for the cell contains the master copy of the configuration for the managed node. From that point on, the deployment manager maintains the permanent configuration for the managed node. Changes that you make with the deployment manager administrative console directly update the configuration files stored on the deployment manager node.

 

What to do next

Occasionally (e.g., after rebooting an Application Server machine), restart the nodeagent server on the Application Server node by running the startNode command from the profile/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


Starting clusters
Stopping clusters
Creating clusters using scripting

 

See Also


addNode command
removeNode command
serverStatus command
startNode command
startServer command
stopNode command
stopServer command
startManager command
stopManager command

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.