+

Search Tips   |   Advanced Search

Node group


A node group is a collection of managed WebSphere Application Server nodes. They define a boundary for server cluster formation.

 

Node groups

Nodes in node groups need to be similar in terms of...

The dmgr does no validation to guarantee that nodes in a given node group have anything in common.

Initially, all Application Server nodes are members of the default node group:

DefaultNodeGroup

Node groups are optional and are established at the discretion of the WAS administrator.

A node can be a member of more than one node group.

Nodes on distributed platforms and the IBM i platform cannot be members of a node group that contains a node on a z/OS platform. However, nodes on distributed platforms and nodes on the IBM i platform can be members of the same node group.

To delete a node group, the node group must be empty. The default node group cannot be deleted.

 

Sysplex node groups

A sysplex node group is a node group unique to the z/OS operating system. The sysplex node group includes a sysplex name and a z/OS operating system location service configuration. A sysplex is a collection of z/OS systems that cooperate by using certain hardware and software products to process workloads. We cannot explicitly create a sysplex node group. The z/OS operating system creates sysplex node groups in the following ways:

We cannot remove a node from a sysplex node group. However, if a node is the only member of a sysplex node group, we can add that node to an empty node group. The empty node group is converted into a sysplex node group and the former sysplex node group of the node is converted into a regular node group.

We cannot delete a node group that is a sysplex node group.

 

Example: Using node groups

Node groups govern which nodes can be used together to form a cluster.

Assume the following...

Applications that exploit WebSphere Business Integration Server Foundation functions can run successfully only on nodes six, seven, and eight. Therefore, clusters that host these applications can be formed only on nodes six, seven, and eight. To define a clustering policy that guides users of the WebSphere cell into building clusters that can span only predetermined nodes, create an additional node group called WBINodeGroup, for example. Add to the node group nodes six, seven, and eight. If we create a cluster on a node from the WBINodeGroup node group, the system allows only nodes from the WBINodeGroup node group to be members of the cluster.

Example 2 Assume the following information:

Applications that exploit z/OS functions in the PLEX1 sysplex can run successfully on nodes five and six only. Therefore, clusters that host these applications can be formed only on nodes five and six. The required separation of distributed platform nodes and IBM i platform nodes from z/OS system nodes establishes a natural clustering policy that guides users of your Application Server cell into building clusters that can span only predetermined nodes. If we create a cluster on a node from the PLEX1NodeGroup node group, the system allows only nodes from the PLEX1NodeGroup node group to be members of the cluster.



Subtopics

Example: Using node groups
Manage node groups
Create clusters