Using HP Serviceguard extension for Oracle E-Business Suite B.01.00, September 2010

3. /opt/cmcluster/ebs/common/apps - (Files of APPS Tier)
ebsapps.conf - EBS APPS user configuration file
toolkit.sh - Wrapper used from SG run script to invoke EBS APPS Tier
haebsapps.sh - Main shell script - for starting, Stopping EBS APPS
Tier
haapps.sh - Second level scripts to start/stop EBS Apps Tier
servers
ebsapps.mon - Called by haebsapps.sh to monitor EBS Apps Tier servers
4. /etc/cmcluster/modules/ebs - (ADF Module files of EBS)
db - Soft link to db.1
db.1 - ADF module definition for DB Tier
apps - Soft link to apps.1
apps.1 - ADF module definition for APPS Tier
5. /etc/cmcluster/scripts/ebs/db (Module scripts of DB Tier)
tkit_module.sh - DB Tier Module script
tkit_gen.sh - DB Tier Configuration file generator script
6. /etc/cmcluster/scripts/ebs/apps (Module scripts of APPS Tier)
tkit_module.sh - APPS Tier Module script
tkit_gen.sh - APPS Tier Configuration file generator script
SGeEBS is fully modularized and it is not required to modify the
configuration files haebsdb.conf and ebsapps.conf for setting up
SGeEBS in a cluster. These configuration files are provided for
future usage for supporting SGeEBS on HPVM guests.
G. SGeEBS Configuration Example
Follow the instructions in the chapter "Building an HA Cluster
Configuration" in the manual "Managing HP Serviceguard" to create the
logical volume infrastructure on shared disks. The disk must be
available to all clustered nodes that will be configured to run
SGeEBS. Create file systems on all logical volumes on the volume
groups.
SGeEBS can be configured in two different modes. The first mode is
install directory operation in which the scripts remain in the
installation directory. The second mode is the configuration directory
operation. In this mdoe, the user can copy the scripts from the
installation directory (including contents of subdirectories) to the
configuration directory and define this location in the parameter
"TKIT_DIR" in the package configuration file. Scripts in the
configuration directory can be modified by users to add any specific
requirements used by customers. Serviceguard first tries to use the
toolkit.sh scripts in the configuration directory. If the scripts are
not found in the configuration directory, it takes them from the
installation directory.