WLMTK Overview: Using HP-UX WLM Effectively With Your Most Critical Applications

To see how to fine-tune the resource allocation for your Oracle instances, download the preceding

example configuration files by clicking the Example configurations link on the HP-UX Workload

Manager website at http://www.hp.com/go/wlm.

HP-UX WLM Apache Toolkit

HP-UX WLM Apache Toolkit (ApacheTK) can help you manage and prioritize Apache-based

workloads. WLM can be used with Apache processes, Tomcat, CGI scripts, and related tools using

HP-UX Apache-based Web Server 2.x.

Why use ApacheTK?

Assume your enterprise (or corporate) applications use Apache as a front end to dispatch work to

workloads running Java software, CGI scripts, and other such processes. You can then use WLM and

ApacheTK to manage these processes in a manner that reflects the business priorities they support.

Tools in ApacheTK

ApacheTK includes a white paper and example configuration files that demonstrate resource

separation of Apache-based workloads. It also includes the simple data collector,

time_url_fetch, which uses the Apache benchmark tool, ab, to record URL response times.

Also, ApacheTK provides wlm_watch.cgi, which provides a web-based view of the standard

prmmonitor, prmlist, and other WLM and HP PRM command line tools. These are view-only

reports—no modifications are allowed from the CGI script.

How ApacheTK works

ApacheTK explores several scenarios using WLM with Apache-based workloads. These scenarios,

based on the WLM model of workload separation, are discussed in a white paper that includes

example configuration files and explains related tools.

How to use ApacheTK

The best way to use ApacheTK is to read the white paper, “Using HP-UX Workload Manager with

Apache,” available by clicking the Information library link at:

http://www.hp.com/go/wlm

This paper guides you through the tools and procedures used to configure WLM to:

• Separate Apache from Oracle database instances

• Separate Apache from batch work

• Isolate a resource-intensive CGI workload

• Separate all Apache Tomcat workloads from other Apache workloads

• Separate two departments’ applications using two Apache instances

• Separate module-based workloads with two Apache instances

• Manage Apache CPU allocation by performance goal