Rename the node

Rename the node

In a clustered environment, it may be necessary to rename a node because the deployment manager does not permit duplicate node names in a cell.
You must first change the name in the deployment manager using the IBM WAS command renameNode. WebSphere Portal stores the node name information in the registry so after running the WAS command, you would need to update the information in the registry. Run...
following
on the node where the node name was changed to ensure that the updates to the registry are reflected in the master configuration repository and synchronized to all nodes in the cell:
Run...
this
...after running the renameNode command.
Operating System Task
Windows ConfigEngine.bat rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName, from the profile_root/ConfigEngine directory.
UNIX ./ConfigEngine.sh rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName, from the profile_root/ConfigEngine directory.
i5/OS ConfigEngine.sh rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName, from the profile_root/ConfigEngine directory.

Parent topic:
Manage the cluster

Related information

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/renameNode_command1395.html

Operating System	Task
Windows	ConfigEngine.bat rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName, from the profile_root/ConfigEngine directory.
UNIX	./ConfigEngine.sh rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName, from the profile_root/ConfigEngine directory.
i5/OS	ConfigEngine.sh rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName, from the profile_root/ConfigEngine directory.