removeNode command

The removeNode command returns a node from a Network Deployment distributed administration cell to a stand-alone application server 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 running 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 ran after a removeNode command does not move the applications into the cell because they exist from the first addNode command. The resulting application servers 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 the node is incorporated into the cell.

Running the removeNode command results in the following actions and system conditions:
Remember:
  • After the node is removed from the cell, it will have the applications as they were before the node was added to the cell. Any changes you made after federating will not be included.
  • The removeNode command returns a node from a Network Deployment distributed administration cell to a stand-alone application server installation.
You must have the following privileges or authorities to use the removeNode command:

Depending on the size and location of the new node you remove from the cell, this command can take a few minutes to complete.

Syntax

See the following removeNode command syntax:
removeNode [options]
All the following parameters are optional.

Parameters

The following options are available for the removeNode command:

-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 might need to use the cleanupNode command on the deployment manager.
-logfile <fileName>
Specifies the location of the log file to which trace information is written. By default, the log file is named removeNode.log and is created in the logs directory of the profile for the node being removed.
-password <password>
Specifies the password for authentication if security is enabled.
-profileName [AIX HP-UX Linux Solaris Windows]
Defines the profile of the application server process in a multiprofile installation. The -profileName option is not required for running in a single profile environment. The default for this option is the default profile.
-quiet
Suppresses the progress information that the removeNode command prints in normal mode.
-replacelog
Replaces the log file instead of appending to the current log file.
-statusport
An optional parameter that allows an administrator to set the port number for server status callback. The tool opens this port and waits for status callback from the server just before the server has completely stopped. If the parameter is not set, an unused port is automatically allocated.
-trace
Generates trace information into a file for debugging purposes.
-user <name>
Specifies the user name for authentication if security is enabled. Acts the same as the -username option.
-username <name>
Specifies the user name for authentication if security is enabled. Acts the same as the -user option.
-help
Prints a usage statement.
-?
Prints a usage statement.

Usage scenario

The following examples demonstrate correct syntax:

removeNode -quiet
[AIX HP-UX Linux Solaris Windows] [z/OS]
removeNode -trace (produces the removeNode.log file)



Related tasks
Managing nodes
Related reference
addNode command best practices
addNode command
Reference topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=rxml_removenode
File name: rxml_removenode.html