HP Serviceguard Toolkit for Oracle E-Business Suite User Guide
Table Of Contents
- HP Serviceguard Toolkit for Oracle E-Business Suite User Guide
- Contents
- 1 Introduction
- 2 Configuring EBS and SGeEBS
- Configuring EBS for SGeEBS
- EBS as Serviceguard package
- Configuring SGeEBS for EBS
- SGeEBS with Serviceguard Continentalclusters
- 3 Troubleshooting
- 4 Support and other resources
- Index

1 Introduction
Serviceguard is the software (or middleware) that gives you the ability to create a High Availability
(HA) clustering environment. HP Serviceguard extension for E-Business Suite (SGeEBS) extends
HP Serviceguard failover cluster capabilities to Oracle E-Business Suite environments. It also protects
the application tier of Oracle Enterprise Business Suite (EBS).
Serviceguard Manager Version B.03.10 included in Serviceguard version 11.20 with April 2011
patch supports HP Serviceguard Extension for Oracle E-Business Suite Toolkit Version B.02.00.
SGeEBS Overview
SGeEBS consists of configuration templates and scripts for easy integration of EBS with Serviceguard.
The Database (DB) and Applications (APPS) tiers of EBS are packaged into two separate failover
packages. Enterprise Cluster Master Toolkit (ECMT ) for Oracle needs to be used to package the
database tier.
The shell scripts are used to start, stop, and monitor the health of APPS and DB tier packages of
EBS. These scripts get integrated with Serviceguard Master Control Script.
The EBS control scripts generated by AutoConfig need not be modified to integrate with Serviceguard
packages.
EBS APPS tier
The HP approach for configuring the APPS tier within the Serviceguard cluster draws upon the
standard EBS implementation technique of defining application services over multiple servers so
that any active node can process user workload.
Applications tier instance with a single APPL_TOP and INST_TOP
SGeEBS design uses the concept of sharing the APPS tier file system by multiple APPS tier servers.
The EBS APPS tier file system should be installed in the shared disk storage that can be shared by
multiple instance-specific information defined for each APPS tier servers in the cluster. The
instance-specific file system can be installed locally in the respective servers or it can be installed
in the shared storage. During the APPS tier startup process, Serviceguard automatically relocates
the storage to be accessible on the active APPS tier server. The storage is mounted at standard file
system mount points ready for EBS initialization to begin.
Advantages of installing instance-specific information in the shared storage
Regardless of which server the applications tier is currently running on, the instance-specific
information for that and the inactive server is accessible within the shared file system. This allows
reports, logs, and output files for both the active and the inactive servers in the cluster to be
available, if required.
A single shared storage area for APPS tier file system and instance-specific information is particularly
useful when an EBS instance fails for some unexpected reason. When a failure occurs, Serviceguard
automatically executes a failover of the APPS tier to the alternate node which includes moving the
shared storage from the failed server to the operational system. Within the shared storage the
instance-specific files for the failed EBS instance are now accessible on the operational system and
so problem determination and root cause analysis of the original failure can be investigated.
4 Introduction