Node collection

Use this page to manage nodes in the WebSphere Application Server environment. Nodes group managed servers. The table lists the managed and unmanaged nodes in this cell. The first node is the deployment manager. Add new nodes to the cell and to the list by clicking Add Node.

To view this administrative console page, click System administration > Nodes.

Name

Specifies a name for a node that is unique within the cell.

A node corresponds to a physical computer system with a distinct IP host address. The node name is usually the same as the host name for the computer.

Both IPv4 and Internet Protocol V6 (IPv6) are now supported by WebSphere Application Server, but there are restrictions that apply to using both IPv4 and IPv6 in the same cell. Note that when you add a node to a cell, the format in which you specify the name is based on the version of IP the node will be using.

V

Product name and version number of the node.

The product version is the version of a WebSphere Application Server for managed nodes.

For unmanaged nodes on which you can define Web servers, the version displays as not applicable

The base edition of WebSphere Application Server is listed in the version column as Base. The express edition of WebSphere Application Server is listed in the version column as Express. The Network Deployment product is listed in the version column as ND.

The product in the version column indicates the product that you used to create the profile, not the type of profile that you installed. For example, if you use the Network Deployment product to install a profile type of application server, the version column indicates ND.

Discovery protocol

Protocol that servers use to discover the presence of other servers on this node.

The possible protocol options follow:

UDP

User Datagram Protocol (UDP)

TCP

TCP

Status

Indicates that the node is either synchronized, not synchronized, unknown, or not applicable.

	Synchronized	The configuration files on this node are synchronized with the deployment manager.
	Not synchronized	The configuration files on this node are not synchronized with the deployment manager and are out-of-date. Perform a synchronize operation to get the latest configuration changes on the node.
	Unknown	The state of the configuration file cannot be determined because the node agent cannot be reached for this node.
	Not applicable	The status column is not applicable for this node because the node is an unmanaged node.

Sub-topics

Related concepts

Related tasks

Related Reference

Reference topic