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 3 157
IS680 Installation Step:
The REM_COMM value defines the method to be used to remotely execute
commands for Application Server handling. It can be set to ssh to provide
secure encrypted communications between untrusted hosts over an
insecure network.
Information on how to set up ssh for each node refer to Section Cluster
Node Configuration.
Default value is remsh.
Example:
REM_COMM=remsh
IS690 Installation Step:
Use the AS_PSTART variable to specify the startup procedure of the
configured Application Servers. The default value here is AS_PSTART=1
for parallel startup and AS_PSTART=0 for sequential startup. Be aware
that setting AS_PSTART=0 will slow down your total failover time.
Example:
AS_PSTART=1
OS700 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