How to remove the node from the deployment manager profile
Execute the below command to un-federate the profile from the dmgr
Run this command from the bin directory of federated node.
[root@localhost bin]# pwd
/opt/IBM/WebSphere/AppServer/profiles/Custom01/bin
Run this command from the bin directory of federated node.
[root@localhost bin]# pwd
/opt/IBM/WebSphere/AppServer/profiles/Custom01/bin
[root@localhost bin]# ./removeNode.sh
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/Custom01/logs/removeNode.log
ADMU0128I: Starting tool with the Custom01 profile
ADMU2001I: Begin removal of node: localhostNode02
ADMU0009I: Successfully connected to Deployment Manager Server: localhost:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU2010I: Stopping all server processes for node localhostNode02
ADMU0512I: Server nodeagent cannot be reached. It appears to be stopped.
ADMU2021I: Removing all servers on this node from all clusters in the cell.
ADMU2014I: Restoring original configuration.
ADMU2017I: The local original configuration has been restored.
ADMU0306I: Note:
ADMU2031I: Any applications that were uploaded to the localhostCell01 cell
configuration during addNode using the -includeapps option are not
uninstalled by removeNode.
ADMU0307I: You might want to:
ADMU2032I: Use wsadmin or the Administrative Console to uninstall any such
applications from the Deployment Manager.
ADMU0306I: Note:
ADMU2033I: Any buses that were uploaded to the localhostCell01 cell
configuration during addNode using the -includebuses option are not
uninstalled by removeNode.
ADMU0307I: You might want to:
ADMU2034I: Use wsadmin or the Administrative Console to uninstall any such
buses from the Deployment Manager.
ADMU2024I: Removal of node localhostNode02 is complete.
!!!!!!!!!!!!!Done !!!!!!!!
Comments
Post a Comment