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.

Exploitation of XCF techniques<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS uses the XCF communication, which<br />

offers three different services:<br />

► Group services<br />

► Signaling services<br />

► Status monitoring services<br />

Only the group service is used for the XCF support for <strong>WebSphere</strong> HA manager.<br />

To use the XCF system service, <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS <strong>V7.0</strong><br />

provides an XCF plug-in that contains XCF user routines, as shown in<br />

Figure 14-8 on page 442.<br />

Become a XCF group member<br />

When the XCF-based protocol is configured as the discovery and failure<br />

detection protocol, then for each <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> core group one<br />

XCF group will be created and the core group members will become active<br />

members of this XCF group.<br />

To become an active member of a XCF group, during startup of a core group<br />

member (for example a node agent) the IXCJOIN macro is executed. As a result<br />

the member is associated with the address space in which the IXCJOIN was<br />

issued and added to the XCF group. As an active XCF member, it can perform<br />

the following tasks:<br />

► Send and receive messages to other members<br />

► Have its status monitored by XCF<br />

► Be notified of status changes to other members of the group<br />

Each <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> component that can become a core group<br />

member can become a XCF group member.<br />

Status change<br />

The XCF group service has three options of recognizing that a member is no<br />

longer active:<br />

► The corresponding XCF macro is run that disassociates a member from the<br />

XCF group. This happens when the core group member is stopped through<br />

the Integrated Solutions Console.<br />

► The address space (with the core group member in it) that is associated with<br />

the XCF member is terminated. This will result in the termination of the XCF<br />

member.<br />

► The status user routine of the XCF member (and the core group member) is<br />

no longer working. To show that a member is still running, it needs to update a<br />

specific field. If the member fails to update this field within a specified time<br />

interval, XCF schedules the status user routine to determine if a problem<br />

exists.<br />

Chapter 14. <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS 443

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

Saved successfully!

Ooh no, something went wrong!