HP-UX 11i September 2003 Release Notes

HP-UX 11i Version 1.0 Operating Environment Applications
HP-UX 11i Mission Critical Operating Environment (MCOE)
Chapter 6
129
HP-UX Workload Manager Toolkits
HP-UX Workload Manager Toolkits (WLMTK), product number T1302AA, consist of
utilities and examples that make it easier to deploy WLM for the management of specific
mission-critical software products. As described earlier (“HP-UX Workload Manager” on
page 127), HP-UX WLM provides goal-based workload management.
updated for June
2003
WLMTK A.01.04 includes the following new toolkit:
WebLogicTK WLM BEA WebLogic Server Toolkit (WebLogicTK) allows you to move
CPUs to or from WebLogic instances as needed to maintain acceptable
performance. By managing the instances' CPU resources, the instances
will tend to consume fewer net CPU resources over time. You can then
use the additional resources for other computing tasks.
new for June 2002 WLMTK A.01.03 consists of the following toolkits:
ApacheTK WLM Apache Toolkit (ApacheTK) facilitates the management and
prioritization of Apache-based workloads.
ApacheTK illustrates how to:
• Separate Apache from Oracle database instances
• Separate Apache from batch work
• Isolate a resource-intensive CGI workload
• Separate all Apache JServ workloads from other Apache workloads
• Separate all Apache Tomcat workloads from other Apache
workloads
• Separate high/low priority JServ workloads using two JServ JVMs
• Separate http from https (SSL) traffic using two Apache instances
• Separate module-based workloads with two Apache instances
• Manage Apache entitlement by performance goal
DMTK WLM Duration Management Toolkit (DMTK) allows users to specify a
desired duration for an application.
DMTK offers the ability to:
• Increase an application’s CPU resources if it may not complete in
time
• Decrease an application’s CPU resources if it is completing too
quickly
ODBTK WLM Oracle Database Toolkit (ODBTK) provides an easy mechanism
for feeding Oracle database metrics into HP-UX WLM.
ODBTK offers the ability to:
• Keeps response times for your transactions below a given level by
setting response-time SLOs
• Increases an instance’s available CPU when a particular user
connects to the instance