Manage nodes
Overview
A node is a grouping of managed servers. To manage nodes, use the Nodes page at...
System Administration > Nodes
...in the console navigation tree.
Steps for this task
- Add a node.
- Ensure that an appserver is running on the remote host for the node that you are adding. Also ensure that the application server has a SOAP connector on the port for the host.
- Go to the Nodes page and click Add Node. On the Add Node page, specify a host name and SOAP connector port for the deployment manager, then click OK.
The node is added to the WAS environment and the name of the node appears in the collection on the Nodes page.
- If the discovery protocol that a node uses is not appropriate
for the node, select the appropriate protocol. On the Nodes page, click on the node to access the settings for the node.
Select a value for Discovery Protocol. User Datagram Protocol (UDP)
is faster than Transmission Control Protocol (TCP). However, TCP is more reliable
than UDP because UDP does not guarantee the delivery of datagrams to the destination.
The default of TCP is the recommended value.
For a node agent or deployment manager, use TCP or UDP.
A managed process uses multicast as its discovery protocol. The discovery protocol is fixed for a managed process. The main benefit of using multicast on managed processes is efficiency for the node agent. Suppose you have forty servers in a node. A node agent that uses multicast sends one broadcast to all forty servers. If a node agent did not use multicast, it would send discovery queries to all managed processes one at a time, totaling forty sends. Additional benefits of using multicast are that you do not have to configure the discovery port for each server or prevent port conflicts since all servers in one node listen to one port instead of to one port for each server.
On the Windows platform, multicast requires a router. If you run WAS on the Windows platform, but the machine the Application Server is on is not connected to the network, the multicast address is not shared with the appservers.
- Define a custom property for a node.
- On the Nodes
page, click on the node for which you want to define a custom property.
- On the settings
for the node, click Custom Properties.
- On the Property collection page, click New.
- On the settings page for a property instance, specify a name-value pair and a description for the property, then click OK.
- On the Nodes
page, click on the node for which you want to define a custom property.
- If you added a node or changed a node's configuration, synchronize the node's configuration. On the Node Agents page, ensure that the node agent for the node is running. Then, on the Nodes page, put a checkmark in the check box beside the node whose configuration files you want to synchronize and click Synchronize or Full Resynchronize.
Clicking either button sends a request to the node agent for that node to perform a configuration synchronization immediately, instead of waiting for the periodic synchronization to occur. This is important if automatic configuration synchronization is disabled, or if the synchronization interval is set to a long time, and a configuration change has been made to the cell repository that needs to be replicated to that node. Settings for automatic synchronization are on the File Synchronization Service page.
Synchronize requests that a node synchronization operation be performed using the normal synchronization optimization algorithm. This operation is fast but might not fix problems from manual file edits that occur on the node. So it is still possible for the node and cell configuration to be out of synchronization after this operation is performed.
Full Resynchronize clears all synchronization optimization settings and performs configuration synchronization anew, so there will be no mismatch between node and cell configuration after this operation is performed. This operation can take longer than the Synchronize operation.
- Stop servers on a node. On the Nodes
page, put a checkmark in the check box beside the node whose servers
you want to stop running and click Stop.
- Remove a node. On the Nodes page, put a checkmark in the check box beside the node you want to delete and click Remove Node.
Node
Node collection