Understanding the HP Serviceguard Extension for Oracle E-Business Suite (SGeEBS)

Adding EBS packages into the cluster

After the EBS packages are configured, you must verify the configuration. If the configurations are

verified without errors, add them to the cluster. Examples of commands are:

1. Verify the configuration parameters

# cmcheckconf -P ebsdbpkg.conf

# cmcheckconf -P ebsappspkg.conf

2. Apply the packages to the cluster

# cmapplyconf -P ebsdbpkg.conf

# cmapplyconf -P ebsappspkg.conf

3. Copy the APPS password file to $TKIT_DIR/apps directory. For default configurations contents of

the Application password file are:

apps <- User Name

apps <- Password

SGeEBS Apps package looks for APPS password file in the $TKIT_DIR/apps directory

4. Enable and start the packages

# cmmodpkg -e -n <node 1> -n <node2> ebsdbpkg #

cmmodpkg -e ebsdbpkg

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

# cmmodpkg -e -n <node 1> -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.

SGeEBS with Serviceguard Continentalclusters

HP Serviceguard Continentalclusters consists of two clusters existing at different geographic locations.

Each of these clusters provides high availability for applications at the local level at that particular

site. For optimal performance and to assure adequate capacity on the recovery cluster, it is best to

have similar hardware in both clusters.

Normally, an application (package) can run on only one node at a time in a cluster. However, in

Continentalclusters, there are two clusters on which the primary package and the recovery package

will be deployed. Both the primary and the recovery package must not be allowed to run at the same

time. To prevent this, it is important to ensure that SGeEBS packages are not allowed to start

automatically and are not started at inappropriate times. To keep packages from starting up

automatically, when a cluster starts, set the AUTO_RUN parameter for all primary and recovery

packages to NO. Then use the cmmodpkg command with the -e <packagename> option to start up

only the primary packages and enable switching.