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

EXAMPLE: (Package IP xx.yy.zz.10)
xx.yy.zz.10 virtualhostname.domain.com virtualhostname
- Mapping Clients/Users To The Active Instance
E. Setting Up E-Business Suite
SGeEBS can be used on servers on which EBS is already installed.
The only constraint is that Oracle binaries, Oracle database and
application base directories should be hosted on shared volume
groups that can be activated on any node of the cluster. If you
are installing EBS for the first time, please refer the latest
version of Oracle document "Oracle® Applications Installation
Guide:Using Rapid Install Release 12.1(12.1.1)Part No.E12842-02".
During fresh EBS installations for the purpose of providing high
availability for it using SGeEBS, when you specify hostname
during database node configuration, you need to specify aliased
hostname instead of physical server name. This aliased hostname
will be assigned the floating IP of EBS DB Tier package and the
APPS Tier accesses the DB Tier using this hostname. This makes
it possible for the APPS Tier to access the DB Tier independent
of the node on which the DB Tier package is running. Communication
between APPS Tier and DB Tier takes place through JDBC connections.
When you deploy SGeEBS in an environment in which EBS is already
installed, and if a physical server name is given during database
node configuration, you need to create a new Database Tier in
which the hostname refers to an aliased hostname. This is possible
by cloning the Database Tier. The procedures to be followed for
cloning the Database Tier , are available in the Metalink article
[ID 406982.1] titled "Cloning Oracle Applications Release 12 with
Rapid Clone". When the cloning script asks for "Target System Hostname
(Virtual or normal)", enter the aliased hostname.
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 filesystem
by multiple APPS tier servers. The EBS APPS tier filesystem should
be housed 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 filesystem can be housed locally
in the respective servers or it can be installed in the shared
storage.
During the APPS tier startup process, the storage is automatically
relocated by Serviceguard to be accessible on the active APPS tier
server and is mounted at standard file system mount points ready for
EBS initialization to begin
For continental cluster environment, it is recommended that,
each APPS tier server house their instance specific information
locally
and APPS tier filesystem in the shared storage