Managing Serviceguard Extension for SAP Version B.05.10, September 2010

During the installation of a SAP Netweaver 2004s Web AS, the SAPIinst installer edits a file in
/usr/sap/sapservices and adds a line for each sapstartservice instance. During boot
time an init script is executed located in:
/sbin/init.d/sapinit
referenced by
/sbin/rc3.d/S<###>sapinit
The sapinit script reads the content in file /usr/sap/sapservices and starts a sapstartsrv
for each instance during OS boot time. This can lead to error output in the boot messages log file
as file systems for exclusive shared storage is not available at that time.
If the use of the SAP control framework is not required, then remove the reference link from the
sapinit script. Furthermore, any running sapstartsrv processes can be killed from the process
list. Example:
# rm /sbin/rc3.d/S<###>sapinit
# ps -ef | grep sapstartsrv# kill {PID of sapstartsrv }
To make use of the sapstartservice configure the SAPSTARTSRV_START and
SAPSTARTSRV_STOP values. The sapstartsrv daemon is started and stopped accordingly.
Example:
SAPSTARTSRV_START=1
SAPSTARTSRV_STOP=1
Optional Step: OS790
To enable the Workload Management (WLM) support of the dispatcher monitors
specify:WLM_PROCMAP=1
The following example WLM configuration file illustrates how to favor dialog to batch processing.
prm {
groups = OTHERS : 1,
Batch : 2,
Dialog : 3,
SAP_other: 4;
users = <sid>adm: SAP_other, ora<sid>: SAP_other;
#
# utilize the data provided by sapdisp.mon to identify batch and dialog
#
procmap = Batch : /opt/wlm/toolkits/sap/bin/wlmsapmap -f
/etc/cmcluster/<SID>/wlmprocmap.<SID>_<INSTNAME><INR>_<HOSTNAME> -t BTC,
Dialog :
/opt/wlm/toolkits/sap/bin/wlmsapmap -f /etc/cmcluster/P03/wlmprocmap.P03_DVEBMGS00_cutst144 -t DIA;}
#
# definition of Service Level Objectives
#
slo s_Dialog {
pri = 1;
entity = PRM group Dialog;
mincpu = 1;
maxcpu = 600;
goal = usage _CPU;
condition = metric sap_db_active;
}
slo s_Batch {
pri = 2;
entity = PRM group Batch;
mincpu = 1;
maxcpu = 600;
goal = usage _CPU;
condition = metric sap_db_active;
}
The following example WLM configuration file ties the CPU core shares guaranteed for dialog
processing to the number of dialog processes running as of the current SAP operation mode. In
times of high load, the overall dialog processing power of the instance is guaranteed to be at
least 25% of a core multiplied by the number of dialog work processes running.
#
# Uses absolute CPU units so that 100 shares == 1 CPU.
#
tune {
92 Step-by-Step Cluster Conversion