Adding, managing, and removing nodes

We can add a node, select the discovery protocol for a node, define a custom property for a node, stop servers on a node, and remove a node.

A node is a grouping of managed or unmanaged servers. We can add both managed and unmanaged nodes to the WAS topology. If we add a new node for an existing WebSphere Application Server to the network deployment cell, you add a managed node. If we create a new node in the topology for managing web servers or servers other than WebSphere Application Servers, you add an unmanaged node.

We can recover an existing managed node of a deployment manager cell. One of the options to add a managed node enables you to quickly recover a damaged node. The option is similar to the -asExistingNode parameter of the addNode command.

To view information about nodes and managed nodes, use the Nodes page. To access the Nodes page, click System administration > Nodes in the console navigation tree.

Manage nodes on an application server through the wsadmin scripting tool, through the Java APIs, or through the console. Perform the following tasks to manage nodes on an application server through the console.

Restriction: The addNode function in the console might fail on non-English, single-byte Windows operating systems when there are non-ASCII characters in the profile name, cell name, or node name. This problem is caused by a code page issue on Windows operating systems. To work around this problem, run the addNode command from the command line rather than from the console on non-English, single-byte Windows operating systems if there are non-ASCII characters in the profile name, cell name, or node name.


What to do next

If we changed a node configuration, examine the configuration changes.


Subtopics


Related concepts

  • Managed and unmanaged nodes
  • Node groups
  • Managed object metadata


    Related tasks

  • Get started with wsadmin scripting

  • Core group servers collection
  • Custom property settings