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

14.4.3 HFS structure
The HFS structure of the WebSphere Application Server for z/OS V7.0 is built out
of the components, seen in Table 14-1 (with default location).
Table 14-1 WebSphere Application Server for z/OS file system structure
FMID Component HFS path
H28W700 Application server itself /usr/lpp/zWebSphere/V7R0
JIWO700 Optional Material /usr/lpp/zWebSphere_OM/V7R0
JDYZ700 Secure Proxy Server /usr/lpp/zWebSphere_SPS/V7R0
HHAP700 IBM HTTP Server V7 /usr/lpp/IHSA/V7R0
14.5 XCF support for WebSphere HA manager
This section describes the WebSphere Application Server support for the z/OS
Cross Coupling Facility (XCF) protocol. It also gives an overview of WebSphere’s
HA manager and the default protocol used for discovery and failure detection in
an application server cluster.
14.5.1 XCF support overview and benefits
WebSphere Application Server for z/OS V7.0 adds the option to use the XCF
system services to monitor the status of cluster components instead of the
default common code base technique. This kind of implementation has two main
values:
► Reduced CPU Overhead
The usage of the XCF significantly reduces the overhead that comes through
the ping packets sent by each core group member. This is noticeable during
CPU idle times.
► Improved interval for failure detection
While the default interval used in the original protocol (180 seconds) was not
convenient for every environment, the usage of the XCF system service
reduces this time. The default settings provide information after 90 seconds.
These values can still be adjusted by the system programmer.
438 WebSphere Application Server V7.0: Concepts, Planning, and Design