http://www.wikio.fr WebSphere And Tivoli Tricks: How to delete and re-add a federated node with different ports

Tuesday, May 17, 2011

How to delete and re-add a federated node with different ports

./removeNode.sh -help
Usage: removeNode [-force] [-quiet] [-nowait] [-logfile <filename>]
[-replacelog] [-trace] [-username <username>] [-password <password>]
[-profileName <profile>] [-help]
An example could be that a node was federated with the wrong ports and you may want to remove the node to correctly federate with a port offset. Looking at the node configuration in the administrative client I have ports that are not in the rage I want.



Removing Node:
./removeNode.sh -profileName node01 -username wasadmin -password wasadmin
ADMU0116I: Tool information is being logged in file
/var/apps/was61/node61_01/profiles/logs/removeNode.log
ADMU0128I: Starting tool with the node01 profile
ADMU2001I: Begin removal of node: node61_01
ADMU0009I: Successfully connected to Deployment Manager Server:
dmgr61.webspheretools.com:10004
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU2010I: Stopping all server processes for node node61_01
ADMU0510I: Server nodeagent is now 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.
ADMU9990I:
ADMU0306I: Note:
ADMU2031I: Any applications that were uploaded to the cell61 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.
ADMU9990I:
ADMU9990I:
ADMU0306I: Note:
ADMU2033I: Any buses that were uploaded to the cell61 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 node61_01 is complete.

Re-adding the node with a port offset

./addNode.sh dmgr61.<your_domain.com> 10004 -profileName node01 -username wasadmin -password wasadmin
-startingport 11000
Result:
./addNode.sh dmgr61.webspheretools.com 10004 -profileName node01 -username wasadmin -password wasadmin -startingport 11000
ADMU0116I: Tool information is being logged in file
/var/apps/was61/node61_01/profiles/logs/addNode.log
ADMU0128I: Starting tool with the node01 profile
CWPKI0309I: All signers from remote keystore already exist in local keystore.
ADMU0001I: Begin federation of node node61_01 with Deployment Manager at
dmgr61.webspheretools.com:10004.
ADMU0001I: Begin federation of node node61_01 with Deployment Manager at
dmgr61.webspheretools.com:10004.
ADMU0009I: Successfully connected to Deployment Manager Server:
dmgr61.webspheretools.com:10004
ADMU0507I: No servers found in configuration under:
/var/apps/was61/node61_01/profiles/config/cells/node61_01/nodes/node61_01/servers
ADMU2010I: Stopping all server processes for node node61_01
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: node61_01
ADMU0014I: Adding node node61_01 configuration to cell: cell61
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: node61_01
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
31996
ADMU9990I:
ADMU0300I: The node node61_01 was successfully added to the cell61 cell.
ADMU9990I:
ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone cell61 configuration
have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the cell61 Deployment Manager with
values from the old cell-level documents.
ADMU9990I:
ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the cell61 cell using wsadmin $AdminApp or
the Administrative Console.
ADMU9990I:
ADMU0003I: Node node61_01 has been successfully federated.



I could have used a ports definition file to specify actual ports, but you need to know all the port names required and takes time to set-up. In a large enterprise you would use a portsdef.props file.

No comments:

Post a Comment