Using HP Global Workload Manager with SAP

9
That completes the first use case example. The vpars containing the SAP instances are now under
gWLM control and the Owns_4-Max_8 policies are in effect.
Ideas for extending this use case
You may wish to configure gWLM events to notify you of resource shortfalls and pass those along to
Openview. For information on generating events, select in the VSE menu bar Tools->Global
Workload Manager->Events. For information on handling and communicating events to other
systems, select in the HP SIM menu bar Options->Events.
If the split of four cores each is not what you desire, select in the VSE menu bar Policies->Create
New Policy, and create a new pair of policies with different owned values, like 5 and 3. Make sure
the owned values’ sum is equal to (or less than) the SRD size; otherwise, gWLM will not allow you to
deploy it.
Example 2: SAP separating instance vs. other work by user
In this example, we separate a single system running two types of work, an SAP instance and another
application, into two separate groups based on the UNIX user ID by which they are run.
Prerequisites
All of the steps in this example use features included in VSEMgmt and gWLM, so there are no other
prerequisites to install.
Because we will be separating running processes into separate workloads within a single OS image,
you may wish to familiarize yourself with a /usr/bin/ps -ef listing on your target system so you
are aware of the UNIX user uid and executable names of your SAP instance processes.
Walkthrough
For this example, our target system cutst128 is running an SAP instance, C03, and some other
processes as well. The SAP instance C03 is run by UNIX user c03adm. We wish to isolate that
instance’s resources from other work going on but allow it to borrow other resources if need be. We
will leave the other jobs running in the default gWLM OTHER workload, and give it some reserved
resources too.