Perform this task if you want 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.
Before you begin
- Understand the concepts that are described in the Core group Discovery
Protocol and Core group Failure Detection Protocol topics.
- Verify that all of the servers that are members of the core group are
at Version 7.0 or higher. If the core group contains servers at a version
earlier than 7.0, then you must use the default Discovery Protocol and the
default Failure Detection Protocol.
- Verify that all of the servers that are members of the core group are
running on the same operating system. The alternative protocol provider can
only be used in an homogenous environment. If the cell contains any servers
that are running on different operating systems, you must use the default
Discovery Protocol and default Failure Detection Protocol. For example, you
cannot have an environment where some of the members of the core group are
running on z/OS and other members are running on a Linux operating system.
- Verify that your system meets all of the system requirements for your
alternate protocol provider.
For example, if you are going to use the z/OS
Cross-system Coupling Facility as your alternate protocol provider, you must
verify that the z/OS VTAM® component is configured to start with the XCFINIT
parameter set to YES. Starting VTAM with XCFINIT=YES
specified in ATCSTRxx enables TCP/IP to utilize the services that the z/OS
Cross-system Coupling Facility provides. See the z/OS product library for
more information about VTAM and the z/OS Cross-system Coupling Facility.
About this task
To select an alternate protocol provider for a core group, complete
the following steps.
Procedure
- In the administrative console, click core_group_name.
- In the Additional Properties section, click .
- Select
- In the field,
specify the fully qualified class name of the factory that is 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.
- Click and
then click .
- Select , and then click .
- Restart all members of the core group.
Results
After the servers restart, all communication between members of this
core group is established and monitored by the selected alternate protocol
provider.