Using HP Global Workload Manager with SAP

Now that we have the two scripts with correct permissions, let’s test them:

root@cutst125:/etc/opt/vse/scripts

/etc/opt/vse/scripts/batch.C03_DVEBMGS00

7956 7961

root@cutst125:/etc/opt/vse/scripts echo $?

root@cutst125:/etc/opt/vse/scripts grep BTC

/etc/cmcluster/C03/wlmprocmap.C03_DVEBMGS00_cutst125

BTC:7956

BTC:7961

and dialog:

root@cutst125:/etc/opt/vse/scripts

/etc/opt/vse/scripts//dialog.C03_DVEBMGS00

7926 7927 7928 7929 7930 7931

root@cutst125:/etc/opt/vse/scripts echo $?

root@cutst125:/etc/opt/vse/scripts grep DIA

/etc/cmcluster/C03/wlmprocmap.C03_DVEBMGS00_cutst125

DIA:7926

DIA:7927

DIA:7928

DIA:7929

DIA:7930

DIA:7931

We confirmed the lists match so now we define gWLM workloads that can consume this procmap

output.

Creating the SRD

For this SRD, we select our system cutst125 and create two new workloads for batch and dialog

processes. We’ll leave all other processes like Oracle instance processes in cutst125.OTHER.

We follow the normal steps to create the SRD by selecting our target system, cutst125, in the System

tab and then selecting Create->Shared Resource Domain. (Starting with gWLM 4.0, the System

tab is known as the Visualization tab.)