Using HP Global Workload Manager with SAP

33
Here’s an example of using one of the templates in a gWLM workload definition, to assign an Oracle
instance and listener to a particular workload. This would be in place of, or perhaps in addition to
“by user” and “by executable” rules for the workload.
Reporting
gWLM Historical and Advanced Reports
In the gWLM examples above, the discussion described setting up and monitoring in real time the
behavior immediately after configuration. However, after the workloads have been running for days,
weeks or months, gWLM’s historical reports to view allocation and consumption in the past will be
useful. Also, many administrators will find the gWLM advanced reports to be useful for:
• Confirming a workload had its owned resource available to it when needed (resource audit)
• Comparing and contrasting different workloads’ resources net borrowing and lending
(topborrowers)
• Triaging workload performance problems to understand if a workload slowdown is an application
or resource shortfall problem (abnormal util)
• Viewing SRD, workload, or other administrative changes (config)
• Exporting historical data to other tools (extract)
Capacity Advisor
All the use cases reviewed above are fully compatible with the use of Capacity Advisor, and you
could use standard Capacity Advisor practices to report on workloads’ utilization. In fact, with
Capacity Advisor’s Serviceguard integration, the Serviceguard failover use case will allow Capacity
Advisor to track the work of the package and stitch an uninterrupted utilization profile together no
matter which cluster node it ran on. While this is a built-in feature, it will make future planning
activities based on the package workload much more accurate than measurements at just the vpar
level. Similarly, because the correct batch or dialog processes are placed in separate workloads in
the last use case example, future Capacity Advisor planning will be able to more accurately plan
needed capacity for batch and/or dialog workload behavior.