HP Serviceguard Toolkit for Oracle E-Business Suite User Guide

2 Configuring EBS and SGeEBS
Configuring EBS for SGeEBS
SGeEBS does not require custom modifications of EBS configuration files, application code, or
AutoConfig generated scripts. This ensures that when EBS configuration and patching processes
are performed, unexpected errors do not occur.
SGeEBS uses standard EBS administration scripts to start, stop, and check the status of the database
and applications tiers where possible ensuring that all interaction with EBS is based on Oracle
provided standard and supported interfaces.
EBS APPS tier configuration
At each node in the cluster, an EBS APPS tier instance is defined either through the initial RapidInstall
process for the first server or through the standard cloning process for the second server. When
building the applications tier configurations, the hostname of the underlying physical server is used
so that each instance definition is tied to that specific server node. This will produce multiple
AutoConfig configuration files (one for each node in the cluster) and several node-specific directories
in the instance-specific file system hierarchy.
The APPS Tier will have permanent affinity to the node, on which it is installed. 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. For HP Continentalclusters environment, HP recommends
that, each APPS tier server house their instance-specific information locally and APPS tier file system
in the shared storage.
NOTE: For details of available capabilities and options in sharing an Applications tier file system,
see My Oracle Support Knowledge Document 384248.1, sharing the Application Tier.
For details of the latest Rapid Clone patches and general usage of the tool, see My Oracle Support
Knowledge Document 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone.
In this configuration the user can find an active instance of the EBS system at two URLs. To simplify
access, SGeEBS configuration allows end users to connect using a symbolic hostname. This symbolic
hostname must be associated with a floating IP address (Serviceguard package IP) and is
automatically activated in the currently active APPS instance. The floating IP address is defined for
exclusive use by the APPS as its networking end point and is normally included in the Domain
Name Service.
As users always connect to the EBS implementation using the symbolic hostname, they do not need
to know which APPS systems is currently active or inactive.
From an EBS configuration point of view, this capability is enabled by setting the Web entry point
and external URL parameters within the EBS APPS tier configuration. They are set so that instead
of pointing to their default value which uses the local system name they are assigned to the symbolic
hostname that was chosen for the APPS tier in the cluster.
Configuring EBS for SGeEBS 5