Using HP Global Workload Manager with SAP

Repeat for the other procmap:

root@cutst125:/tmp /etc/opt/vse/scripts/batch.C03_DVEBMGS00

7956 7961

root@cutst125:/tmp ps -fR c03.batch

UID PID PPID C STIME TTY TIME COMMAND

c03adm 7961 7919 0 20:45:47 ? 0:00 dw.sapC03_DVEBMGS00

pf=/usr/sap/C03/SYS/profile/C03_DVEBMGS00_cutst125

c03adm 7956 7919 0 20:45:47 ? 0:00 dw.sapC03_DVEBMGS00

pf=/usr/sap/C03/SYS/profile/C03_DVEBMGS00_cutst125

If, during normal SAP work, these lists change, SGeSAP will update the map file and the procmap will

run shortly afterwards, causing gWLM to move the process to the workload reflecting the new function

of the process.

Ideas for extending this use case

You might wish to separate just batch processes from the instance, leaving dialog processes in

cutst125.OTHER. Alternatively, you may wish to create named fss workload for more processes like

Oracle or other SAP instances.

Tips for using other VSE tools with SAP

Using Application Discovery with SAP for process placement and

monitoring

For simplicity, most of our gWLM examples above used gWLM’s “by user” process placement. The

exception, the special batch vs. dialog case, required the “by procmap” methods of separating and

placing processes into fss or pset workloads. However, there is another tool in the VSE suite that will

be useful for many administrators.

VSE 3.0.1 includes Application Discovery, which has additional capabilities to find, group, and place

processes for more complex cases. You can form a workload template to do regular expression

matching against the ps list to include or exclude particular processes in a workload. Optionally, you

can then have gWLM form a workload “by application” to take that group of processes and place

them in a new fss or pset workload.