Dustin’s note: Seeing as the wsadmin command to rename a cell is not officially documented or supported, I have removed it from this post. I’m sorry, but it is for your own good!!
It seems like I get asked quite a bit about how to change node names and host names for a given WebSphere Application Server environment. It usually starts by someone asking me what configuration files they need to change when they want to update this information, and is followed by their surprise when I tell them none. The reason I say that is because it’s time consuming, hard, and unnecessary for you to figure this out. Instead, you can use two simple wsadmin commands. I’ll give you an example of those here (all written in Jython).
To change the name of a given node, use the following wsadmin command:
AdminTask.renameNode(‘[-nodeName <existing_node_name> -newNodeName <new_node_name>]’)
This updates the name of the node specified by the nodeName parameter to the name specified by the newNodeName parameter.
To change the host name for a given node, use the following wsadmin command:
AdminTask.changeHostName(‘[-nodeName <node_name> -hostName <new_host_name>]’)
This updates the host name for the node specified in the nodeName parameter to the value specified in the hostName parameter.
These commands update all of the necessary WAS configuration, but do keep in mind they do not update any shell or batch files in the environment. This means you need to update the setupCmdLine script included in your WAS installation, and you obviously need to update any of your custom scripts that have hard coded values for node and host names.
Dustin's Blog 
January 27, 2010 at 12:55 am |
[…] This post was mentioned on Twitter by Dustin Amrhein, Bleddyn Williams and Stephane WACONGNE, Stephane WACONGNE. Stephane WACONGNE said: @WebSphereClouds thanks a lot for the tip on renaming cellName nodeName & hostName in #websphere app server http://bit.ly/9MpAHz […]
February 11, 2010 at 12:49 pm |
[…] cell, node, and host names across the installations (something you can overcome by using the commands I talked about here), the two installations existed at different file path locations on their respective disks. On the […]
February 16, 2010 at 10:55 am |
Thanks a bunch for this hint – worked like a champ!
One note, though: if you’re changing an ND environment, you need to run the renameCell on both the Deployment Manager and nodeagent instances, then start the Deployment Manager. Once it’s running, run syncNode before starting the nodeagent.
June 30, 2010 at 12:03 pm |
Dustin;
Your post on “Changing cell names, node names, host names” was a great help in transitioning an old Windows 2000 Websphere install to 2003. Had to install on Websphere new server with different host name. Used the instructions to change the Cell/Node/Host name in websphere post install.
July 1, 2010 at 3:18 pm |
Your post really help me thank you
September 22, 2011 at 2:21 am |
Hello there,
I know it’s been well over than one year, but i’ve got a comment/question. We’ve got an ND environment (WPS 6.2.0.3) – golden topology and we followed Doug’s advice as well (quoting)
“One note, though: if you’re changing an ND environment, you need to run the renameCell on both the Deployment Manager and nodeagent instances, then start the Deployment Manager. Once it’s running, run syncNode before starting the nodeagent.”
We’ve observed that the name of the SIBBuses haven’t changed and still contain the old cell name (eg SCA.SYSTEM.uatCELL.Bus – whereas the new cell name is uat-vf-CELL). Do you know how to go about it?Any ideas would be highly appreciated
Thanks a lot in advance
Pavlos
September 22, 2011 at 6:29 am |
Pavlos,
The renameCell command only affects the configuration that specifies the cell name. If other resources in the environment have a naming format somehow tied to the cell, you will need to independently update those. Specifically for the SIBus situation you mention, depending on the underlying version of WAS, you may be able to use the following approach to rename the bus:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.zseries.doc/info/zseries/ae/txml_prop_wccm_object.html
Having said that, this is not something I have had the occasion to try, so I’m not sure it will do what you need.
January 24, 2012 at 10:37 am |
Reblogged this on Mirv in the 'Burgh and commented:
Attn: WebSphere users – this is good to know.