Manage nodes

 

+

Search Tips   |   Advanced Search

 

Overview

This topic describes how to...

• Add a node
• Select the discovery protocol for a node
• Define a custom property for a node
• Stop servers on a node
• Remove a node

A node is a grouping of managed or unmanaged servers. You can add both managed and unmanaged nodes to the WAS topology. If you add a new node for an existing WAS to the ND cell, you add a managed node. If you create a new node in the topology for managing Web servers or servers other than WAS servers, you add an unmanaged node.

To view information about nodes and managed nodes,

System Administration | Nodes

You can manage nodes on an appserver through the wsadmin scripting tool, through the Java APIs, or through the console. Perform the following tasks to manage nodes on an appserver through the console.

 

Procedure

 

• Add a node.

  1. Go to the Nodes page and click Add Node. Choose whether you want to add a managed or unmanaged node, and click Next.

  2. For a managed node, verify that an appserver is running on the remote host for the node that you are adding. On the Add Node page, specify a host name, connector type, and port for the appserver at the node you are adding.

  3. For a managed node, perform one of the following sets of actions listed in the table:

     If the deployment manager is on	And the node that you add to the cell is on	Complete the appropriate set of actions:
     The distributed platform or the i5/OS platform	The distributed platform or the i5/OS platform	Optionally specify a node group and a core group. Click OK.
     The distributed platform or the i5/OS platform	A z/OS system	Specify a node group that contains nodes from the same sysplex as the node you are now adding. If no such node group exists, create a node group and then specify that node group. Optionally specify a core group. Click OK.
     A z/OS system	The distributed platform or the i5/OS platform	Specify a node group that contains distributed nodes. If no such node group exists, create a node group and then specify that node group. Optionally specify a core group. Click OK.

     For the node group option to display, a group other than the default node group must first be created. Likewise, for the core group option to display, a group other than the default core group must first be created. For managed nodes, another console panel is displayed if the node to federate is on a Windows operating system. Specify on the panel whether you want to register the node agent to run as a Windows service. If security is enabled, you can optionally enter the local operating system user name and password under which you will run the service. If you do not specify a user name and password, the service runs under the local system identity. When you run remove the node, the node agent is de-registered as a Window service.

  4. For an unmanaged node, on the Nodes > New page, specify a node name, a host name, and a platform for the new node. Click OK.

  The node is added to the WAS environment and the name of the node is displayed in the collection on the Nodes page.

  Both IPv4 and IPv6 are now supported by WAS, but restrictions do apply when using both IPv4 and IPv6 in the same cell. When you add a node to a cell, the format in which you specify the name is based on the version of IP that the node is using. For details, see IP version considerations for cells. On completing this step, you will have added one or more nodes.

  When nodes are added while LDAP security is enabled, the following exception is generated in the deployment manager System.out log under certain circumstances. If this happens, restart the deployment manager to resolve the problem.

  0000004d ORBRas E com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl  createSSLSocket ProcessDiscovery : 0 JSSL0080E: javax.net.ssl.SSLHandshakeException - 
  The client and server could not negotiate the desired level of security. 
  Reason?com.ibm.jsse2.util.h: No trusted certificate found 
  
  

   

• Select the discovery protocol.

  If the discovery protocol that a node uses is not appropriate for the node, select the appropriate protocol. On the Nodes page, click the node to access the Settings for the node. Select a value for Discovery Protocol. User Datagram Protocol (UDP) is faster than 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 because 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.

  Nodes | nodename | Settings for the node | Custom Properties | Property collection page | New

   

• Synchronize the node configuration.

  If you add a managed node or change a managed node configuration, synchronize the node configuration. On the Node Agents page, ensure that the node agent for the node is running. Then, on the Nodes page, select the check box beside the node whose configuration files you want to synchronize and click Synchronize or Full Resynchronize.

  Clicking either option 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 action is important if automatic configuration synchronization is disabled, or if the synchronization interval is set to a long time, and a configuration change is made to the cell repository that needs to replicate 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. 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 is no mismatch between node and cell configuration after this operation is performed. This operation can take longer than the Synchronize operation.

  Unmanaged nodes cannot be synchronized.

   

• Stop servers on a node.

  On the Nodes page, Select the check box beside the managed node whose servers to stop running, and click Stop.

   

• Remove a node.

  On the Nodes page, Select the check box beside the node to delete and click Remove Node. If you cannot remove the node by clicking Remove Node, remove the node from the configuration by clicking Force Delete.

   

• View node capabilities.

  Review the node capabilities, such as the product version through the console. You can also query them through the Application Server API or the wsadmin tool.

  WAS versions for WAS are as follows: The base edition of WAS is listed in the version column as Base. The express edition of WAS is listed in the version column as Express. The ND product is listed in the version column as ND.

---

Node collection

Add managed nodes

Node installation properties

 

Related concepts

Node
Node group
Managed object metadata

 

Related Reference

Core group servers collection