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

For default configurations contents of the Application password

file are:

apps <- User Name

apps <- Password

SGeEBS Apps package looks for Application password

file in the $TKIT_DIR/apps directory

4. Enable and start the packages

# cmmodpkg -e -n <node1> -n <node2> ebsdbpkg

# cmmodpkg -e ebsdbpkg

Run cmviewcl command and make sure that ebsdbpkg has come up on one

node.

# cmmodpkg -e -n <node1> -n <node2> ebsappspkg

# cmmodpkg -e ebsappspkg

Run cmviewcl command and make sure that ebsappspkg has come up on

the

other node. You should be able to ping ebsapps.domain.com now.

If necessary, consult the manual "Managing HP Serviceguard" for

information

on managing packages.

I. Dependency between APPS and DB packages

There exists a complex dependency between the APPS and DB packages of

SGeEBS.

The DB package should know the name of the APPS package and vice

versa.

The proper sequence of starting the EBS packages is DB first and then

APPS.

If the APPS package is started first, it will check for the existence

of the

DB package in the running state and if it is not found, the APPS

package

startup will be aborted.

The proper sequence of bringing down the EBS packages is APPS Tier

first

and then the DB Tier. If DB package is brought down when the APPS

package

is up and running, the APPS package also will be brought down in the

shutdown

sequence of the DB package.

The failure scenarios of EBS packages are different from operator

initiated

start and stop operations. There is no issue in failing over the APPS

package when the DB package is running on any node of the cluster. If