Configure the core group bridge between core groups that are in different cells

The core group bridge service can be configured for communication between core groups. Use an access point group to define the core groups that communicate. Use this task to configure communication between core groups that are in different cells.

You should have two or more core groups that are in different cells. Core groups are a statically defined component of the high availability manager. See Core groups for more information about core groups.

If there are multiple core groups within any of the cells, configure an access point group between the core groups in the cell before you can enable communication outside of the cell. See Configuring communication between core groups that are in the same cell for more information.

Use the core group bridge service to share the availability status of the servers in each core group among all the configured core groups. Enable the core group bridge only when the service is required by a WebSphere Application Server component. For example, the core group bridge is required when configuring an EJB backup cluster. Configure a backup EJB cluster in a different cell to continue servicing requests when the primary cluster fails. See Creating backup clusters for more information.

When you configure core group communication between core groups that are in different cells, configure an access point in each core group that has the same name. This task uses the DefaultAccessPointGroup access point group, but you can create and use another access point group. However, the access point group name is the same in both cells.

With WebSphere Application Server, Version 6.0.2 or later, you can define the CGB_ENABLE_602_FEATURES custom property. By enabling this property, you can add core group bridge servers to the configuration without restarting the other servers in the configuration. When you add a core group bridge server in one cell, you no longer need to modify the configuration in the other cell to include peer ports for the core group bridge server. Instead of manually configuring peer ports in each of the cells, you can configure the peer ports in one cell and let the other cell discover the peer ports for the first cell.

If you decide to use the CGB_ENABLE_602_FEATURES custom property, before you begin decide which cell will be the listener cell and which cell will initiate contact with the other cells. The listener cell does not contain any peer access points or peer ports for the other cells in the configuration. For example, in a configuration that contains a secured cell and an unsecured cell, configure the unsecured cell as the listener, because it cannot access information about the secured cell. Configure the core group bridge service on the listener cell first.

CAUTION:

Do not configure the CGB_ENABLE_602_FEATURES custom property if you have already configured the FW_PASSIVE_MEMBER custom property. Any server that has this property cannot initiate contact with other systems in the configuration. For more information about the FW_PASSIVE_MEMBER custom property, see Core group and core group bridge custom properties.

Complete the following set of steps for each of the cells in your configuration.

1. Configure bridge interfaces for your core group access point.

   1. In the administrative console, click Servers > Core groups > Core group bridge settings > Access point groups > DefaultAccessPointGroup > Core group access points > CGAP_1\DefaultCoreGroup > Show detail > Bridge interfaces > New .

   2. Select a node, server, and transport channel chain that becomes your bridge interface.

   3. Click Apply.

   4. Repeat this set of steps to add more bridge interfaces to the core group access point. Define at least two bridge interfaces for each core group access point to back up your configuration. The bridge interfaces that you select should all have the same transport channel chain.

2. If you are enabling the WebSphere Application Server Version 6.0.2 feature for the core group bridge, define the CGB_ENABLE_602_FEATURES custom property on all the access point groups in your configuration. By enabling this property, you can add core group bridge servers to the configuration without restarting the other servers in the configuration.

   CAUTION:

   Do not configure this custom property if you have already configured the FW_PASSIVE_MEMBER custom property. Any server that has this property configured cannot initiate contact with other systems in the configuration. For more information about the FW_PASSIVE_MEMBER custom property, see Core group and core group bridge custom properties.

   1. In the administrative console, click Servers > Core groups > Core group bridge settings > Access point groups > DefaultAccessPointGroup >
      Custom properties > New .

   2. Type the name as CGB_ENABLE_602_FEATURES and set the value to true .

   3. Click Apply and save your configuration.
   When you complete this step on all the access point groups in your configuration, you can add a bridge interface to one of the cells. Then, you can save the configuration so that it is propagated to all of the nodes. Then, instead of restarting all of the application servers, you need to restart the new bridge interface server only.

3. Add peer access points and peer ports to your access point group.

   If you enabled the CGB_ENABLE_602_FEATURES custom property, you do not need to add peer access points or peer ports to the listener cell. Add a peer access point for each core group that is in another cell. Within each peer access point, you should configure a peer port that corresponds to each bridge interface in the other cell. Before you add a peer access point, you should have the following information about the other cell:

   • cell name

   • core group name

   • core group access point name

   • host and port information. The host and port corresponds to the bridge interfaces that are configured in the other cell. Specify a peer port for each bridge interface that is in the other cell.

   1. In the administrative console, click Servers > Core groups > Core group bridge settings > Access point groups > DefaultAccessPointGroup > Peer access points > New .

   2. Specify the information for your peer access point and click Next .

   3. Select Use peer ports . Specify the host and port information for your peer cell. For example, if you defined a bridge interface in cell_x, you should use that configuration information for your peer port in cell_y.

   4. Click Next and then Finish. Save your configuration.
   If there is more than one bridge interface defined in your peer cell, you should add additional peer ports for each bridge interface.

   1. Click Peer_access_point_name > Show detail > Peer ports > New .

   2. Enter the host name and port.

   3. Click Apply and save your changes.

ResultYou configured the core group bridge between core groups that are in different cells.

Example

Following is an example of a configuration between two core groups that are in two different cells. Each cell has a defined access point group, DefaultAccessPointGroup, which contains one core group access point for the core group that is in the cell, and a peer access point for the other cell.

What to do next

Related tasks
Setting up a high availability environment