removeNode command

The removeNode command returns a node from a WAS 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 WAS 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.

Best practice: If the applications were modified in a feature pack environment, uninstall and reinstall the application into the base configuration after removing the node. This process ensures that your changes are not lost when removing a node configured for the feature pack. No action is necessary if the applications were not modified.bprac

Running the removeNode command completes the following actions and system conditions:

• 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 deployment manager

  • Copies the original application server cell configuration that existed when the node was added and the application originally install into the active configuration

• System conditions

  • The EAR files remain on the deployment manager.

  • The installed application remains on the deployment manager.

  • No changes you made after federating the node will be restored to base node.

  • You have the old base node that existed before federation. After federating, you still have the original configuration for the node, the servers, and the original applications in their original states.

  • If we federate again, you overwrite any updates on the deployment manager.

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 WAS Network Deployment distributed administration cell to a stand-alone application server installation.

We must have the following privileges or authorities to use the removeNode command:

• (dist)(zos) We must have Administrator privileges to use the removeNode function.

• (iseries) Your user profile must have *ALLOBJ authority or must have read and execute authority for the removeNode Qshell script.

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 application server 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 that was 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 deployment manager to remove the node configuration from the cell repository. A new profile can be created using the Profile Management Tool or the manageprofiles command.

(zos) To successfully remove a node that was federated as part of a cell profile creation, use the Profile Management Tool to delete the profile for the node. After the profile for the node is deleted, use the cleanupNode command on the deployment manager to remove the node configuration from the cell repository. We can create a new profile using the Profile Management Tool.

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 we can reach the deployment manager for cell repository cleanup. After using the -force parameter, we might need to use the cleanupNode command 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.

(dist)(iseries) -profileName

Defines the profile of the application server process in a multiple-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

Suppress 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 <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.

-trace

Generates 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.

-help

Prints a usage statement.

-?

Prints a usage statement.

Usage scenario

The following examples demonstrate correct syntax:

removeNode -quiet

removeNode.sh -trace (produces the removeNode.log file)

(zos)

removeNode -trace (produces the removeNode.log file)

(iseries)

removeNode -profileName mynode removeNode -trace (produces the removeNode.log file)

Related tasks

Adding, managing, and removing nodes

addNode command best practices

addNode command