HP-UX Workload Manager overview

Using HP-UX Workload Manager with HP Systems Insight

Manager and HP Servicecontrol Manager

HP Systems Insight Manager and one of its predecessors, HP Servicecontrol Manager, provide a

single point of administration for multiple HP-UX systems. The WLM integration with HP Systems

Insight Manager and HP Servicecontrol Manager enables you to perform the following activities from

the Central Management Server (CMS) on nodes in the cluster that have WLM installed:

• Enable HP-UX WLM

• Disable HP-UX WLM

• Start HP-UX WLM

• Stop HP-UX WLM

• Reconfigure HP-UX WLM

• Distribute HP-UX WLM configuration files to the selected nodes

• Retrieve currently active HP-UX WLM configuration files from the nodes

• Verify the syntax of HP-UX WLM configuration files on either the CMS or the selected nodes

• View, rotate, and truncate HP-UX WLM log files

Using HP-UX Workload Manager with Oracle databases

HP-UX WLM Oracle Database Toolkit (ODBTK) simplifies getting metrics on Oracle database

instances into WLM, which enables you to better manage Oracle instances. ODBTK is part of the

WLM Toolkits product, which is included with WLM. Benefits of ODBTK include the ability to:

• Keep response times for your transactions below a given level by setting response-time SLOs

• Increase an instance’s available CPU resources when a particular user connects to the instance

• Increase an instance’s available CPU resources when more than n users are connected

• Increase an instance’s available CPU resources when a particular job is active

• Give an instance n CPU shares for each process in the instance

• Give an instance n CPU shares for each user connection to the instance

Using HP-UX Workload Manager with Apache

WLM can help you manage and prioritize Apache-based workloads through the use of the HP-UX

WLM Apache Toolkit (ApacheTK). ApacheTK, a component of the WLM Toolkits product that comes

with WLM, enables you to:

• Separate Apache from Oracle database instances

• Separate Apache from batch work

• Isolate a resource-intensive common gateway interface (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 allocations by performance goal

For more information, see the white paper, “Using HP-UX Workload Manager with Apache-based

Applications,” which offers various use cases. This paper is installed on systems with WLM at