Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Cluster Configuration
Chapter 2 65
OS610 Optional Step:
If you want to use DB_RECONNECT with any instance of your SAP
component, you must disable the automatic restart of that component
(ASTREAT not set to ${RESTART_DURING_FAILOVER}).
This prevents the Instance from restarting in the event of a database or
central instance failover. This means that the Instance profiles must be
configured to use DB_RECONNECT. Remember that if you want to use
DB_RECONNECT with any application server you must also use it with
the Central Instance. A reconnection of the application server to the
switched database is only possible if the Central Instance has not been
restarted. See the appropriate OSS notes for the usage of
DBRECONNECT: OSS 109036, 98051, 24806 for more information.
OS630 Optional Step:
If your setup consists of application servers that are significantly slower
than the Central Instance host, it is possible that the Central Instance
shuts down before application server shutdown is completed. This can
lead to unsafe shutdowns and instance crash. To be safe, specify one of
the following:
WAIT_OWN_AS=1
The shutdown of all application servers takes place in parallel, but the
scripts do not continue before all of these shutdown processes have come
to an end.
WAIT_OWN_AS=2
if the package should also wait for all application servers to come up
successfully. You have to use this value if you want to prevent the
integration from temporarily opening a new process group for each
application server during startup.
WAIT_OWN_AS=0
This can significantly speed up the package start and stop. Use this
value only if you have tested and verified timing issues will not occur.
OS640 Optional Step:
Specify SAPOSCOL_STOP=1 if the SAP operating system collector
saposcol should be stopped together with each instance that is stopped.
SGeSAP/LX IPF makes sure that the collector only stops if there is no
instance of an SAP WAS system remains running on the host.