+

Search Tips   |   Advanced Search

Select an alternate protocol provider for a core group

Perform this task to use an alternate protocol provider instead of the default Discovery Protocol and the default Failure Detection Protocol to monitor and manage communication between core group members. In general, alternate protocol providers, such as the z/OS Cross-system Coupling Facility (XCF)-based provider, use less system resources than the default Discovery Protocol and Failure Detection Protocol, especially during times when the core group members are idle. An alternate protocol provider generally use less system resources because it does not perform the member-to-member TCP/IP pinging that the default protocol providers use to determine if a core group member is still active.

To select an alternate protocol provider for a core group, complete the following steps.


Tasks

  1. In the administrative console, click...

      Servers > Core Groups > Core group settings > core_group_name

  2. In the Additional Properties section, click Discovery and failure detection.

  3. Select Use alternative protocol providers

  4. In the Factory class name field, specify the fully qualified class name of the factory used to create the alternate protocol provider.

    For example, the fully qualified class name for the alternative protocol provider that enables XCF to establish and monitor communication between members of this core group is com.ibm.ws.xcf.groupservices.LivenessPluginZoSFactory.

  5. Click OK and then click Review.

  6. Select Synchronize changes with nodes> Save.

  7. Restart all members of the core group.

After the servers restart, all communication between members of this core group is established and monitored by the selected alternate protocol provider.


Related:

  • Core groups (high availability domains)
  • Core group discovery and failure detection protocols
  • Discovery and failure detection settings
  • Core group custom properties