HP-UX Workload Manager overview

Note

WLM’s network interfaces are designed to operate correctly to defend

against attacks in a moderate to high threat environment, such as a

demilitarized zone (DMZ). (A DMZ is a computer or small subnetwork

located between a trusted internal network, such as a private corporate

LAN, and an untrusted external network, such as the public Internet.) You

may use network protections such as firewalls to provide an additional level

of defense and to give you additional time to react if a security loophole is

found.

Managing application performance: Quick start

You can quickly and easily set up WLM to manage application performance with shares-based SLOs

and usage goal-based SLOs. These SLOs do not require user-supplied metrics.

To set up either type of SLO:

1. Set up the application’s host as a workload or assign the application to a workload group.

2. Define an SLO for that workload:

a. Specify the priority of the SLO.

b. (Optional) Specify the minimum and maximum CPU requests for the SLO.

c. For a shares-based SLO, specify a shares-per-metric allocation (using a data collector included

with WLM) or a fixed-allocation request for the SLO.

For a usage-goal-based SLO, specify the usage goal (using the default range of percentages or

specifying a range. WLM adjusts the workload’s allocation, giving it more CPU resources when

utilization falls below the minimum percentage and fewer CPU resources when it rises above

the maximum).

Managing application performance with metric goals:

Advanced HP-UX Workload Manager management

Using metric goals, you can fine-tune how workloads are managed. For each SLO with a metric goal,

WLM collects metrics from either built-in or user-supplied data collectors. Use metric goals only if

performance data is available and understood. Otherwise, use usage goals.

With metric-goal-based SLOs, you must:

1. Set up the application’s host as a workload or assign the application to a workload group.

2. Define an SLO for that workload:

a. Specify the priority of the SLO.

b. (Optional) Specify the minimum and maximum CPU requests for the SLO.

c. Specify the metric goal.

3. Specify the data collector that will provide the metric.