Managing Serviceguard Extension for SAP Version B.05.10, December 2012

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. Step IS1110 will describe how to achieve that.
Installation Step: LS680
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
Installation Step: LS690
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
Optional Step: OS700
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
Can significantly speed up the package start and stop, especially if Windows NT application
servers are used. Use this value only if you have carefully tested and verified that timing issues will
not occur.
Optional Step: OS710
Specify SAPOSCOL_STOP=1 if saposcol should be stopped together with each instance that is
stopped .
The collector will only be stopped if there is no instance of an SAP system running on the host.
Specify SAPOSCOL_START=1 to start the saposcol even with packages that don't use the implicit
startup mechanism that comes with SAP instance startup, e.g. database-only packages or packages
that only have a SCS, ASCS, or ERS instance.
Legacy Package Configuration 99