29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Member notification<br />

To notify the other core group members of a status change, an XCF group user<br />

routine is executed.<br />

The group user routine enables XCF to notify active members of a group when<br />

there is a change in the operational state of any other member in the group, or a<br />

change to the status of any system in the sysplex.<br />

This triggers the HA coordinator inside <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS<br />

to perform neccessary actions.<br />

14.5.5 Activating XCF support for HA manager<br />

To take advantage of the enhanced HA manager discovery and failure<br />

mechanism, the following requirements must be satisfied: (Otherwise you have to<br />

use the default policy.)<br />

► The z/OS VTAM® component must be configured to start XCFINIT = YES, to<br />

enable TCP/IP to use the XCF service.<br />

► All core group members must be on Version 7 of <strong>WebSphere</strong> <strong>Application</strong><br />

<strong>Server</strong><br />

► All core group members must be running on z/OS<br />

► Should the core group be bridged to another core group, then all bridged<br />

groups must be reside on z/OS in the same sysplex<br />

When these prerequisites are met, perform the following steps to activate the<br />

XCF support in the Integration Solutions Console:<br />

1. Select <strong>Server</strong>s → Core Groups → Core Group settings.<br />

2. Select the core group you want to modify.<br />

3. In the selected core group, select Discovery and failure detection.<br />

4. Check the Use alternative protocol providers radio box and enter the fully<br />

qualified class name for the z/OS factory that is used to create the alternate<br />

protocol provider, com.ibm.ws.xcf.groupservices.LivenessPluginZoSFactory,<br />

as seen in Figure 14-9 on page 445.<br />

444 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!