• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1866
  • Last Modified:

How do rename a node in Websphere 6.1

Hi,
We are running websphere 6.1.0.35 on windows server 2008 sp2.
I would like to rename the node from ctgNode01 to ctgNode03 so that the name is not duplicated when I create our cluster.

I created a script called changeNodeName.py

AdminTask.renameNode('[-nodeName ctgNode01 -newNodeName ctgNode03]')

and ran it using
./wsadmin.sh -lang jython -f /root/scripts/changeNodeName.py

This seemed to partially work in that I now have a ctgNode03, however whenever I restart edthe deployment manager and node agent services then both give me a file not found error when looking for the folder
C:\ibm\WebSphere\AppServer\profiles\ctgAppSrv01\config\cells\ctgCell01\nodes\ctgNode01\servers

I have modified the WAS_NODE value in C:\ibm\WebSphere\AppServer\profiles\ctgAppSrv01\setupCmdLine to ctgNode03

What else do I need to do to get the services to start correctly?  Why would the still be trying to open a file under the ctgNode01 folder.

Do I need to delete and recreate the two services?  If so how do I find out the command to recreate the deployment manager service?

Thanks
Tim
0
fowlow
Asked:
fowlow
  • 4
  • 2
2 Solutions
 
fowlowAuthor Commented:
I have also deleted the temp, tranlog and wstemp folders to ensure I don't have a caching issue.
0
 
HonorGodCommented:
I was able to find the following information from this documentation page:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tagt_rename_dnodes.html

--------------------------------------------------------------------------------
4. ...

At this point, the renameNode command renames the managed node, but does not modify the deployment manager node configuration. Thus, the deployment manager does not restart.

5. Modify the WAS_NODE variable in the profile_root /deployment_manager_name/bin/setupCmdLine file so that it references the new managed node name.
--------------------------------------------------------------------------------

  Is this what you need?
0
 
fowlowAuthor Commented:
Issue resolved by running the renameNode command which is found in the bin folder. I then restarted the IBM services and deleted the temp and tranlog folders.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
fowlowAuthor Commented:
Issue resolved
0
 
fowlowAuthor Commented:
Restart IBM Services is helpful.
0
 
HonorGodCommented:
Thanks for the grade & points.

Good luck & have a great day.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now