Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Serviceguard Extension for SAP on Linux Configuration – sap.config
Chapter 3156
Example 2:
The failover node is running a Central Consolidation System QAS. It
shall be stopped in case of a failover to this node.
ASSID[0]=QAS; ASHOST[0]=node2; ASNAME[0]=DVEBMGS;
ASNR[0]=10; ASTREAT[0]=8; ASPLATFORM[0]="HP-UX"
The failover node is running the Central Instance of Consolidation
System QAS. There are two additional Application Servers configured for
QAS, one inside of the cluster and one outside of the cluster. The
complete QAS shall be stopped in case of a failover. In this case,
${STOP_DEPENDENT_INSTANCES} is specified for the Central Instance of
QAS.
ASSID[0]=QAS; ASHOST[0]=node2; ASNAME[0]=DVEBMGS;
ASNR[0]=10; ASTREAT[0]=24; ASPLATFORM[0]="HP-UX"
ASSID[1]=QAS; ASHOST[1]=node3; ASNAME[1]=D; ASNR[1]=11;
ASTREAT[1]=8; ASPLATFORM[1]="HP-UX"
ASSID[2]=QAS; ASHOST[2]=extern1; ASNAME[2]=D; ASNR[2]=12;
ASTREAT[2]=8; ASPLATFORM[2]="HP-UX"
The Central Instance is treated the same way as any of the additional
packaged or unpackaged instances. Use the ASTREAT[*]-array to
configure the treatment of a Central Instance. For Example, if a Central
Instance should be restarted as soon as a DB-package fails over specify
the following in sapdb<SID>.config:
ASSID[0]=SG1; ASHOST[0]=node2; ASNAME[0]=DVEBMGS;
ASNR[0]=00; ASTREAT[0]=${RESTART_DURING_FAILOVER};
ASPLATFORM[0]="SG-PACKAGE"; ASPKGNAME="ciSG1"
If you don’t restart the SAP Instances during database failover, make
sure to turn on the DB-RECONNECT feature within their profile.
NOTE It is not possible to configure a JAVA-only instance in the AS*array as a
dependent component.