If you are running a federated environment, update your node configurations.
Procedure
-
For each node, update the wsadmin.properties properties file.
-
Open the WC_profiledir/properties/wsadmin.properties
file.
-
Ensure that the following properties are set correctly for your new DMGR host name:
For example:
- com.ibm.ws.scripting.host=newdmgr.example.com
- com.ibm.ws.scripting.port=8879
-
For each node, change the host name for the node on the DMGR profile.
-
Go to the
WAS_installdir/profiles/instance_name/bin
directory.
-
Run a command to change the host name for the node on the DMGR profile.
For
example:
./wsadmin.sh -c "$AdminTask changeHostName {-nodeName myNode1 -hostName newNode1.example.com}"
Note: This
command connects to the deployment manager.
- Optional:
For each node, change the WebSphere Commerce node name:
-
Go to the
WAS_installdir/profiles/instance_name/bin
directory.
-
Run a command to change the node name for the node in the DMGR configuration:
For
example:
./wsadmin.sh -c "$AdminTask renameNode {-nodeName dmgrNode1 -newNodeName newdmgrNode1}"
-
Run a command to change the node name for the node in the local configuration:
./wsadmin.sh -c "$AdminTask renameNode {-nodeName myNode1 -newNodeName newNode1}" -conntype NONE
This step is necessary because synchronization does not work when the local node name differs
from what is stored in the DMGR configuration.
-
Update the
WAS_installdir/profiles/instance_name/bin/setupCmdLine.sh
script to set the WAS_NODE value to your new node name.
For example:
WAS_NODE=newNode1
-
Restart the Deployment Manager (DMGR) server to ensure that the new WebSphere Commerce host
name and node names are loaded in the deployment manager configuration.
-
For each node, synchronize the nodes:
-
Go to the
WAS_installdir/profiles/instance_name/bin
directory.
-
Run a command to sync the nodes.
For
example:
./syncNode.sh newdmgr.example.com 8879 -user dmgrAdmin -password dmgrPassword