You can rename a deployment manager node by modifying the setupCmdLine file
for the node.
Before you begin
Make sure that you create a backup of the deployment manager
configuration including its node configurations. For more information,
see the documentation about the backupConfig command.
About this task
You can use the renameNode command to
modify managed nodes. However, the rename command does not modify
the node name information within the deployment manager configuration.
If you use the renameNode command to modify a deployment
manager node, the deployment manager does not restart. This task resolves
the problem by modifying the setupCmdLine file
so that it references the new node name.
Procedure
- Start the deployment manager.
- Start the wsadmin scripting tool within the deployment
manager profile.
For more information, see the documentation
about starting the wsadmin scripting client.
- Use the renameNode command in the interactive
mode to rename the managed node.
- Using Jacl:
$AdminTask renameNode {-interactive}
- Using Jython string:
AdminTask.renameNode ('[-interactive]')
- Using Jython list:
AdminTask.renameNode (['-interactive'])
- Save the configuration changes.
For more information,
see the documentation about saving configuration changes with the
wsadmin tool.
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.
- Modify the WAS_NODE variable in the profile_root/deployment_manager_name/bin/setupCmdLine file
so that it references the new managed node name.
Results
After you save the setupCmdLine file,
the deployment manager starts successfully.