Use the migration tools to migrate from WebSphere Application Server
Version 4.0.x to Network Deployment Version 6.0.x.
Before you begin
Migrating WebSphere Application Server Advanced Edition to WebSphere
Application Server Network Deployment requires migrating all nodes in the
collection to standalone WebSphere Application Server nodes. When migrating
a server group from an earlier version to a Version 6.0.x cluster, you should
first migrate the server group node to a standalone WebSphere Application
Server Version 6.0.x node, which also migrates applications that are on the
previous version node. Migrated applications are in the installableapps folder
in the profile of the standalone WebSphere Application Server 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 Version 6.0.x clusters. To install a migrated
application on a cluster, you copy the EAR file from the installableapps folder
of the Version 6.0.x standalone WebSphere Application Server node.
About 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:
- On one of the nodes where you are installing and migrating applications
to a standalone WebSphere Application Server node.
This choice maps the
single domain with multiple nodes to a single Version 6.0.x cell with the
same number of nodes. The deployment manager is on one of the nodes. This
placement provides a configuration that is equivalent to the previously installed
version.
- On an additional machine that does not have WebSphere Application Server.
This
choice maps the single domain with multiple nodes to a single Version 6.0.x
cell with the same number of nodes, but with the deployment manager 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 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 standalone WebSphere Application Server nodes have been added
to the cell.
Procedure
- 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
.
- Create a Version 6.0.x standalone WebSphere Application Server
profile on each node in the Version 4.x repository, as described in Creating profiles through the graphical user interface
.
Note: You must use the same cell name in Version 6.0.x that you used
in Version 4.0.x. Although it is not required, you should use the same node
name as well.
- Migrate each Version 4.x node to the standalone 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.
- Create a deployment manager, as described in Creating profiles through the graphical user interface
.
- When installing the deployment manager on a Version 6.0.x standalone
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.
- 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_name > 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.
- Use the addNode command
to
add each standalone WebSphere Application Server node to a cell. The
following procedure supports adding migrated nodes to a deployment manager
cell, whether the nodes are cloned, standalone, or a combination of the two.
- Use the addNode command
to add each node to the cell.
- 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 Version 6.0.x standalone application server. You can
find the EAR file in the installableApps directory that
is in the standalone application server profile.
The deployment manager
automatically propagates enterprise applications to application server nodes
in the cluster.
Federating a standalone 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 (after rebooting an application server machine for
example), 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
.
Adding
a node automatically issues the startNode command
for the node.