Clustered migration scenarios

Portal, V6.1

Clustered migration scenarios

+
Search Tips | Advanced Search

Migrating to a cluster is not supported; migrate to a managed node where the current version of WebSphere Portal is installed but the cluster has not been created. Ensure that the node agent is turned off before migrating.
If you intend to install IBM WebSphere Process Server v6.2 along with IBM WebSphere Portal to use business process integration, you may install the primary node on an unmanaged or a managed node. However, all secondary nodes must be installed on a managed node. Once you have federated the primary (first) node including WebSphere Process Server into the deployment manager cell, federation of additional portal nodes into this cell is not supported. Instead, follow the instructions to install secondary nodes using the managed node procedure.
Any version of WebSphere Process Server lower than v6.2 does not support installing on an unmanaged node and then federating the node to a cell. If you are installing WebSphere Portal without WebSphere Process Server follow the instructions for installing WebSphere Portal on an unmanaged node.
It is possible to install WebSphere Portal without WebSphere Process Server into a managed node, but detailed procedures for this scenario are not included in this documentation. If you choose to install WebSphere Portal without WebSphere Process Server on an unmanaged node and then federate the node, you cannot in the future install and use the business process integration capabilities of WebSphere Process Server in this existing profile containing WebSphere Portal.
When migrating to a managed node, ensure that the node agent is turned off before starting your migration.

Clustered migration paths

Table 1.
Migration Path Process
Option A

Migrate to a standalone node.
Set up the cluster

Option B

Set up the cluster with a deployment manager and primary node.
Migrate the deployment manager from the earlier server. See Migrating to a V6.1 deployment manager in the WAS Information Center.
Migrate the primary node.
Set up additional nodes to cluster.

Option C

Migrate the deployment manager from the earlier server. See Migrating to a V6.1 deployment manager in the WAS Information Center.
Migrate the standalone node.
Create the V6.1 cluster.
Add other nodes to the cluster.

Notes:

Migrate the primary node (as opposed to a secondary node) from the earlier portal environment. Migrating a secondary node can lead to security problems.
The WAS V6.1 node name must be the same as the earlier server's managed node.
If you have already installed WebSphere Portal and did not specify the same node name during installation as the earlier server's cluster managed node name, you can change the node name. For detailed instructions, see the procedure for altering the node name property for a standalone Base profile in Best Practices for Configuration Changes in WebSphere Application Server v6.x.
When migrating a deployment manager, the WAS Version 6.1 cell name must match the cell name in the earlier version.
The V6.1 deployment manager must be running when you migrate an earlier deployment manager to it.
If you are migrating a managed node to a V6.1.x managed profile, the node names must match.

Parent topic
Migration scenarios

Related information

Best Practices for Configuration Changes in WAS v6.x

Migration Path	Process
Option A	Migrate to a standalone node. Set up the cluster
Option B	Set up the cluster with a deployment manager and primary node. Migrate the deployment manager from the earlier server. See Migrating to a V6.1 deployment manager in the WAS Information Center. Migrate the primary node. Set up additional nodes to cluster.
Option C	Migrate the deployment manager from the earlier server. See Migrating to a V6.1 deployment manager in the WAS Information Center. Migrate the standalone node. Create the V6.1 cluster. Add other nodes to the cluster.