The removeNode command returns a node from a Network Deployment distributed administration cell to a base WAS installation. You must run this command from the $WAS_HOME/bin directory of a WAS installation.
The removeNode command only removes the node-specific configuration from the cell. This command does not uninstall any applications that were installed as the result of executing an addNode command. Such applications can subsequently deploy on additional servers in the Network Deployment cell. As a consequence, an addNode command with the -includeapps option executed after a removeNode command does not move the applications into the cell because they already exist from the first addNode command. The resulting appservers added on the node do not contain any applications. To deal with this situation, add the node and use the deployment manager to manage the applications. Add the applications to the servers on the node after it is incorporated into the cell.
Depending on the size and location of the new node you remove from the cell, this command can take a few minutes to complete.
The command syntax is as followsAll arguments are optional.removeNode [options]
The following options are available for the removeNode command...
-quiet Suppresses the progress information that the removeNode command prints in normal mode.
-logfile <fileName> Specifies the location of the log file to which information is written.
-replacelog Replaces the log file instead of appending to the current log.
-trace Generates trace information into a file for debugging purposes.
-statusport <portNumber> Specifies that an administrator can set the port number for the node agent status callback.
-username <name> Specifies the user name for authentication if security is enabled. Acts the same as the -user option.
-user <name> Specifies the user name for authentication if security is enabled. Acts the same as the -username option.
-password <password> Specifies the password for authentication if security is enabled.
-force Cleans up the local node configuration regardless of whether you can reach the deployment manager for cell repository cleanup. After using the -force parameter, you may need to use the cleanupNode command on the deployment manager.
-help Prints a usage statement.
-? Prints a usage statement.
The removeNode program...
- Stops all of the running server processes in the node, including the node agent process.
- Removes the configuration documents for the node from the cell repository by sending commands to the deployment manager.
- Copies the original appserver cell configuration into the active configuration.
The following examples demonstrate correct syntaxremoveNode -quiet removeNode -trace (produces the removeNode.log file)