Node collection
Use this page to manage nodes in the WAS 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 console page, click System administration > Nodes.
Name
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.
Version
Product name and version number of the node.
The product version is the version of a WAS for managed nodes.
For unmanaged nodes on which we can define web servers, the version displays as not applicable
The base edition of WAS (base) is listed in the version column as Base. The express edition of WAS is listed in the version column as Express. The WebSphere Application Server 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 WAS 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
- Transmission Control Protocol (TCP)
Status
Indicates that the node is either synchronized, not synchronized, unknown, or not applicable.
| Button | Node Status | Description |
|---|---|---|
|
| 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.
After a deployment manager or node agent restart, nodes are assumed to be out of synchronization until the first synchronize operation is performed. |
|
| 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. |
Subtopics
- Node settings
Use this page to view or change the configuration or topology settings for either a managed node instance or an unmanaged node instance. - Add a Windows based node as a Windows service
Use this page to run the node agent as a Windows service.
Related concepts
Related tasks
Add a Windows based node as a Windows service