Manage nodes

 

+

Search Tips   |   Advanced Search

 

Overview

A node is a group of appservers. Nodes associated with an ND cell become managed nodes. Non-appserver nodes, such as Web servers, are unmanaged 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
• Remove a node

...using...

• admin console
• wsadmin
• Java APIs

 

Add a node using the admin console

1. To add a node to a cell, go to...

   System Administration | Nodes | Add Node | (managed | unmanaged) | Next

2. Start the appserver on the remote host for the node we are adding to the cell.

3. On the Add Node page, specify...
   • Host name
   • Connector type
   • Port
   • Node group
   • Core group

   For managed nodes, a non-default node or core group must first exist before selection options are displayed.

   If dmgr is...	If node is...	Set
   Distributed or i5/OS	Distributed or i5/OS	Optionally specify a node group and a core group. Click OK.
   Distributed or i5/OS	z/OS	Node group containing nodes from the same sysplex as the node we are now adding. If no such node group exists, create and then specify. Optionally specify a core group. Click OK.
   z/OS	Distributed or i5/OS	Node group containing distributed nodes. If no such node group exists, create and then specify. Optionally specify a core group. Click OK.

4. For managed nodes, if federating to a Windows, specify whether to register the node agent to run as a Windows service. If security is enabled, optionally enter the local operating system user name and password.

5. For an unmanaged node, on the page...
   Nodes | New

   ...specify...

   • node name
   • host name
   • 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.

   Restrictions apply when using both IPv4 and IPv6 in the same cell. When adding a node to a cell, the name is based on the IP version the node is using.

6. When nodes are added while LDAP security is enabled, the following exception might be generated in the dmgr System.out log...

   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

   Restart the dmgr to resolve.

7. Select the discovery protocol...

   System Administration | Nodes | node_name

   UDP multicast is faster than TCP, but TCP is more reliable as UDP does not guarantee the delivery of datagrams.

   Multicast benefits...

   • Send one broadcast to all servers, rather than one for each server
   • We do not have to configure the discovery port for each server to prevent port conflicts

   On Windows , multicast requires a router. If we run WAS on Windows , but the machine the appserver is on is not connected to the network, the multicast address is not shared with the appservers.

8. To define custom properties for a node...

   System Administration | Nodes | node_name | Custom Properties | New

9. On the Node Agents page, verify the node agent for the node is running.

10. If automatic configuration synchronization is disabled, or if the synchronization interval is set to a long time, on the Nodes page...

    • Synchronize uses normal synchronization optimization. It is still possible for the node and cell configuration to be out of synchronization.

    • Full Resynchronize clears all synchronization optimization settings and performs configuration synchronization anew, so there is no mismatch between node and cell configuration. This operation will probably take longer than the Synchronize.

    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 we cannot remove the node by clicking Remove Node, remove the node from the configuration by clicking Force Delete.

 

Related concepts

Node collection
Add managed nodes
Node installation properties
Node group
Managed object metadata
Core group servers collection