The removeNode command returns a node from a Network Deployment
distributed administration cell to a standalone WebSphere Application Server
installation.
For more information about where to run this command,
see the Using command tools article.
You must have Administrator privileges to use the removeNode function.
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 ran
after a removeNode command does not move the applications into the
cell because they already 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
it is incorporated into the cell.
The
removeNode command does the following:
- 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 application server cell configuration into the active
configuration.
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
The command syntax is as follows:
removeNode [options]
All
arguments 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 may 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
- Defines the profile of the Application Server process in a multi-profile
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.
- -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 -trace (produces the removeNode.log file)