core groups

Thus, core groups do not scale to the same degree as a cell, and large cells will need to be divided into multiple core groups.

The technique requires CGBS configuration if the ODRs and clusters (application deployment targets) are located in different core groups.

The processes that belong to a cluster (or dynamic cluster) cannot span multiple core groups.

CGBS is required in the back-end cell if the clusters (application deployment targets) are located in different core groups.

The Core groups configuration panel is displayed, as shown in Figure 6.

Bridge all of the core groups containing the clusters and the core group containing the proxy server.

Core groups rely on DCS, which uses a reliable multicast message (RMM) system for transport.

Core groups have low latency (only one network hop) between members.

Bridge all of the core groups containing the clusters and the core group containing the ODRs.

WebSphere Application Server V6. 0. 2: Consider multiple core groups as you approach 50 members.

Select the core group that contains the failed server in the Core groups window.

Select the core group that contains these servers in the Core groups window.

This action opens the Core groups configuration panel, as shown previously in Figure 6.

WebSphere Application Server V6. 1 or V7. 0: Consider multiple core groups as you approach 100 members.

Select the core group that is associated with the cluster members in the Core groups window.

This is a collection of core groups that communicate with each other.

If necessary, break large cells into multiple core groups and bridge the core groups together