Example WLM configuration files

#
# Name:
#	isolate_sap.wlm
#
# Version information:
#	@(#) __HP_WLM_WHAT_ID_GOES_HERE__
#
#	(C) Copyright 2005 Hewlett-Packard Development Company, L.P.
#
#	$Revision: 1.2 $
#
# Caveats:
#	DO NOT MODIFY this file in its /opt/wlm/toolkits/sap/config location!
#	Make modifications to a copy and place that copy outside the
#	/opt/wlm/ directory, as items below /opt/wlm will be replaced
#	or modified by future HP-UX WLM product updates.
#
# Purpose:
#	This example demonstrates WLM’s ability to isolate an SAP workload
#	and allocate CPU resources based on the workload’s usage.  FSS
#	workload groups are used, but PSET groups could be used as well.
#
# Dependencies:
#	This example was designed to run with HP-UX WLM version A.02.00 or
#	later.
 
#
# Set the interval on which WLM takes CPU requests and makes changes in CPU
# allocations to 5 seconds. (The default interval is 60 seconds. Using a
# smaller interval allows WLM to respond more quickly to changes in
# workload performance.)
#
# Use absolute_cpu_units mode so that 100 shares equals 1 core of CPU 
# resources.
#
tune {
    wlm_interval = 5;
    absolute_cpu_units = 1;
}
 
#
# prm structure
#
#	Define groups for the various workloads.  Use an application record
#	to isolate the Apache workload and a user record to isolate the SAP
#	workload.  All httpd processes will be moved to the Apache group, and
#	all processes run as user p00adm will be moved to the SAP group.
#
prm {
    groups = OTHERS : 1,
	     Apache : 2,
	     SAP : 3;
 
    apps = Apache : /opt/hpws/apache/bin/httpd;
 
    users = p00adm : SAP;
}
 
#
# The following SLO requests resources on behalf of the Apache workload.
# This SLO requests a static entitlement of 100 shares.
#
slo s_apache {
	pri = 1;
	entity = PRM group Apache;
	cpushares = 100 total;
}
 
#
# The following SLO requests resources on behalf of the SAP workload.
# This SLO is usage-based, so more CPU resources will get allocated as
# the workload gets busier.
#
slo s_sap {
	pri = 1;
	entity = PRM group SAP;
	mincpu = 100;
	maxcpu = 300;
	goal = usage _CPU;
}

#
# Name:
#	split_inst.wlm
#
# Version information:
#	@(#) __HP_WLM_WHAT_ID_GOES_HERE__
#
#	(C) Copyright 2005 Hewlett-Packard Development Company, L.P.
#
#	$Revision: 1.3 $
#
# Caveats:
#	DO NOT MODIFY this file in its /opt/wlm/toolkits/sap/config location!
#	Make modifications to a copy and place that copy outside the
#	/opt/wlm/ directory, as items below /opt/wlm will be replaced
#	or modified by future HP-UX WLM product updates.
#
# Purpose:
#	This example demonstrates WLM’s ability to separate SAP instances
#	within the same SAP system and allocate CPU resources based on the
#	workload’s usage.  FSS workload groups are used, but PSET groups
#	could be used as well.  The process map (procmap) feature is used
#	to move the different SAP instance processes to the appropriate
#	workload groups.
#
# Dependencies:
#	This example was designed to run with HP-UX WLM version A.03.01 or
#	later.
 
#
# Set the interval on which WLM takes CPU requests and makes changes in CPU
# allocations to 5 seconds. (The default interval is 60 seconds. Using a
# smaller interval allows WLM to respond more quickly to changes in
# workload performance.)
#
# Use absolute_cpu_units mode so that 100 shares equals 1 core of CPU
# resources.
#
tune {
    wlm_interval = 5;
    absolute_cpu_units = 1;
}
 
#
# prm structure
#
#	Define groups for the various workloads.  Use process maps to map
#	the different SAP instance processes to the appropriate workload
#	groups.  When wlmsapmap uses just the map file argument, all the SAP
#	processes from that instance are moved to the corresponding
#	workload group.
#
prm {
    groups = OTHERS : 1,
	     SAP_D01 : 2,
	     SAP_D02 : 3;
 
    procmap =
	SAP_D01 : /opt/wlm/toolkits/sap/bin/wlmsapmap
			-f /etc/cmcluster/C11/wlmprocmap.C11_D01_node1,
 
	SAP_D02 : /opt/wlm/toolkits/sap/bin/wlmsapmap
			-f /etc/cmcluster/C11/wlmprocmap.C11_D02_node1;
}
 
#
# The following SLO requests resources on behalf of the SAP_D01 workload.
# This SLO is usage-based, so more CPU resources will get allocated as
# the workload gets busier.
#
slo s_SAP_D01 {
	pri = 1;
	entity = PRM group SAP_D01;
	mincpu = 100;
	maxcpu = 300;
	goal = usage _CPU;
}
 
#
# The following SLO requests resources on behalf of the SAP_D02 workload.
# This SLO is usage-based, so more CPU resources will get allocated as
# the workload gets busier.
#
slo s_SAP_D02 {
	pri = 1;
	entity = PRM group SAP_D02;
	mincpu = 100;
	maxcpu = 300;
	goal = usage _CPU;
}

#
# Name:
#	split_procs.wlm
#
# Version information:
#	@(#) __HP_WLM_WHAT_ID_GOES_HERE__
#
#	(C) Copyright 2005 Hewlett-Packard Development Company, L.P.
#
#	$Revision: 1.4 $
#
# Caveats:
#	DO NOT MODIFY this file in its /opt/wlm/toolkits/sap/config
#	location!  Make modifications to a copy and place that copy
#	outside the /opt/wlm/ directory, as items below /opt/wlm will
#	be replaced or modified by future HP-UX WLM product updates.
#
# Purpose:
#	This example demonstrates WLM’s ability to separate different types
#	of SAP processes into different workload groups.  The process map
#	(procmap) feature is used to move SAP batch and dialog processes
#	into different workload groups.
#
# Dependencies:
#	This example was designed to run with HP-UX WLM version A.03.01 or
#	later.
 
#
# Set the interval on which WLM takes CPU requests and makes changes in CPU
# allocations to 5 seconds. (The default interval is 60 seconds. Using a
# smaller interval allows WLM to respond more quickly to changes in
# workload performance.)
#
# Use absolute_cpu_units mode so that 100 shares equals 1 core of CPU
# resources.
#
tune {
    wlm_interval = 5;
    absolute_cpu_units = 1;
}
 
#
# prm structure
#
#	Define groups for the various workloads.  The procmap feature is
#	used in conjunction with the SAPTK process ID finder so that the
#	SAP batch processes are moved to the Batch group and the dialog
#	processes are moved to the Dialog group.
#
#	Note that when multiple process types are specified with the -t
#	option, quotes must be used around the argument; otherwise, the
#	comma separating the process types is interpreted as a procmap
#	record separator rather than a process type separator.  For example:
#
#	    procmap = BTC_UPD : opt/wlm/toolkits/sap/bin/wlmsapmap
#		-f /etc/cmcluster/C11/wlmprocmap.C11_D01_node1 -t “BTC,UPD”;
#
#	This would move all the batch (BTC) and update (UPD) processes
#	to the BTC_UPD workload group.
#
prm {
    groups = OTHERS : 1,
	     Batch : 2,
	     Dialog : 3;
 
    procmap =
	Batch : /opt/wlm/toolkits/sap/bin/wlmsapmap
		    -f /etc/cmcluster/C11/wlmprocmap.C11_D01_node1 -t BTC,
 
	Dialog : /opt/wlm/toolkits/sap/bin/wlmsapmap
		    -f /etc/cmcluster/C11/wlmprocmap.C11_D01_node1 -t DIA;
}
 
#
# The following SLO requests resources on behalf of the Batch workload.
# This SLO is usage-based, so more CPU resources will get allocated as the
# workload gets busier.
#
slo s_Batch {
	pri = 1;
	entity = PRM group Batch;
	mincpu = 100;
	maxcpu = 300;
	goal = usage _CPU;
}
 
#
# The following SLO requests resources on behalf of the Dialog workload.
# This SLO is usage-based, so more CPU resources will get allocated as the
# workload gets busier.
#
slo s_Dialog {
	pri = 1;
	entity = PRM group Dialog;
	mincpu = 100;
	maxcpu = 300;
	goal = usage _CPU;
}