The removeNode command returns a node from an ND distributed administration cell to a stand-alone appserver 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 ND 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 appservers added on the node do not contain any applications. To deal with this situation, add the node and use the dmgr to manage the applications. Add the applications to the servers on the node after the node is incorporated into the cell.
Run the removeNode command completes the following actions:
- Stops all of the running server processes in the node, including the node agent process
- Removes the node configuration documents from the cell repository by sending commands to the dmgr
- Copies the original appserver 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.
Remove a node that was federated as part of cell profile creation
An appserver node that is built as part of a cell profile creation does not have an original configuration. Therefore, the removeNode command does not restore the node to a usable base configuration. If we use the removeNode command on a node created during cell profile creation, then the command indicates that the node removal utility cannot remove the node and restore the node to a base configuration.
To successfully remove a node that was federated as part of a cell profile creation, use the manageprofiles command to delete the profile for the node. After the profile for the node is deleted, use the cleanupNode command on the dmgr to remove the node configuration from the cell repository. A new profile can be created using the Profile Management Tool or the manageprofiles command.
SyntaxSee the following removeNode command syntax:
All the following parameters are optional.
- Clean up the local node configuration regardless of whether we can reach the dmgr for cell repository cleanup. After using the -force parameter, we might need to use cleanupNode.sh on the deployment manager.
- -logfile <fileName>
- 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>
- Password for authentication if security is enabled.
- Define the profile of the appserver 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.
- Suppress the progress information that the removeNode command prints in normal mode.
- Replace the log file instead of appending to the current log file.
- -statusport <portNumber>
- 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.
- Generate trace information into a file for debugging purposes.
- -user <name>
- User name for authentication if security is enabled. Acts the same as the -username option.
- -username <name>
- User name for authentication if security is enabled. Acts the same as the -user option.
- Prints a usage statement.
- Prints a usage statement.
The following examples demonstrate correct syntax:
removeNode.sh -trace (produces the removeNode.log file)
Related tasksManage nodes
addNode command best practices
Manageprofiles command: Example for creating a cell profile