Use this page to create a core group or to edit an existing core group. A core group is a component of the high availability manager function. It can contain standalone servers, cluster members, node agents and the deployment manager. A core group must contain at least one node agent or the deployment manager.
Before you create a core group understand the relationship of core groups in a high availability environment and know how you intend to use each core group.
To view this administrative console page, click Servers > Core groups > Core group settings > New or Select an existing core group for editing.
On the Configuration tab, you can edit fields. On the Runtime tab, you can look at read-only information.
After you specify your core group settings, click Apply before defining additional properties or setting up a core group bridge.
Extended information about the core group fields:
Specifies the name of the core group. This field can only be edited when you create new core groups.
If you are defining a new core group, specify a name that is unique among the existing core groups. It is helpful to other WebSphere Application Server administrators if the name helps define the use of this core group and if it is consistent with the names of the other core groups in the cell. This field can contain alpha and numeric characters. The following characters cannot be used in this field:
# \ / , : ; " * ? < > | = + & % '
Also, the name cannot begin with a period (.) or a blank space. A blank space does not generate an error. However, leading and trailing blank spaces are automatically deleted.
For example, DefaultCoreGroup is the name of the core group that contains the deployment manager server process.
Specifies a description of the core group. In environments where there are multiple system administrators this field can help these administrators understand the overall organization of the core groups. The supported length of this field is quite large. However, long descriptions take time to load and can cause a delay when displaying the page.
Example: "Default Core Group. The default core group cannot be deleted." is the description of the DefaultCoreGroup.
Specifies the number of coordinators for this core group. The coordinator is the aggregation point for high availability manager information. The coordinator determines group membership and communicates state and status to the other members of the core group.
The default value is one coordinator, although multiple coordinators are advisable for large core groups. All of the group data must fit in the memory of the allocated coordinators. One coordinator can run out of memory in a system with a large core group, which can cause the system to work improperly.
Timeransport mechanism to use for communication between members of a core group. This is a required field.
If a core group needs to use the core group bridge service, select Channel framework as the transport mechanism for that core group. If you select Unicast or Multicast, you might receive error message CHFW0029E, which indicates that the transport chain could not be initialized because the address was already in use.
Specifies the name of the channel chain if you select channel framework for the transport type.
The port setting tells the coordinator where to scan for transmissions. When setting this value, verify that you are specifying a port that is not used by another network communication device. Setting a port value that has conflicts causes problems with your high availability manager infrastructure.
Specify the starting Internet Protocol (IP) address of the intended communication area.
Specify the ending IP address of the intended communication area. Plan the network to accommodate scalability.
Specifies one or more name=value pairs as the match criterion for a high availability group. If you specify more than one name=value pair, use a comma to separate the pairs. You can specify an asterisk (*) to obtain the selected information for all of the high availability groups within this core group.
When a WebSphere Application Server component creates a new high availability group, it establishes a map of that group's properties as the group name. This map is used to uniquely identify that high availability group.
After you specify a match criterion or an asterisk:
Example: Suppose the following high availability groups are defined for a core group:
If you specify policy=oneofN in the Group name properties field and then select Show groups, the groups for components A and C are listed.
If you specify owner=smith in the Group name properties field and then select Show groups, the groups for components A, B and C are listed. If you specify all of component C's name properties in the Group name properties field:
name=compC,policy=oneofN,owner=smith
Then select Show groups, only the group for component C is listed. Note that the properties are separated by commas. There are no blank spaces.