HP Serviceguard Toolkit for Oracle E-Business Suite User Guide

applications tier services, that is, concurrent manager is run on the same server at the same time
as the Web and Forms components.
If an APPS tier server failure occurs, the concurrent processing subsystem undergoes a failover with
the rest of the application tier services to the alternative node and is automatically restarted on that
server. Through PCP functionality, concurrent managers are now restarted on the alternate server
and batch and asynchronous job processing can now continue.
EBS as Serviceguard package
SGeEBS requires EBS to be configured as two Serviceguard packages, a DB tier package and an
APPS tier package, The package configuration file declares the preferred nodes, disks/or volume
groups, and subnets that the package will use. When the package is up, a monitor script runs in
the background to check that the APPS tier-specific processes are still running. If the monitoring
script detects that a component is no longer up, it triggers Serviceguard to commence a package
failover to a different node. The monitoring script of the APPS package continuously loops through
each applications tier service and checks that they are still up. These services are the fulfillment
server, applications tier listener, HTTP server, concurrent processing server, forms server, and the
OACORE server. In worst case scenarios both packages can run on one node. This makes it
possible to deploy the SGeEBS product on a cluster having a minimum of 2 nodes. The package
runs the stop command when the stop or failover occurs.
Figure 1 (page 7) illustrates a basic two node SGeEBS configuration with hosting the Oracle EBS
APPS tier and sq-serv1 hosting the DB tier. Both nodes are accessing a shared storage disk
array.
Figure 1 A basic two node SGeEBS configuration
EBS as Serviceguard package 7