HP WebQoS Administrator's Guide
HP WebQoS Administration Guide
Edition 4
E0801
U.S.A.
© Copyright 2001, Hewlett-Packard Company.
Legal Notices
The information in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited
to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall
not be held liable for errors contained herein or direct, indirect, special, incidental or consequential
damages in connection with the furnishing, performance, or use of this material.
Warranty. A copy of the specific warranty terms applicable to your Hewlett- Packard product and
replacement parts can be obtained from your local Sales and Service Office.
Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013.
HEWLETT-PACKARD COMPANY
3000 Hanover Street
Palo Alto, California 94304 U.S.A.
Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR
52.227-19(c)(1,2).
Copyright Notices. ©copyright 1999-01 Hewlett-Packard Company.
©copyright 1979, 1980, 1983, 1985-93 Regents of the University of California
This software is based in part on the Fourth Berkeley Software Distribution under license from the
Regents of the University of California.
©copyright 1980, 1984, 1986 Novell, Inc.
©copyright 1986-1992 Sun Microsystems, Inc.
©copyright 1985-86, 1988 Massachusetts Institute of Technology.
©copyright 1989-93 The Open Software Foundation, Inc.
©copyright 1986 Digital Equipment Corporation.
©copyright 1990 Motorola, Inc.
©copyright 1990, 1991, 1992 Cornell University
©copyright 1989-1991 The University of Maryland
©copyright 1988 Carnegie Mellon University
Trademark Notices.UNIX® is a registered trademark of the Open Group.
X Window System is a trademark of the Massachusetts Institute of
Technology.
OSF/Motif is a trademark of the Open Software Foundation in the U.S. and other countries.
Java™ is a U.S. trademark of Sun Microsystems, Inc.
MS-DOS®, Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft
Corporation.
2
1. Understanding HP WebQoS
The Role and Benefits of HP WebQoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
WebQoS Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Request Classifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Capacity Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
SLOs, Thresholds, and Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
How WebQoS Fits Into Your Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
WebQoS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2. Setup
WebQoS Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
WebQoS Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
qos.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SCA and Web Server Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Web Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SCA Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
SCO Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Logging and Tracing Parameters (UNIX Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
URL Encoding Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Restarting Individual WebQoS Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Restarting WebQoS Components (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Restarting WebQoS Components (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
WebQoS setup Script (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Single Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Multiple Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Server 1 Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Servers 2 and 4 Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Server 3 Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Removing WebQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Contents
3. The Management Console
Management Console Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Console Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Auto Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
The Services/Systems View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Console Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3
Contents
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Domain Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4. Templates
Preconfigured and Default Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Preconfigured Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Default Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Service Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Service Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
URL Group Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
SLOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Add/Edit SLOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Defer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Redirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Site Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Classification Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Add/Edit Classification Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
SLOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Add/Edit SLOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Threshold Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Add/Edit Threshold Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Session Timeouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Web Server Accept Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Corrective Action Policy Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Site Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5. Services, Sites, and Systems
Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Add a Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Edit a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4
Contents
Move a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Delete a Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Add a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Edit a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Move a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Delete a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Microsoft IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Starting and Stopping IIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
iPlanet Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Add a System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Delete a System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6. Statistics
Service Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Service SLO Related Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Service Session Control Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Service Defer Related Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Site Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Site SLO Related Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Site Session Control Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7. Logs and Filters
SLOs, Thresholds, and the History Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
The Service Level Objectives View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
The History Log View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
SLO and Threshold Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
History Log Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
OpenView Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Service and Site Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Site Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Policy and Corrective Action Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8. Troubleshooting
Troubleshooting on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Shared Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Management Console Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5
Contents
Error Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Measurement Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Statistics Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Changing Logging and Tracing Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Troubleshooting on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Problems with Shared Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Resetting the Management Console Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Error Messages Viewable From the Management Console . . . . . . . . . . . . . . . . . . . 115
Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Changing Logging and Tracing Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Deleting WebQoS Log and Trace Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
A. Policy and Rule Descriptions
Request Classification Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Policies Set in WebQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Service Level Objectives for Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Service Level Objectives for the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Threshold Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Corrective Actions for SLO and Threshold Policy Violations. . . . . . . . . . . . . . . . . . 124
Customizing the Defer and Reject Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
B. External Measurement API
Using the External Measurement API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
wqCreateConnection() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Synopsis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Return Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
wqSendMeasurement() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Synopsis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Return Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
wqCloseConnection() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
6
Contents
Synopsis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Return Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Sample Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7
Contents
8
Printing History
The manual printing date and part number indicate its current edition.
The printing date will change when a new edition is printed. Minor
changes may be made at reprint without changing the printing date. The
manual part number will change when extensive changes are made.
Manual updates may be issued between editions to correct errors or
document product changes. To ensure that you receive the updated or
new editions, you should subscribe to the appropriate product support
service. See your HP sales representative for details.
First Edition: August 2001
9
10
1 Understanding HP WebQoS
This chapter explains the roles and benefits of HP WebQoS and how it
fits into your environment. It also describes fundamental WebQoS
concepts to help you understand how WebQoS technology works.
Chapter 1 11
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
The Role and Benefits of HP WebQoS
HP WebQoS is an enhancement to your operating environment that
stabilizes, optimizes, and prioritizes Internet-related applications and
transactions that run on Windows 2000 and NT servers (Windows) and
SPARC1 servers (Solaris1 operating environment). HP WebQoS works
with web-enabled applications built on top of the iPlanet Web Server
version 4.1 (UNIX®) and Microsoft® IIS2 (Internet Information Server)
version 4.0 (Windows NT) and version 5.0 (Windows 2000).
HP WebQoS enables you to use your resources efficiently to deliver
predictable and differentiated service levels for your web-based
applications, based on the type of customer or transaction. It allows you
to determine these service levels based on business policies.
Although the Internet represents significant opportunities for expanding
your business, the following risks may hamper your ability to deliver
web-based services to customers and partners reliably:
• Unpredictable and possibly fluctuating demand for services.
1
Because the Internet offers instantaneous access to your site,
promotional, seasonal, or current events may instigate sudden and
immediate interest in your services. Although the additional interest
and business may be welcome, your server may not be able to handle
the load if significant numbers of clients come all at one time. Or if
you are a service provider hosting multiple sites on one server, you
should make sure that the demands of one site do not restrict use by
other sites on the same server.
• Heavier than expected system processing per user request.
The actual workloads exhibited by each visitor to your site may not
align with the workload models you generated during the capacity
planning stage. Perhaps users are performing far more searches than
you anticipated or are spending a lot more time performing compute
intensive operations while at your site.
1. SPARC, Solaris, and the iPlanet Web Server are products of Sun
Microsystems, Inc.
2. Microsoft IIS is a product of Microsoft Corporation.
Chapter 112
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
• All requests are treated the same.
During overload conditions, all user requests and all transactions are
impacted. Even your most important customers who are trying to
access their accounts to make purchases, or sales representatives who
are trying to make a sale at the end of the month, are at the mercy of
Web surfers.
Each of the above conditions can cause increased load at your site or may
impede your ability to deliver your services at optimum levels.
By configuring WebQoS based on the type of services offered and traffic
experienced at your site, you ensure that important web-based
transactions are handled optimally in order to maximize revenue and
customer satisfaction.
Key capabilities and benefits of WebQoS allow you to do the following:
• Stabilize the system during server overload situations.
When the server is at capacity, WebQoS works to alleviate the load
and improve the performance. For more information, refer to
“Capacity Protection” on page 15.
• Prioritize client requests to the server system.
WebQoS allows you to provide differentiating service to different
types of client requests by prioritizing requests submitted to the site.
For more information, refer to “Request Classifications” on page 14.
• Establish rules for the classification of service requests from users.
WebQoS fulfills high priority service requests with optimum
performance while lower priority service requests are handled in
accordance with your instructions. For more information, refer to
“Request Classifications” on page 14.
Chapter 1 13
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
WebQoS Concepts
This section describes fundamental WebQoS concepts and capabilities.
Understanding these concepts is necessary before you can understand
how WebQoS technology works.
Service
A service refers to something of value that a business is offering to other
businesses or consumers. For example, a business may provide email,
messaging, documentation publishing, cataloging, and Electronic
Commerce services. A WebQoS service is a way to logically group web
sites related to a business application that you offer to customers or
partners.
Request Classifications
Request classifications determine access priority for requests submitted
to a web site. They enable you to give preferential treatment to your
most important customers or transactions, allowing you to meet formal
or informal service level agreements.
WebQoS request classifications differentiate requests as they enter the
server system by dividing requests into categories based on application,
client or destination IP addresses, destination port number, and URL
document paths. These request classifications can be assigned different
priority levels.
WebQoS supports three request classification priority levels: high,
medium, and low. During periods of heavy system load high priority
requests can be given preferred access to the server and low priority
requests can be redirected or rejected. If a request is accepted, it is
scheduled based on its request classification priority. Based on your
configured policies, the request might be immediately processed, or it
may wait while higher priority requests are processed first.
Sessions
A session is composed of one or more requests to a web site from the
same user. These requests may arrive over one, or over several
connections. Once a session has been granted access to a web site, a
user's remaining requests are guaranteed to be forwarded to the web
server, unless the session times out.
Under periods of heavy system load, new sessions may not be granted.
Chapter 114
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
This is controlled by the WebQoS policies. When new sessions are
rejected, redirected, or deferred, existing sessions continue
uninterrupted. User request prioritization and session management are
the primary tools used by WebQoS to provide capacity protection. The
network manager is responsible for updating the timers that define a
session, and for establishing the policies that control if the session is
admitted.
Capacity Protection
Capacity Protection prevents system overload with prioritization and
admission control. This minimizes the impact of unexpected surges in
demand while maximizing the volume of completed transactions.
Capacity Protection makes sure that performance levels for active
customers and their currently running transactions are not
compromised. New user requests are not admitted to a site unless their
transactions can be completed quickly.
Capacity is assessed by service level objectives and thresholds.
Protection is provided by corrective actions.
SLOs, Thresholds, and Corrective Actions
To ensure that your business policies are reflected in your Web
applications, they need to be translated into service level objectives
(SLOs) and thresholds. SLOs are business-oriented policies and
thresholds are operations-oriented policies. When an SLO or threshold is
violated, a configured corrective action is performed.
SLOs WebQoS has the following types of business-oriented SLOs:
• Capacity - Maximum number of concurrent sessions supportable with
acceptable performance. Typically coupled with a response time SLO
or performance threshold.
• Response times - A key component of customer satisfaction.
Measured from the time a request enters the server to the time a
response is sent back.
• External measurement - Measurements collected from external
sources can be used to determine corrective actions.
Thresholds WebQoS uses an operations-oriented load threshold to
keep your system operating properly during times of peak load. System
load is assessed as a function of CPU (central processing unit) usage.
Chapter 1 15
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
Corrective Actions Corrective actions help bring the violated SLO or
threshold into compliance. You configure and prioritize corrective
actions, which are executed when a violation occurs.
There are three types of corrective actions:
• Redirect requests to another system.
• Defer requests for a few moments until current sessions are
completed.
• Reject low priority customers in extreme overload conditions.
Chapter 116
How WebQoS Fits Into Your Environment
WebQoS works with your web server and application servers for all of
your web-enabled applications. Refer to Figure 1-1, "WebQoS in Your
Environment".
Figure 1-1 WebQoS in Your Environment
To ensure acceptable web-based interactions between you and your
customers, all parts of your web environment (client, network, web
server, and application server which includes an application) must work
together efficiently and effectively. The network alone cannot deliver
acceptable service levels if the server is creating delays due to excessive
demand or component failures. The server alone cannot deliver
acceptable service levels if the network is exhibiting bottlenecks.
Understanding HP WebQoS
How WebQoS Fits Into Your Environment
The following describes briefly the function of each part of the
environment:
• The client identifies itself and initiates requests.
• The network distinguishes class priorities and routes priority packets
efficiently while delivering best effort service to lower priority
packets.
• The web server distinguishes WebQoSrequest priorities and resource
management policies to ensure high priority service requests are
processed quickly.
• The application server contains an application with the processing
rules that enables service requests to be classified and handled by the
server and network.
Chapter 1 17
Understanding HP WebQoS
How WebQoS Fits Into Your Environment
WebQoS Components
WebQoS comprises a number of components that perform priority-based
resource management and service request handling (see Table 1-2,
WebQoS Components). In addition, management components allow you
to configure WebQoS for the systems on which it is installed as well as
define the SLOs and threshold policies that are important to your
business.
Note that not all components are required on every WebQoS-enabled
system but at least one of each component must exist in a WebQoS
domain. Refer to the HP WebQoS release note for more detailed
information.
Figure 1-2 WebQoS Components
Chapter 118
How WebQoS Fits Into Your Environment
Component Installed On Description
Understanding HP WebQoS
Management
Console
Database
SCA (Service
Control Agent) or
Web Services
SCI (Service
ControlInterface)
or
Communications
SCO (Service
ControlOperator)
or Management
Server
Any Windows
NT/95/98/00 system.
Can be installed on
Allows you to define performance objectives
for the components of the service and to
monitor performance levels and SLOs.
multiple PCs.
Any system*.
Stores configuration and event information,
statistics, and component status. Resides on
only one system in your WebQoS domain.
Anysystem*running
a web server that is
managed by
WebQoS.
Any system*.
Monitors site level SLOs, classifies user
requests, collects performance information,
and performs corrective actions. Resides on
at least one system in your WebQoS domain.
Receives configuration information from the
management console and API and monitors
the SCO and SCA(s). Resides on at least one
system in your WebQoS domain.
Any system*.
Monitors service level SLOs. Resides on
only one system in your WebQoS domain.
*
If you are running WebQoS on Windows 2000 or NT 4.0, any system is
any Windows 2000 or NT 4.0 server or any Advanced Server system.
If you are running WebQoS on the Solaris operating environment, any
system is any SPARC server running Solaris 8.
Chapter 1 19
Understanding HP WebQoS
How WebQoS Fits Into Your Environment
Chapter 120
2 Setup
This chapter covers the initial steps you must complete before
configuring policies and rules using WebQoS. Complete the following
steps:
Chapter 2 21
Setup
WebQoS Software Installation
1. Install the WebQoS software.
2. Modify the WebQoS configuration files.
3. Run the WebQoS setup script and start your web server(s) (UNIX).
WebQoS Software Installation
Information about installing, upgrading, and removing WebQoS and its
management console can be found in the HP WebQoS release note.
On a Windows system, the Microsoft IIS software should be installed,
configured, and running on the web server system before WebQoS is
installed.
See “Microsoft IIS” on page 81 for more information about using
Microsoft IIS with WebQoS.
NOTE In this manual, the location where the WebQoS program files are
installed for Windows is referred to as
default installation directory is
C:\Program Files\Hewlett-Packard\HPWebQoS.
<install-directory>
. The
WebQoS Configuration Files
The following configuration file can be modified before starting WebQoS:
• qos.conf - WebQoS global configuration file.
Chapter 222
Setup
WebQoS Configuration Files
qos.conf
qos.conf is the WebQoS global configuration file. In UNIX, this file is
located in the /etc/opt/webqos directory. In Windows, this file is
located in
On a UNIX system, configure qos.conf before running the WebQoS
setup script. If you update qos.conf after running the setup script,
individual components (for example, the web server, SCA, SCI, and/or
SCO) must be restarted for any changes to take effect (see “Restarting
WebQoS Components (UNIX)” on page 30).
On a Windows system, if you update qos.conf, individual components
(for example, the web server, SCA, SCI, and/or SCO) must be restarted
for any changes to take effect (see “Restarting WebQoS Components
(Windows)” on page 30).
The following parameters can be set:
SCA and Web Server Parameter
The following parameter affects the SCA and web server. If you change
this parameter, you must restart the SCA and web server.
<install-directory>
.
• MeasurementInterval (seconds)
Default: 30
Range: 5 - 43200 (12 hours)
How often, in seconds, WebQoS collects performance measurements.
The MeasurementInterval must be an even multiple of the
MonitorInterval.
If Site Statistics Logging is enabled from the management console,
this parameter also specifies the interval at which the SCA generates
site statistics.
Web Server Parameters
The following parameters affect the web server. If you change any of
these parameters, you must restart the web server.
• EXCLUDE_FILE_EXTNS
Default: gif jpeg jpg
Range: Up to 10 extensions can be specified. Each extension can be up
to 10 characters.
Chapter 2 23
Setup
WebQoS Configuration Files
Extensions of file types that are typically embedded in a requested
page and should not be considered new sessions. Any policies or rules
should not be applied to them. For example, gif, jpeg, and jpg are
graphic files that are typically embedded in a requested page. A
separate request is generated for each of these files but these requests
should not be considered new sessions. Also, any policies and/or rules
configured are applied only to the requested page, not to these
embedded files.
• HTTPVersion
Default: HTTP/1.1
• KeepDeferringAfterMaxDeferTime
Default: TRUE
Range: TRUE or FALSE
Based on the calculated defer time and the maximum defer time
configured in the Defer Corrective Actions screen (default
maximum defer time is 120 seconds). If the calculated defer time is
greater than the maximum defer time and this parameter is set to
TRUE, new sessions are deferred. If the parameter is set to FALSE,
new sessions are re-evaluated (in accordance with the configured
corrective actions).
• MonitorCPUWeight (%)
Default: 20
Range: 1 - 100
Percentageof the current CPU utilization (pstat is used to determine
current CPU utilization) used to calculate the weighted CPU
utilization. The weighted CPU utilization is based on the current and
previous (last measured) CPU utilization:
weighted CPU% = (MonitorCPUWeight% * current CPU) +
[(100 - MonitorCPUWeight)% * previous CPU]
For example, if you set the MonitorCPUWeight to 20, the current
CPU utilization is 60, and the previous CPU utilization is 50, the
weighted CPU utilization is (20% * 60) + [(100 - 20)% * 50] or 52%.
If you want to monitor the current CPU utilization only, set this
parameter to 100.
The MonitorInterval parameter determines how often the weighted
CPU utilization is calculated (default is every 5 seconds).
Chapter 224
WebQoS Configuration Files
• MonitorInterval (seconds)
Default: 5
Range: 1 - 43200 (12 hours)
How often, in seconds, threshold policies are monitored.
• MonitorResponseTimeWeight (%)
Default: 50
Range: 1 - 100
Percentage of the current response time used to calculate the
weighted response time. The weighted response time is based on the
current and previous (last measured) response time:
weighted response = (MonitorResponseTimeWeight% * current
response time) + [(100 - MonitorResponseTimeWeight)% * previous
response time]
For example, if you set the MonitorResponseTimeWeight to 20, the
current response time is 3 seconds, and the previous response time is
2 seconds, the weighted response time is (20% * 3) + [(100 - 20)% * 2]
or 2.2 seconds.
Setup
If you want to monitor the current response time only, set this
parameter to 100.
The MonitorInterval parameter determines how often the weighted
response time is calculated (default is every 5 seconds).
• NumOfDeferredSessionsPerSecond
Default: 1
The number of deferred sessions that have the same deferral time
allocated to them. The default minimum deferral time is 10 seconds
and the default maximum deferral time is 120 seconds.
For example, if you set this parameter to 1 and three requests arrive
at the same time, the first deferred session is allocated a deferral time
of 10 seconds, the second deferred session is allocated a deferral time
of 11 seconds, and the third deferred session is allocated a deferral
time of 12 seconds. If you set the parameter to 2 and three requests
arrive at the same time, the first and second deferred sessions are
allocated a deferral time of 10 seconds and the third deferred session
is allocated a deferral time of 11 seconds.
The default minimum and maximum deferral times (also called wait
Chapter 2 25
Setup
WebQoS Configuration Files
times) can be configured for a template by selecting the Advanced tab
and then Corrective Actions Policy Details.
SCA Parameters
The following parameters affect the SCA only. If you change any of these
parameters, you must restart the SCA.
These parameters impact measurement log files. In UNIX, the
measurement log files are located in the /var/opt/webqos/measures
directory. In Windows, these files are located in the
<install-directory>
• LogInterval (minutes)
Default: 30
Range: >=1
How often, in minutes, WebQoS logs measurements to a log file. The
LogOn parameter must be enabled (set to 1) before WebQoS logs
measurements to the log file.
• LogOn
\measures directory.
Default: 0 (disabled)
Range: 0 (disabled) or 1 (enabled)
Enable or disable measurement logging. To enable measurement
logging, set this parameter to 1. To disable measurement logging, set
this parameter to 0.
WebQoS creates a new measurement log file daily for each WebQoS
site. The measurement log file name is the site name you entered in
the management console followed by the date. The log file contains
performance measurements collected during the day for the site
including:
— Average response time for each request class
— Number of new, redirected, deferred, and rejected sessions for each
request class
• SaveFiles
Default: 0 (disabled)
Range: 0 (disabled) or 1 (enabled)
Enable or disable saving measurement log files. If enabled, all
measurement log files are saved. If disabled, measurement log files
Chapter 226
Setup
WebQoS Configuration Files
more than two days old are deleted.
SCO Parameters
The following parameters affect the SCO only. If you change any of these
parameters, you must restart the SCO.
• HistoryEventDays (days)
Default: 7
Range: 1 - 365
How many days of history events to save. At midnight, history events
older than the specified age are deleted.
• SCOLogExternMeas
Default: 0 (disabled)
Range: 0 (disabled) or 1 (enabled)
Enable or disable external measurement logging.
The SCOLogInterval parameter determines how often the SCO
writes external measurement data to a log file.
In UNIX, the external measurement log files are located in the
/var/opt/webqos/stats directory. In Windows, these files are
located in the
• SCOLogInterval (minutes)
Default: 5
Range: 1 - 1440 (24 hours)
How often, in minutes, WebQoS logs aggregate service statistics to a
service statistics log file. Service statistics logging must be enabled
using the management console before aggregate service statistics are
logged. See “Service Statistics” on page 50 for a list of the logged
aggregate statistics.
In UNIX, the service statistics log file is located in the
/var/opt/webqos/stats directory. In Windows, these files are
located in the
• ServiceSLOInterval (seconds)
Default: 30
Range: 5 - 43200 (12 hours)
How often, in seconds, the SCO monitors the service level SLOs.
Chapter 2 27
<install-directory>
<install-directory>
\stats directory.
\stats directory.
Setup
WebQoS Configuration Files
Logging and Tracing Parameters (UNIX Only)
Refer to “Changing Logging and Tracing Levels” on page 116 for
information on how to change these levels on your Windows server.
The following parameters affect the amount of information written to the
logging and tracing files. Logging and tracing is dynamically updated for
the web server (information written to qoslog, qoslog.child,
qostrace, and qostrace.child). However, you must restart the SCA,
SCI, and SCO for changes to affect logging and tracing for WebQoS
components. You can control logging and tracing levels by component by
restarting specific components. For example, if you change the LOGLEVEL
from 3 to 4 but only restart the SCO, detailed logging only occurs for the
SCO. If you do not restart the SCA and SCI, the logging level remains at
level 3.
• LOGLEVEL
Default: 3 (informative logging)
Range: 0 - 4
The amount of logging information that is written to the qoslog,
qoslog.child, scalog, scilog, and scolog log files. Logging values
are:
0 - None
1 - Error
2 - Warning
3 - Informative
4 - Detailed
The larger the value, the more logging information is generated.
The log files are located in the /var/opt/webqos/logs directory.
• TRACELEVEL
Default: 0 (no tracing)
Range: 0 - 3
The amount of tracing information that is written to the qostrace,
qostrace.child, scatrace, scitrace, and scotrace files. Tracing
values are:
0 - None
1 - Data flow
2 - Detailed
3 - Procedural
Chapter 228
Setup
WebQoS Configuration Files
The larger the value, the more tracing information is logged.
The trace files are located in the /var/opt/webqos/logs directory.
URL Encoding Parameters
The following parameters allow you to support users who have disabled
cookies on their browser. These parameters are useful only if you are
using an application server such as the BroadVision One-To-One
Server1. If you change any of these parameters, you must restart the
SCA.
• APP_SESS_ENABLE_URL_ENCODING
Default: 0 (disabled)
Range: 0 (disabled), 1 (enabled), or 3 (dynamic enable)
Enable or disable URL encoding. If disabled, cookies are used to pass
state information and users who have disabled cookies are not
supported. If enabled, URLs are encoded to pass state information,
users who have disabled cookies are supported, but the aggregate
session count SLO is not useful. If set to 3, the application server you
are using allows dynamic switching between cookies and URL
encoding.
• APP_SESSION_ID_STR
No default.
The application server session identifier. How the application server
uniquely identifies its sessions. For example, BroadVision uses the
identifier BV_SessionID, so you would enter APP_SESSIONS_ID_STR
BV_SessionID in the qos.conf file.
You must enable APP_SESS_ENABLE_URL_ENCODING to use this
parameter.
1. The BroadVision One-To-One Server is a product of BroadVision,
Inc.
Chapter 2 29
Setup
WebQoS setup Script (UNIX)
Restarting Individual WebQoS Components
In UNIX, if you have configured parameters in the qos.conf file after
you have run the WebQoS setup script, you must restart (by stopping
and starting) specific components (the SCA, SCI, and/or SCO).
In Windows, if you have configured parameters in the qos.conf file, you
must restart specific components (the SCA, SCI, and/or SCO).
Restarting WebQoS Components (UNIX)
To restart the SCA, type the following:
/opt/webqos/bin/sca_stop
/opt/webqos/bin/sca_start
To restart the SCI, type the following:
/opt/webqos/bin/sci_stop
/opt/webqos/bin/sci_start
To restart the SCO, type the following:
/opt/webqos/bin/sco_stop
/opt/webqos/bin/sco_start
Restarting WebQoS Components (Windows)
On a Windows NT system, to restart a WebQoS component, go to the
Control Paneland select Services. Highlight the component you wantto
restart (WebQoS SCA, WebQoS SCI, or WebQoS SCO), click on the Stop
button and then the Start button.
On a Windows 2000 system, to restart a WebQoS component, click on
Start -> Programs -> Administrative Tools -> Services.
Double-Click on the component you want to restart (WebQoS SCA,
WebQoS SCI, or WebQoS SCO).
WebQoS setup Script (UNIX)
This utility enables and disables the WebQoS daemons and “qosifies”
your web server. You run it after your web server is installed and after
WebQoS is installed on systems running any WebQoS component or if
Chapter 230
Loading...