Using HP Global Workload Manager with SAP

4
Requirements for each example
The paper covers several different example use cases, from simple to more complex. The more
complex use cases have more tool requirements, as shown in the following table. Also included in the
table for your reference are the versions used on the test systems during the development of this
paper.
Use case demonstrated Required management components Versions demonstrated
Example 1: SAP instances or
systems in partitions
gWLM VSEMgmt 3.0.1 (includes gWLM 3.0.1)
Example 2: SAP separating one
instance vs. other work by user
gWLM VSEMgmt 3.0.1 (includes gWLM 3.0.1)
Example 3: Controlling SAP
resources during Serviceguard
failovers
gWLM, Serviceguard (SG),
Serviceguard Extensions for SAP
(SGeSAP)
VSEMgmt 3.0.1 (includes gWLM 3.0.1),
Serviceguard 11.18, SGeSAP 4.51
Example 4: SAP separating batch
and dialog processes
gWLM, WLMTK (wlmsapmap),
Serviceguard Extensions for SAP
(SGeSAP)
VSEMgmt 3.0.1 (includes gWLM 3.0.1),
WLMToolkits A.01.10.01, SGeSAP
4.51
We’ll now discuss each demonstration use case in detail, describing the goals, prerequisites, and
then walk through the set up of the use case on an example system. After showing the walk through,
we’ll suggest some additions or variations that might more closely match other customer situations.
Common Prerequisites
You need gWLM 3.0.1 or later, which is part of VSE Management Software (VSEMgmt). Also, you
need any prerequisites, such as HP Systems Insight Manager (SIM), properly installed and configured.
For all of these examples, it is assumed that you have:
• Completed the setup of VSEMgmt, including gWLM, according to the VSE Management Software
Installation and Update Guide
• Discovered the target systems that host SAP and deployed the required VSE agents to them
• Run vseassist against those new systems and corrected any errors or warnings it reported
All of the gWLM policies shown use CPU utilization (e.g. using two cores of an allocated four cores is
a 50% CPU utilization) as their measurement of workload CPU resource need or appetite. No extra
external metrics like response time, dialog steps, or queue depth are used, so there are no external
data collectors required.
Example 1: SAP instances or systems in partitions
The first example shows gWLM flexing virtual partitions (vpars), each with one or more SAP instances
in them. gWLM manages the vpar as a single workload, and the whole vpar’s CPU utilization is
considered when gWLM computes and applies the next intervals’ resource allocation. Because the
workload being flexed is the entire vpar OS instance, this example gives OS isolation to the SAP
instance within the vpar.
You can perform this example with nPartitions that share a hardware frame and unallocated ICAP
cores, or virtual machines within the same HP Integrity VM Host. In each case, the HP-UX OS instance
is the workload, and the gWLM policies are applied to these OS workloads just like in the vpar
example.