HP-UX 11i September 2002 Release Notes

HP-UX 11i Version 1.0 Operating Environment Applications
HP-UX 11i Mission Critical Operating Environment (MCOE)
Chapter 6
113
Installation Requirements
updated for
June 2002
HP-UX WLM requires 11MB of disk space (91 if PRM is not already installed) and 5MB
of memory.
Prior to June 2002, HP-UX WLM requires 9MB of disk space (89 if PRM is not already
installed) and 5MB of memory.
Compatibility Issues
HP-UX WLM can be used with any 11.x version of GlancePlus for monitoring. However,
if you are going to use a WLM glance_* data collector (for example, glance_app or
glance_tt), use GlancePlus version C.03.35.00 or later. Do not use GlancePlus for
changing PRM entitlements.
If you have iCOD or Pay Per Use (PPU) software installed, do not use WLM’s vPar
(virtual partitions) management. Using WLM’s vPar management in such an
environment may cause an iCOD processor to be automatically enabled without
customer authorization. If this situation occurs, please contact your HP representative.
Documentation
Documentation includes:
• The HP-UX Workload Manager User’s Guide and the HP-UX Workload Manager
A.02.00 Release Notes for HP-UX 11.0 and HP-UX 11i available on the HP-UX 11i
Instant Information CD and on the Web at http://docs.hp.com/.
• Manpages:
— wlm (5)
For more information on HP-UX Workload Manager, see http://www.hp.com/go/wlm.
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 112), HP-UX WLM provides goal-based workload management.
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