HP WebQoS Setup and Install

Download

Conﬁguring HP WebQoS on HP-UX

Edition 3

Manufacturing Part Number: B8311-90004

E0900

U.S.A.

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 ﬁtness 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 speciﬁc warranty terms applicable to your Hewlett- Packard product and replacement parts can be obtained from your local Sales and Service Ofﬁce.

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-00 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

©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.

Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation. MS-DOS®, Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft

Corporation.

1. Understanding HP WebQoS

The Role and Beneﬁts of HP WebQoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

WebQoS Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Request Classiﬁcations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Capacity Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Policy Based Service Level Objectives (SLOs) and Thresholds . . . . . . . . . . . . . . . 15

How WebQoS Fits Into Your Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

WebQoS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Request and Management Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2. Installing HP WebQoS

3. Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Enabling Network Type of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

The IN_TOS Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

The OUT_TOS Flag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Modifying WebQoS Global Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

SCA and Web Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

SCA Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

SCO Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Denial of Service Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Logging and Tracing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

URL Encoding Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Conﬁguring Your Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Zeus Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Conﬁguring Zeus Web Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

IP-Based Virtual Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Subservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Improving Web Server Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

iPlanet Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Running the WebQoS setup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Running setup -r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Conﬁguring WebQoS from the Management User Interface. . . . . . . . . . . . . . . . . . . . . 40

Starting the WebQoS Management User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Understanding the Management User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Contents

Adding a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Adding a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

To Conﬁgure Service Statistics Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

To Conﬁgure Service Level Objectives for the Service . . . . . . . . . . . . . . . . . . . . . . 49

To Specify Service-Wide Corrective Actions for SLOs. . . . . . . . . . . . . . . . . . . . . . . 52

Modifying Service-Wide Corrective Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Adding a Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

To Identify the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

To Identify the Web Server for the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Prioritizing Requests to the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Setting Site Service Level Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

To Specify Corrective Actions for Site SLOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Adding Site Threshold Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

To Specify Corrective Actions for Threshold Policies . . . . . . . . . . . . . . . . . . . . . . . 72

Conﬁguring Advanced Features for the Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Modifying Session Timeouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Assigning Web Server Request Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Modifying Web Server Accept Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Specifying Site-Wide Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Enabling Site Statistics Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Verifying Your Conﬁguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4. Using HP WebQoS

Navigating the Services/Systems View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Editing a System Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Editing a Site Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

To Edit the Site Type and Service Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

To Edit the Site’s Request Classiﬁcation Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

To Edit the Site’s SLOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

To Edit a Site’s Threshold Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

To Edit Session Timeouts, Request Queues, Accept Threads, and Corrective Actions. 90

To Apply Your Conﬁguration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Copying a System or Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Deleting a System, Service, or Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Monitoring SLOs and the History Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Contents

Understanding the Service Level Objectives View. . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Understanding the History Log View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Filtering SLOs and Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Filtering the History Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Displaying Site Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Viewing SLO Related Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Viewing Site Session Control Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Displaying Service Performance Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Viewing Service SLO Related Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Viewing Service Session Control Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Viewing Defer Related Statistics for the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Changing the Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Connecting to Another Management Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Shared Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Error Messages Viewable From the Management User Interface. . . . . . . . . . . . . . 115

Error Messages Viewable From the Terminal Window . . . . . . . . . . . . . . . . . . . . . . 117

Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Measurement Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Statistics Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Changing Logging and Tracing Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

5. Customizing and Using HP OpenView with HP WebQoS

Installing, Conﬁguring, and Using HP OpenView Service Reporter . . . . . . . . . . . . . 123

Installing and Conﬁguring the WebQoS System . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Installing and Conﬁguring the Service Reporter System. . . . . . . . . . . . . . . . . . . . . 125

Viewing WebQoS Reports in Service Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Installing, Conﬁguring and Using PerfView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Logging WebQoS Site Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Logging WebQoS Service Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Viewing Graphs in PerfView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Installing and Conﬁguring HP OpenView IT/Operations . . . . . . . . . . . . . . . . . . . . . . 132

Installing the Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Getting a Quick Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Customizing the ITO Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Managing the WebQoS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Contents

Troubleshooting WebQoS Processes on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

If Problems Occur But There Are No Error Messages . . . . . . . . . . . . . . . . . . . . . 138

6. Installing and Using HP LocalDirector Controller

What is HP LocalDirector Controller? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Installing HP LocalDirector Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Installing the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Conﬁguring Cisco LocalDirector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Conﬁguring HP LocalDirector Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Conﬁguring the HP LDControl Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Conﬁguring the HP LDControl Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Starting and Stopping the HP LDControl Daemon . . . . . . . . . . . . . . . . . . . . . . . . . 148

Conﬁguring a System with More than One LAN Card . . . . . . . . . . . . . . . . . . . . . . 149

Troubleshooting the HP LD Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

HP LDControl Cannot Find Cisco’s LocalDirector . . . . . . . . . . . . . . . . . . . . . . . . 149

Problems Accessing the HP LD Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

HP LDControl Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Problems with HP LocalDirector Controller and Cisco LocalDirector . . . . . . . . . . 152

A. Policy and Rule Descriptions

Request Classiﬁcation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Policies Set in WebQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Service Level Objectives for Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Service Level Objectives for the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Threshold Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Corrective Actions for SLO and Threshold Policy Violations. . . . . . . . . . . . . . . . . . 161

Customizing the Reject and Defer Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

B. HP OpenView IT/Operations (ITO) Alarms

IT/Operations Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

ITO Alarms Based on WebQoS Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

ITO Alarms Based on WebQoS Process Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . 170

ITO Alarms Based on WebQoS Statistic Crossing a Threshold. . . . . . . . . . . . . . . . 171

WebQoS Statistic Variable Names for ITO Threshold Templates. . . . . . . . . . . . . . . . 173

Contents

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.

Second Edition: March 2000 (HP-UX 11) Third Edition: September 2000 (HP-UX 11)

1 Understanding HP WebQoS

This chapter explains the roles and beneﬁts of HP WebQoS and how it ﬁts 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 Beneﬁts of HP WebQoS

HP WebQoS is an enhancement to the HP-UX operating environment that stabilizes, optimizes, and prioritizes Internet-related applications and transactions that run on HP 9000 Enterprise servers. HP WebQoS works with web-enabled applications built on top of the iPlanet Web

Server1 version 4.1 or the Zeus Web Server2 version 3.3.6. HP WebQoS enables you to use your resources efﬁciently 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 signiﬁcant 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 ﬂuctuating demand for services. 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 signiﬁcant 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.

• 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

1. The iPlanet Web Server is a product of Sun Microsystems, Inc.

2. The Zeus WebServer is a product of Zeus Technology.

Chapter 112

Understanding HP WebQoS

The Role and Beneﬁts of HP WebQoS

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 conﬁguring WebQoS based on the type of services offered and trafﬁc 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 beneﬁts of WebQoS for HP-UX 9000, Series 800 customers 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 14.

• 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 Classiﬁcations” on page 14.

• Establish rules for the classiﬁcation of service requests from users. WebQoS fulﬁlls 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 Classiﬁcations” on page 14.

WebQoS Concepts

The following are 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.

Chapter 1 13

Understanding HP WebQoS

The Role and Beneﬁts of HP WebQoS

Request Classiﬁcations

Request classiﬁcations 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 classiﬁcations 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. High request classiﬁcations have higher priority access to the server.

WebQoS supports three request classiﬁcations: high, medium, and low. During periods of heavy system load, low priority requests may possibly be redirected or rejected. If a request is accepted, it is scheduled based on its request classiﬁcation priority. Based on your conﬁgured policies, the request might be immediately processed, or it may wait in the queue while other higher priority requests are processed ﬁrst.

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, 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. 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 deﬁne a session, and for establishing the policies that control whether the session is admitted.

Capacity Protection

Capacity Protection prevents system overload with load balancing 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

Chapter 114

Understanding HP WebQoS

The Role and Beneﬁts of HP WebQoS

transactions can be completed quickly. With Capacity Protection, you conﬁgure a system when it is functioning

at peak levels to do the following:

• Redirect high priority customers to another system with available capacity.

• Defer high priority customers for a few moments until current sessions are completed.

• Reject low priority customers in extreme overload conditions.

Policy Based Service Level Objectives (SLOs) and Thresholds

To ensure that your business policies are reﬂected 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.

Business-oriented service level objectives deﬁne the following:

• Response time—measured from the time a request enters the server to the time it leaves the server.

• Concurrent session capacity—created when an initial request is accepted and maintained until the session times out.

Operations-oriented thresholds for capacity protection determine the following:

• Average CPU load—measured on the local system.

• Queue depth—the maximum number of service requests waiting that are not yet forwarded to the web server.

The administrator deﬁnes SLOs, thresholds,and their relative priorities. WebQoS can trade off meeting policies based on these priorities. Information Technology rules concerning response time, throughput, availability, and priorities for request classiﬁcation rules and applications are translated into SLOs and thresholds.

The administrator also conﬁgures corrective actions that are executed when the rules are violated. Corrective actions are a list of prioritized actions an administrator uses to help bring the SLO or threshold into compliance with the rule.

Chapter 1 15

Understanding HP WebQoS

How WebQoS Fits Into Your Environment

WebQoS, which includes a set of extensions to HP-UX, 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 efﬁciently 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.

The following describes brieﬂy the function of each part of the environment:

• The client identiﬁes itself and initiates requests.

• The network distinguishes class priorities and routes priority packets efﬁciently while delivering best effort service to lower priority packets.

• The web server distinguishes WebQoS request priorities and manipulates operating system scheduling policies 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 classiﬁed and handled by the server and network.

Chapter 116

WebQoS Components

WebQoS comprises a number of components that perform priority-based resource management and service request handling. (See Table 1-1, “WebQoSComponents.”)In addition, management components allow you to conﬁgure WebQoS for the systems on which it is installed as well as deﬁne the service level objectives (SLOs) and threshold policies that are important to your business. (For an explanation of SLOs, refer to “Service Level Objectives for Site” on page 158.)

Note that not all components are required on every WebQoS-enabled system. Refer to Figure 1-2, "Request and Management Data Flow", to understand how these components ﬁt into the WebQoS picture.

Table 1-1 WebQoS Components

Component Installed On Description

Understanding HP WebQoS

How WebQoS Fits Into Your Environment

Management User Interface

WebQoS Management Server or Service Control Operator (SCO)

Any Windows NT/95/98 system. Can be installed on multiple PCs. Mustreside onat least one system in the WebQoS domain.

Any HP-UX Enterprise Server running HP-UX 11.x. Must reside on only one system.

Allows you to conﬁgure WebQoS-enabled systems, including identiﬁcation of those systems, websites and applications that make up a particular service offering. Also lets you deﬁne performance objectives for the components of the service. Enables you to monitor performance levels and service level objectives (SLOs).

Manages the WebQoS conﬁguration and communicates with the management user interface. Sends out management control directives to the Service Control Agents (SCAs) and receives status from them.

Chapter 1 17

Understanding HP WebQoS

How WebQoS Fits Into Your Environment

Table 1-1 WebQoS Components

Component Installed On Description WebQoS Services or

Service Control Agent (SCA) and WebQoS Request Control

Any HP-UX Enterprise Server running on HP-UX 11.x and running a web server that is managed by WebQoS.

Collects performance information from the Service Resource Controller and WebQoS request control. Receives management control directives from the Service Control Operator. Distributes conﬁguration information to WebQoS nodes. The SCA monitors operation information and gives feedback to the SCO. This information is displayed by the management user interface.

This component includes the following sub-components:

Session Manager—creates sessions and tracks activity within a session until it expires.

Classiﬁer—examines attributes of a service request to determine the appropriate request classiﬁcation assignment for the request.

Admission Controller—monitors system load and response time in order to decide whether or not new sessions are accepted.

Scheduler—submits service requests to the web server based on each request's assigned request classiﬁcation priority.

Class Encoder/Decoder—encodes and decodes the request classiﬁcation priority for requests and responses into network packet headers so that network devices can handle these accordingly.

Chapter 118

How WebQoS Fits Into Your Environment

Request and Management Data Flow

In this example, you are running a web server system that is accessible by various clients through a browser. The system may be running multiple web server processes, each of which may be hosting different web sites that are assigned to different process groups. By assigning these sites to different process groups, you cause them to exhibit different performance characteristics. If you assign your most important website to the high priority process group, it receives majority access to shared system resources. Also, by assigning different priorities for each web server, you can give different performance levels to different user requests or to different actions.

Figure 1-2 Request and Management Data Flow

Understanding HP WebQoS

Chapter 1 19

Understanding HP WebQoS

How WebQoS Fits Into Your Environment

Chapter 120

2 Installing HP WebQoS

Information about installing, upgrading, and removing this product can be found in the HP WebQoS Premium for HP-UX Release Note.

Chapter 2 21

Installing HP WebQoS

Chapter 222

3 Conﬁguring HP WebQoS

This chapter describes how to modify the WebQoS conﬁguration ﬁles. It also describes the management user interface and how to use it.

Chapter 3 23

Conﬁguring HP WebQoS

Figure 3-1 WebQoS Administrator’s Task Flow

Chapter 324

Conﬁguring HP WebQoS

The steps below are explained in detail in the sections following.

1. Modify conﬁguration ﬁles from the command line before starting WebQoS.

2. Conﬁgure your web server.

3. Run the WebQoS setup script to start the WebQoS SCO.

4. Start the WebQoS management user interface. The WebQoS SCO must be started prior to starting the management user interface.

5. Use the management user interface to conﬁgure one or more systems. A system is a computer with web sites and application servers managed by WebQoS.

6. Use the management user interface to conﬁgure one or more services. A service is a way to logically group web sites that are related to the same business application. You can view logical groups of web sites as a single entity in the management user interface and you can set a service level objective for the service that allows you to put limits on the number of concurrent sessions.

7. Use the management user interface to conﬁgure one or more sites. A site is a web server instance that is managed by WebQoS. When you conﬁgure a site, you do the following:

• Connect the site logically to a previously conﬁgured service so you

can view grouped sites belonging to that service in the management user interface.

• Specify the system and port number which identify the site. The

system must already be conﬁgured in WebQoS. You can look at all the sites on a system in the management user interface.

• Prioritize requests to the site with request classiﬁcation rules.

• Deﬁne response time and capacity objectives and policies for the

site.

• Set service level objectives for the site.

8. Use the management user interface to edit your site(s).

9. Conﬁgure necessary ﬁles from the command line after conﬁguration is completed from the management user interface.

Chapter 3 25

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

The following ﬁles can be modiﬁed from the command line before starting WebQoS:

• /etc/opt/webqos/net_tos.conf (See “Enabling Network Type of Service” below.

• /etc/opt/webqos/qos.conf (See “Modifying WebQoS Global Conﬁguration” on page 27.)

Enabling Network Type of Service

Enabling network type of service (TOS) allows classiﬁcation rules to be reﬂected in network trafﬁc priorities. Please check with your network equipment provider if TOS encoding is supported.

If you would like to enable network TOS, you must modify the following conﬁguration ﬁle: /etc/opt/webqos/net_tos.conf.

Modify this ﬁle before you start up WebQoS. The ﬁle contains two ﬂags, IN_TOS and OUT_TOS, which tell WebQoS how to interpret and set the TOS byte in the IP headers of incoming and outgoing requests.

The IN_TOS Flag

The IN_TOS ﬂag tells WebQoS how to interpret the TOS values of requests coming into WebQoS from your clients. If you have conﬁgured your networking devices (for example routers or switches) to set the TOS byte, and you want WebQoS to classify incoming requests based on that value rather than other request classiﬁcation rules (for example IP address, URL, or port number), you should set this ﬂag to TRUE. Then conﬁgure the expected value ranges for each request classiﬁcation. Next, you conﬁgure your request classiﬁcation rules to enable network QoS. Refer to “Setting Site Service Level Objectives”.

The OUT_TOS Flag

The OUT_TOS ﬂag tells WebQoS how to set the TOS values for outgoing responses back to the client. If your network devices are conﬁgured to interpret these settings, you can signal these network devices to ensure

Chapter 326

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

your requests receive the appropriate priority across the network. Speciﬁc instructions to enable network TOS are included in the

/etc/opt/webqos/net_tos.conf ﬁle.

Modifying WebQoS Global Conﬁguration

To modify your WebQoS global conﬁguration, you need to modify the /etc/opt/webqos/qos.conf conﬁguration ﬁle.

You should do this before you run the WebQoS setup script. If you update this ﬁle after running the setup script, the web server must be restarted for any changes to take effect. However, logging and tracing parameters can be changed dynamically and take effect when a site is edited.

The following parameters can be set:

SCA and Web Server Parameters

The following parameters affect the SCA and web server. If you change any of these parameters, you must restart the SCA and web server.

• HTTPVersion - Default: HTTP/1.1

• KeepDeferringAfterMaxDeferTime - No default Defer users when the maximum defer time is reached. Set this

parameter to TRUE to continue deferring users.Set this parameter to FALSE to reject users when the maximum defer time is reached.

• MeasurementInterval - Default: 30 seconds How often, in seconds, WebQoS collects performance measurements.

The MeasurementInterval must be an even multiple of the MonitorInterval. The minimum value is 5 seconds.

If Site Statistics Logging is enabled in the management user interface, this parameter also speciﬁes the interval at which the SCA generates site statistics.

• MonitorCPUWeight - Default: 20% 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:

Chapter 3 27

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

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).

If you modify MonitorCPUWeight, you must restart the SCA and your web server.

• MonitorInterval - Default: 5 seconds How often, in seconds, threshold policies are monitored. The

minimum value is 5 seconds. If you change the value, you must restart the web server.

• MonitorResponseTimeWeight - Default: 50% 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.

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).

• NumOfDeferredSessionsPerMinute - No default The number of sessions that can be deferred per minute. If the value

is greater than 60, then the parameter NumOfDeferredSessionsPerSecond automatically increases.

• NumOfDeferredSessionsPerSecond - Default: 1

Chapter 328

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

The number of deferred sessions that have the same deferral time allocated to them. Minimum deferral time is 10 seconds; maximum is 120 seconds.

Forexample, if you set this parameter to 1 and two requests arrive at the same time, the ﬁrst deferred session is allocated a deferral time of 10 seconds and the second deferred session is allocated a deferral time of 11 seconds. If you set the parameter to 2 and two requests arrive at the same time, the ﬁrst deferred session is allocated a deferral time of 10 seconds and the second also is allocated a deferral time of 10 seconds.

SCA Parameters

The following parameters affect the SCA only. If you change any of these parameters, you must restart the SCA.

• LogInterval - Default: 30 minutes How often, in minutes, WebQoS logs measurements to a

measurement log ﬁle located in the directory /var/opt/webqos/measures. The LogOn parameter must be enabled (set to 1) before WebQoS logs measurements to the log ﬁle. The minimum value is 1 minute.

• LogOn - Default: 0 (disabled) 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 ﬁle daily for each WebQoS site and places it in the directory /var/opt/webqos/measures. The measurement log ﬁle name is the site name you entered in the management user interface followed by the date. The log ﬁle contains performance measurements collected during the day for the site.

The measurements logged include: — Average response time for each request class

— Number of new, redirected, deferred, and rejected sessions foreach

request class

— Average and maximum queue lengths

• SaveFiles - Default: 0 (disabled)

Chapter 3 29

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

Enable or disable saving measurement log ﬁles (located in the directory /var/opt/webqos/measures). If enabled, all measurement log ﬁles are saved. If disabled, measurement log ﬁles 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.

• SCOLogInterval - Default: 5 minutes How often, in minutes, WebQoS logs aggregate service statistics to a

service statistics log ﬁle located in the directory /var/opt/webqos/stats). Service statistics logging must be enabled using the management user interface before aggregate service statistics are logged. Values range from 5 to 30 minutes. See “To Conﬁgure Service Statistics Logging” on page 47 for a list of the logged aggregate statistics.

• SCOLogSROn - Default: 0 (disabled) Enable or disable logging to HP OpenView MeasureWare. You can

view the statistics logged using the HP OpenView Service Reporter. Service statistics logging must be enabled using the management user interface before statistics are logged.

To enable logging, set this parameter to 1. To disable logging, set this parameter to 0.

• ServiceSLOInterval - Default: 30 seconds How often, in seconds, the SCO requests the site SLO status from the

SCA.

Denial of Service Parameters

The following parameters can be set to protect your web server from denial of service attacks.

Connections with No Data Conﬁgure the following parameters to protect your web server against excessive connections that contain no data.

• MaxPollDescriptors - Default: 50% of the total number of ﬁle descriptors available for each process deﬁned by the maxfiles kernel parameter. For example, if the maxfiles kernel parameter is 4096,

Chapter 330

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

then the default value is 2048. The maximum number of connections that are polled or checked for

data. This parameter prevents connections with no data from using too many ﬁle descriptors. HP recommends that this value be a percentage of the maxfiles kernel parameter.

• NoDataConnectionTimeout - Default: 30 seconds The amount of time, in seconds, to wait before closing a connection

without data. If no data is received for a connection in this amount of time, the

connection is closed.

• PollThreadSleepTime - Default: 100 milliseconds The amount of time, in milliseconds, to wait before checking if any

data has arrived. If a connection with no data is received, then wait for this amount of

time before checking the connection for the arrival of data. The total number of times the connection is checked for data during

the NoDataConnectionTimeout time is calculated by dividing NoDataConnectionTimeout by this value. For example, using the default values, the connection with no data is checked for data 300 times (30 seconds/100 milliseconds) in a 30 second period.

• WaterMarkForNoDataConn - Default: 95% of MaxPollDescriptors When MaxPollDescriptors is reached, an event is sent indicating

that there are too many connections with no data. When the total number of ﬁle descriptors falls below this percentage of MaxPollDescriptors, another event is sent indicating that the number of connections with no data is at an acceptable level.

Logging and Tracing Parameters

The following parameters affect the amount of information written to the logging and tracing ﬁles.

• LOGLEVEL - Default: 3 (informative logging) The amount of logging information that is written to the ﬁles

/var/opt/webqos/logs/qoslog and /var/opt/webqos/logs/acclog. Logging values are:

0 - None

Chapter 3 31

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

1 - Error 2 - Warning 3 - Informative 4 - Detailed

The larger the value, the more logging information is generated.

• TRACELEVEL - Default: 0 (no tracing) The amount of tracing information that is written to the ﬁle

/var/opt/webqos/logs/qostrace and /var/opt/webqos/logs/acctrace. Tracing values are:

0 - None 1 - Data ﬂow 2 - Detailed 3 - Procedural

The larger the value, the more tracing information is logged.

NOTE The logging and tracing parameters are the only parameters in the

qos.conf ﬁle that can be changed dynamically. Changes to these parameters take effect when a site is edited.

Chapter 332

Conﬁguring HP WebQoS

Modifying Conﬁguration Files Before Start-Up

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 the BroadVision One-To-One Server1.

• BV_SYSTEM_NAME - No default This is the name of the BroadVision One-To-One root server. Set this

parameter only if you are using the BroadVision server. Youcan enter up to two server names. The names must be separated by a space.

This parameter must be deﬁned on the WebQoS management server system if you are using the BroadVision server.

• BV_USER_NAME - No default This is the user name conﬁgured on the BroadVision One-To-One

server. The user cannot be root. This parameter must be deﬁned on the WebQoS services system and

the WebQoS management server system if you are using the BroadVision server.

• ENABLE_URL_ENCODING_BV - Default: 0 (disabled) If you are running the BroadVision One-To-One Server, you can use

BroadVision’s session count to keep track of the aggregate session count for the service. This allows you to support users who have disabled cookies on their browser. To enable this feature, set this parameter to 1.

This parameter must be deﬁned on the WebQoS services system and the WebQoS management server system if you are using the BroadVision server.

If the BroadVision One-To-One Server is not installed but you enable this parameter, WebQoSuses URLs to maintain state information. In this case, the aggregate session count SLO is not useful.

1. The BroadVision One-To-One Server is a product of BroadVision, Inc.

Chapter 3 33

Conﬁguring HP WebQoS

Conﬁguring Your Web Server

This section lists required and optional parameters that can be conﬁgured for your web server.

Zeus Web Server

Conﬁguring Zeus Web Server Parameters

You must conﬁgure the following Zeus web server parameters with the given values in order to use WebQoS successfully. Each parameter is formatted as follows:

parameter_name: given_value In $ZEUSHOME/webadmin/config/sites/

IP-based virtual server, conﬁgure the following parameter (this parameter can also be conﬁgured by modifying the Bind address ﬁeld in the General Server Configuration screen of the Zeus web administration server for each IP-based virtual server):

• bindaddr: IP address of the IP-based virtual server The IP address assigned to the IP-based virtual server. Used with the tuning!bind_any parameter, this parameter allows

you to conﬁgure WebQoSindividually for each IP-based virtual server (you can conﬁgure each IP-based virtual server as an individual site in WebQoS).

If this parameter is not conﬁgured, WebQoS can only be conﬁgured globally for all virtual servers (you must conﬁgure all virtual servers as one site in WebQoS).

In $ZEUSHOME/web/global.cfg, conﬁgure the following parameters:

• tuning!bind_any: no Do you want to bind the virtual server with any IP address? If the bindaddr parameter is conﬁgured and this parameter is set to

no, the web server can bind a speciﬁc IP address with each IP-based virtual server. This allows you to conﬁgure WebQoS individually for each IP-based virtual server (you can conﬁgure each IP-based virtual server as an individual site in WebQoS).

virtual_server

, for each

Chapter 334

Conﬁguring HP WebQoS

Conﬁguring Your Web Server

If this parameter is set to yes or if bindaddr is not conﬁgured, WebQoS can only be conﬁgured globally for all virtual servers (you must conﬁgure all virtual servers as one site in WebQoS).

Chapter 3 35

Conﬁguring HP WebQoS

Conﬁguring Your Web Server

• tuning!use_poll: yes Do you want to use the system call poll() instead of select()? poll() gives you better performance and is the default system call

used if this parameter is not set. WebQoS only supports the poll() system call.

IP-Based Virtual Servers

WebQoS supports IP-based virtual servers (hardware virtual servers) where each IP-based virtual server has a unique IP address and port number combination. This allows each IP-based virtual server to be conﬁgured as an individual site in WebQoS.

NOTE IP-Based virtual servers cannot be added nor deleted dynamically. That

is, you must stop the web server before you can add or delete an additional IP-based virtual server (see the next two sections for more information).

All IP-based virtual servers must be running and each IP-based virtual server must be conﬁgured as an individual site in WebQoS before WebQoS can be active.

Adding an Additional IP-Based Virtual Server If you want to add an additional IP-based virtual server,do the following (refer to your Zeus web server documentation for more information):

1. Stop the Zeus web server from the Zeus administration server.

2. Add the virtual server.

3. Start the Zeus web server.

4. Enable all virtual servers.

5. Conﬁgure the added IP-based virtual server as a WebQoS site.

Deleting/Disabling an IP-Based Virtual Server To disable an IP-based virtual server, you must delete it. To delete an IP-based virtual server, do the following (refer to your Zeus web server documentation for more information):

1. Stop the virtual server.

Chapter 336

Conﬁguring HP WebQoS

Conﬁguring Your Web Server

2. Stop the Zeus web server from the Zeus administration server.

3. Delete the virtual server.

4. Start the Zeus web server.

5. Make sure all virtual servers are enabled.

6. Remove the site in WebQoS.

Subservers

Zeus allows you to conﬁgure subservers (software virtual servers or host header-based virtual servers). These subservers cannot be conﬁgured individually in WebQoS. Instead, all subservers conﬁgured to one IP address and port number are conﬁgured as one site in WebQoS.

Adding/Deleting an Additional Subserver Subservers can be added and deleted dynamically (refer to your Zeus web server documentation for more information). You do not have to stop the web server.

Improving Web Server Performance

For information about improving the performance of your Zeus web server, refer to question 7.1 (How can I tune the webserver for maximum performance) of the Zeus FAQ located at http://support.zeus.com/faq/.

iPlanet Web Server

Please refer to the following web page for iPlanet Web Server 4.1 performance conﬁguration information:

http://docs.iplanet.com/docs/manuals/enterprise/41/ag/esperfrm.htm#1011987

Please refer to the following web site for the iPlanet Web Server 4.0 tuning guide:

http://home.netscape.com/eng/server/webserver/4.0/perf.html

Please refer to the following web site for iPlanet Web Server 4.1 documentation:

http://docs.iplanet.com/docs/manuals/enterprise.html#41

Chapter 3 37

Conﬁguring HP WebQoS

Running the WebQoS setup Script

This utility enables and disables the WebQoS daemons and web servers with WebQoS. You run it after WebQoS is installed on systems running the web server tier, application server tier, and on the management system where the SCO is run.

Run the following script on any HP-UX system you are using as an application tier or a web server tier for WebQoS:

/opt/webqos/install/setup

When you run the setup script, you must provide the following information:

• Continue running the script? If you do not want to run WebQoS or read the software license terms,

you can exit the script now. Otherwise, enter y to continue.

• Do you accept the HP software license terms? If you accept the software license terms and want to continue running

the setup script, enter y. Otherwise, enter n to exit the script.

• Do you want to enable the SCO? You must enable one SCO in your WebQoS domain in order to

conﬁgure and manage your WebQoS-enabled web servers.

• Do you want to start the qosmond daemon? If you want to use HP OpenView IT/Operations with WebQoS, the

qosmond daemon must be started.

• Conﬁgure the management user interface password. This is the password you use to log in to the management user

interface. There is one password for each management server.

• Select the type of web server on which you want to use WebQoS. Choose either NES (Netscape Enterprise Server) or Zeus.

• Enter the root pathname of your web server. This is the path to the web server you want to manage on this system.

The setup script installs WebQoS for all the web servers operating under the directory you specify.

Chapter 338

Conﬁguring HP WebQoS

Running the WebQoS setup Script

If you do not want to conﬁgure any web servers, enter NONE.

• Do you want to remove HP Admission Control? This question appears only if you have installed an older version of

WebQoS (HP ServiceControl) on your system. You must remove HP Admission Control in order to use this version of WebQoS. If you answer no, you will exit the script and you will not be able to use this version of WebQoS.

• Log the service statistics to MeasureWare? This questions appears only if MeasureWare is already installed on

your system. WebQoShas been integrated with some components of HP OpenView.

If you would like to view WebQoS reports, statistics, graphs, and events in HP OpenView, answer yes.

The setup script also starts the Service Control Agent.

Running setup -r

If you decide you no longer want to use WebQoS with your web server, run the following command.

/opt/webqos/install/setup -r

WebQoSconﬁguration data is preserved in case you want to run WebQoS again later.

When you run setup -r, you must provide the following information:

• Continue running or exit the script? If you want to continue using WebQoS, you can exit the script now.

• Select the type of web server on which you no longer want to use WebQoS.

Choose either NES (Netscape Enterprise Server) or Zeus.

• Enter the root pathname of the web server.

Chapter 3 39

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Once you have installed the relevant WebQoS components on each of your web and application servers and have performed the appropriate modiﬁcations to conﬁguration ﬁles, you can conﬁgure WebQoS to know about the applications and web sites hosted on the WebQoS-enabled systems.

WebQoS considers each web site and application to be a component of some service that you are offering to your customers or partners. By telling WebQoS what service each site supports, the WebQoS management user interface allows you to displaythe status of the service as well as all sites relating to the service. This allows you to take a Service Level view of your environment, rather than an individual Service Component view. By taking a Service Level view you can better appreciate how your customers are experiencing your service.

The sections that follow provide instructions to help you do the following:

• Identify the services that are being offered by your business.

• Identify the web sites that are components of the service, including:

❏ The system and web server process that hosts each site. ❏ Performance and capacity objectives for the site. ❏ Corrective actions that you can take when the objectives are not

being met.

❏ Rules for classifying, prioritizing and processing requests that

come into the site.

• Conﬁgure monitoring intervals for the resources that are being shared.

Chapter 340

Conﬁguring WebQoS from the Management User Interface

Starting the WebQoS Management User Interface

To start the WebQoS management user interface, follow these steps:

1. Double-Click on the WebQoS icon on the Windows desktop. The WebQoS login dialog box appear (Figure 3-2, “WebQoS Login Dialog Box”).

Figure 3-2 WebQoS Login Dialog Box

2. Enter the system name where the WebQoS management server (SCO) is installed. This system is also called the management station.

3. Enter the WebQoS management station password. There is one password per management station. You can change this password by choosing File: Change Password from the management user interface.

Conﬁguring HP WebQoS

If you forget your password, you can specify a new one by running /opt/webqos/install/setup -p on the system on which the WebQoS management server is installed.

4. Choose [OK]. The user interface shown below allows you to conﬁgure and use WebQoS to manage the service levels provided by your web servers.

Chapter 3 41

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-3 The Management User Interface View

Menu Bar

Task Bar

Pulldown Lists

Services/ Systems Views

SLO/

History Views

Status Summary

Understanding the Management User Interface

The following table describes the management user interface top level screen. For detailed information, refer to the WebQoS online Help.

Table 3-1

Window Area Description

Menu Bar The File menu allows you to change the administrator’s

password. The Actions menu allows you to add, edit, copy, or delete

services, systems, and sites. You can also ﬁlter SLOs and the History log.

The Help menu provides overview online help and product information.

Task Bar Each button provides quick access to some actions in the

Actions menu.

Chapter 342

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Table 3-1

Window Area Description

Pulldown Lists The Services/Systems pulldown list allows you to select

either the services view or the systems view. The Service Level Objective/History log pulldown list allows

you to select either the SLO view or the History log view.

Services/Systems Views These views display a tree containing your conﬁgured

services, systems, and sites (your domain topology). The Services view displays your domain by services. The

systems and sites that provide each service are displayed below the service.

The Systems view displays your domain by systems. The services and sites available on each system are displayed below the system.

For an explanation of the symbols see “Navigating the Services/Systems View” on page 86.

When editing or deleting a service, system or site, you must ﬁrst select it in this view area.

SLO /History Views Displays the SLOs or history log for the service, system, or

site that you selected in the Services/Systems view area. For an explanation of the color codes, see “Understanding

the Service Level Objectives View” on page 94, and “Understanding the History Log View” on page 96.

Status Summary The buttons at the bottom report the number of SLOs being

violated, at risk, in compliance, and inactive. For an explanation of the color codes, see “Understanding

the Service Level Objectives View” on page 94.

Chapter 3 43

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Adding a System

To conﬁgure WebQoS for your environment you must ﬁrst inform the WebQoS management system on which servers WebQoS is installed. To

do this, add a system entry for each server that will run WebQoS. To add a system, follow these steps:

1. From the management user interface, choose Actions: Add -> System. The Add System Configuration dialog box appears.

Figure 3-4 Add System Conﬁguration Description Dialog Box

2. In the Add System Configuration Description dialog box, enter the system name in the System Name input box. The name does not need to be fully qualiﬁed. You may enter an alias. The system name must be recognized by Domain Name Service (DNS).

Chapter 344

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

3. When you have ﬁnished your modiﬁcations, choose [OK].

You can view the system you conﬁgured by selecting Systems from the Systems/Services pull down menu on the main management user interface view. The Service Control Agent must be started or already running for these changes to take effect.

NOTE If you select a system and choose File: Delete, all the conﬁgurations

for sites on that system are also deleted. Any service conﬁguration on that system will remain.

Adding a Service

A Service is a way to logically group web sites related to a business application that you offer to your customers or partners. The service deﬁnition lets an administrator view logical groups of web sites and other business application components as a single entity.

To add a service, do the following:

1. Choose Actions: Add -> Service from the management user interface, The Add Service Configuration Description dialog box appears.

Chapter 3 45

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-5 Add Service Conﬁguration Description Dialog Box

2. Enter the service name in the Add Service Configuration dialog box. A service name can be anything that is meaningful to you as an administrator of WebQoS. For example, a service name could be “BigCompany.” The “BigCompany” service might contain sites such as: www.BigCompanyStore.com, www.BigCompanySupport.com and www.BigCompanyHR.com. You can use spaces in the name. (To conﬁgure the sites of a service, see “Adding a Site” on page 60.)

You can view the service you conﬁgured by selecting Services from the Systems/Services pull down in the main management user interface view.

NOTE If you select a service and choose File: Delete all the conﬁgurations for

sites in that service are also deleted. Any system conﬁguration for that service will remain.

3. If you wish the WebQoS SCO to generate aggregate service statistics

Chapter 346

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

logging, or conﬁgure service level objectives, go to the next sections. Otherwise click [OK].

To Conﬁgure Service Statistics Logging

By default, service statistics logging is disabled. If you enable Service Statistics Logging in the management user

interface, WebQoS will log statistics to a service statistics log ﬁle in /var/opt/webqos/logs for each of the enabled services. The statistics ﬁle is created daily until you disable Service Statistics Logging in the management user interface. The ﬁle name is < service name is the one entered in the management user interface. At midnight, the ﬁle is moved to <

You can specify the interval at which the SCO generates the service statistics by editing the SCOLogInterval parameter in the /etc/opt/webqos/qos.conf ﬁle. The minimum value is 5 minutes; the maximum value is 30 minutes. The default value is 5 minutes. For more information on the SCOLogInterval parameter, see “Modifying WebQoS Global Conﬁguration” on page 27.

To enable service statistics logging, do the following:

servicename

>.stat.<

previousdate

>.stat. The

1. From the Add Service Configuration window, select the Statistics tab.

Chapter 3 47

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-6 Add Service Conﬁguration Statistics Dialog Box

2. Click on the Check to enable service logging box. The following aggregate statistics are logged in the service statistics

log ﬁle:

Timestamp Sessions Admissions Deferrals Redirections Rejections Compliances (Number of sites in compliance) At Risk (Number of sites at risk) Violation (Number of sites in violation) Other (Number of sites in states other than compliance, at risk, or violation) Response High Response Medium Response Low Admissions High Admissions Medium Admissions Low Deferrals High Deferrals Medium Deferrals Low

Chapter 348

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Redirections High Redirections Medium Redirections Low Rejections High Rejections Medium Rejections Low Deferred Outstanding High Deferred Outstanding Medium Deferred Outstanding Low Deferral Time Average High Deferral Time Average Medium Deferral Time Average Low Deferral Time Current High Deferral Time Current Medium Deferral Time Current Low

3. If you wish to conﬁgure a Service Level Agreement for the service, go to the next section. Otherwise click [OK].

To Conﬁgure Service Level Objectives for the Service

A service level objective (SLO) speciﬁes the level of service that you expect to provide. WebQoS monitors compliance and takes corrective actions if you have speciﬁed them. SLOs put limits on the total number of sessions that have not expired and are possibly active for all the sites in the service. If you have conﬁgured the SLO, the results are displayed by selecting the Service in the main Management Interface Window and clicking on the Statistics icon in the task bar.For more information on viewing statistics, see “Displaying Service Performance Statistics” on page 107.

To add the SLO for the service, do the following:

1. From the Add Service Configuration window select the SLOs tab (Figure 3-7, "Add a Service Conﬁguration SLO Dialog Box").

Or, if you are adding the SLO to an existing service, select the service in the Services/Systems pulldown menu and choose the Edit task icon button.

Chapter 3 49

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-7 Add a Service Conﬁguration SLO Dialog Box

2. Add the service level objective by choosing the [Add] button (Figure 3-8, "Add Service Level Objectives Dialog Box").

Chapter 350

Conﬁguring WebQoS from the Management User Interface

Figure 3-8 Add Service Level Objectives Dialog Box

Conﬁguring HP WebQoS

3. Fora service, WebQoS offers the SLO Support at most <NUMBER> concurrent sessions. This SLO lets you support a speciﬁc NUMBER of concurrent sessions for the service. Concurrent sessions

means the total number of sessions that have not expired and are possibly active.

4. Enter an appropriate number in the Number input box. 5 is the default.

5. Enter the appropriate SLO Priority. The SLOs are prioritized in ascending order, with priority 1 having the highest priority. The SLO priority determines which SLO will have its corrective actions taken.

Only one SLO at a time may have corrective actions in force. The SLO with the highest priority is the one with corrective actions in force, and currently in violation. If there are two SLOs with the same priority and both are in violation, the one which became violated ﬁrst is the one with corrective actions in force (unless there is an SLO with higher priority that is also in violation.)

6. If you wish to add corrective actions for when the SLO is violated, go to the next section “To Specify Service-Wide Corrective Actions for

Chapter 3 51

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

SLOs”. Otherwise click [OK].

To Specify Service-Wide Corrective Actions for SLOs

Corrective actions are those actions taken to bring an SLO into compliance. Corrective actions may involve making trade-offs between requests belonging to different Request Classes, or making trade-offs between requests going to different sites or services running on the same system. You can add, edit or delete corrective actions by selecting the appropriate button.

1. Tospecify corrective actions when the aggregate session count SLO is violated, choose [Add] in the Add Service Level Objectives dialog box (Figure 3-8, "Add Service Level Objectives Dialog Box").

Figure 3-9 Add Corrective Actions Dialog Box

2. In the Add Corrective actions dialog box (Figure 3-9, "Add Corrective Actions Dialog Box") select the type of corrective action from the If Violated pull down menu.

For speciﬁc information on the corrective actions supported by WebQoS, and descriptions of Number and Class parameters, see “Corrective Actions for SLO and Threshold Policy Violations” on page 161.

3. Enter the appropriate Number if applicable. Number is the number of times a session is redirected for the speciﬁed request class.

4. Select the Class from the pull down menu.

Chapter 352

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

highest priority occurs ﬁrst. Priority is based on the order assigned to the action, with order 1 having the highest priority.

For example, a set of corrective actions can be:

Order 1: Redirect low class sessions 3 times Order 2: Reject low class sessions

A low class session is redirected up to three times. If a session has been redirected three times, it is rejected.

It is recommended that the reject action be conﬁgured as the last action (lowest priority) for the class.

You can change the order of the corrective actions by moving their order using the [Move Up] and [Move Down] buttons in the Add Service Level Objectives dialog box.

6. Click [OK].

Modifying Service-Wide Corrective Actions

Once you have conﬁgured corrective actions for SLO violations, you may want to defer, redirect, or reject corrective actions. Follow the steps in the sections below.

Deferring Service-Wide Corrective Actions To defer a corrective action for an SLO violation, do the following:

1. From the management user interface, select Actions> Edit> Service.

2. Select the Advanced tab from the Add Service Configuration Advanced dialog box (Figure 3-10, "Edit Service Conﬁguration Dialog Box").

Chapter 3 53

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-10 Edit Service Conﬁguration Dialog Box

3. Select Corrective Action Policy Details... from the Add Service Configuration Advanced dialog box.

Chapter 354

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-11 Service Corrective Action Conﬁguration Defer Dialog Box

4. In the Corrective Action Defer dialog box (Figure 3-11, "Service Corrective Action Conﬁguration Defer Dialog Box") enter the following information:

a. Enter the minimum wait in seconds for each defer period in the

Minimum Wait (in secs): input box. The default is 10 seconds.

b. Enter the maximum wait in seconds for each defer period in the

Maximum Wait (in secs): input box. The default is 120 seconds. Make sure the maximum wait number you enter is larger than the minimum wait number. The maximum number must be less than 3,600 (1 hour).

c. Enter the maximum number of times that a corrective action is

deferred in the Maximum Times to Defer: input box. The default is 1.

Chapter 3 55

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

d. If you want to guarantee entry after the initial defer, accept the

default in the Automatically Enter box. If not, click on the toggle to remove the checkmark.

e. You can choose to send either a Defer Message (the default), or

you can choose to send the request to a URL.

• If you choose a URL, click on the toggle in the Is URL box, delete the default text in the Defer Message box, and enter the URL, for example: http://www.Bigcompany.com. Make sure the URL is to a different site.

• If you choose to use the Defer Message, you can use the default Defer Message, or edit the text as appropriate for your situation.

5. When you have entered all your information, choose [OK] in the Service Corrective Action Configuration Defer dialog box.

Redirecting Service-Wide Corrective Actions To redirect a corrective action for an SLO violation, do the following:

1. From the management user interface, select Actions> Edit> Service.

2. Select the Advanced tab from the Add Service Configuration Advanced dialog box (Figure 3-10, "Edit Service Conﬁguration Dialog Box").

3. Select Corrective Action Policy Details... from the Add Service Configuration Advanced dialog box.

4. Choose Redirect from the Corrective Action Configuration dialog.

Chapter 356

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-12 Service Corrective Action Conﬁguration Redirect Dialog Box

5. You can choose to enable or disable Service-wide redirection corrective actions in the Corrective Action Configuration Redirect dialog box (Figure 3-12, "Service Corrective Action Conﬁguration Redirect Dialog Box"). The default is disable. This redirection conﬁguration applies to all redirection corrective actions for the Service. If the redirection is disabled, the redirection corrective actions are ignored. This is only applicable if you choose the Redirect sessions up to NUMBER times for CLASS priority request corrective action, otherwise it is ignored. The redirection information is stored so that you can enable the redirection any time.

To enable service-wide redirection corrective actions, choose the

Enable Redirection toggle in the Service Corrective Action Configuration Redirect dialog box.

You must enter either the URL of the website (for example,

Chapter 3 57

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

http://www.Bigcompany.com), or the cluster domain to redirect to (for example, city.company.com). If both are ﬁlled in, WebQoS uses the cluster domain information ﬁrst.

If you choose URL of website to redirect to this is the top level URL of the website.

If you choose Cluster Domain to redirect to, requests are forwarded to one of the servers also running WebQoS on that domain.

If no cluster domain is conﬁgured, or if requests cannot be forwarded to the cluster domain, they are forwarded to the website URL. WebQoS can dynamically detect other servers and their availability on the cluster domain.

6. When you have entered all your information choose [OK] in the Service Corrective Action Redirect dialog box.

Rejecting Service-Wide Corrective Actions To reject a corrective action for an SLO violation, do the following:

1. From the management user interface, select Actions> Edit> Service.

2. Select the Advanced tab from the Add Service Configuration Advanced dialog box (Figure 3-10, "Edit Service Conﬁguration Dialog Box").

3. Select Service-Wide Corrective Actions... from the Add Service Configuration Advanced dialog box.

4. Choose the Reject tab from the Service Corrective Action Configuration dialog.

Chapter 358

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-13 Service Corrective Action Conﬁguration Reject Dialog Box

5. From the Corrective Action Configuration Reject dialog box (Figure 3-13, "Service Corrective Action Conﬁguration Reject Dialog Box") you can choose to send either a reject message (the default), or specify an HTML ﬁle name.

If you choose to use a reject message, you can use the default reject message or edit the text as appropriate for your situation.

If you choose an HTML ﬁle name, click on the toggle in the Reject

message is an HTML file name box, delete the default text in the Reject Message box, and enter a fully qualiﬁed ﬁle name (for

example: /opt/docs/reject.html).

6. When you have entered all your information choose [OK].

Chapter 3 59

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Adding a Site

Before adding a site you must conﬁgure the site’s system and service(s) (See “Adding a System” on page 44 and “Adding a Service” on page 45).

A site entry contains the WebQoS conﬁguration for a web server instance. The web server does not have to be running in order for you to conﬁgure WebQoS. However,it would be helpful if you complete your web server conﬁguration before conﬁguring the site in WebQoS. You need to know the web server's port number to conﬁgure WebQoS.

When you add a site to WebQoS, you do the following:

• Identify the site.

• Connect it logically to a service so you can look at all components belonging to that service when needed.

• Identify the web server(s) for the site.

You can then edit a site to do the following:

• Prioritize user requests to the site with request classiﬁcations.

• Deﬁne the response time and capacity objectives for the site.

• Deﬁne site thresholds for capacity protection.

• Deﬁne the priority of the SLOs and thresholds with respect to each other.

NOTE If you copy a web site across two or more servers, you need to add a site

entry for each server on which the web site resides. You can use the [Copy] button in the management user interface to copy the site conﬁguration information and simply specify a new system name.

Chapter 360

Conﬁguring WebQoS from the Management User Interface

To Identify the Site

1. From the management user interface, choose Actions: Add -> Site. The Add Site Configuration Description dialog box

appears (Figure 3-14, "Add Site Conﬁguration Description Dialog Box").

Figure 3-14 Add Site Conﬁguration Description Dialog Box

Conﬁguring HP WebQoS

2. Enter a site name in the Site Name input box. The site name is required. Choose a site name that is easy to remember. It does not have to match any other conﬁgured names.

3. Select the Site Type from the pulldown menu.

4. To associate a site with a service, select the service name from the Service Name pulldown box. Selecting the service name is required. The service name must have been conﬁgured previously using Actions: Add -> Service from the management user interface.

To Identify the Web Server for the Site

1. To identify the web server for the site, select the Web Server tab (Figure 3-15, "Add Site Conﬁguration Web Server Dialog Box") and select the system name in the System Name pulldown box. This

Chapter 3 61

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

must be the name of the system on which the web server is running. The system has been previously conﬁgured using Actions: Add -> System from the management user interface.

Figure 3-15 Add Site Conﬁguration Web Server Dialog Box

2. Enter the appropriate IP address in the IP Address input box if your web server is bound to an IP address. ANY is the default.

To ﬁnd out if your web server is bound to an IP address,

• for the iPlanet Web Server, look in the

server_root

/https-

server_identifier

/config/magnus.conf

ﬁle for the Address ﬁeld. If there is an Address entry, specify the associated IP address in the IP Address input box.

• for the Zeus web server, look in the

$ZEUSHOME/webadmin/config/sites/

virtual_server

ﬁle for the bindaddr ﬁeld. If there is a bindaddr entry, specify the associated IP address in the IP Address input box.

3. Enter the port number of the web server in the Port Number input box. The port number is the number that is conﬁgured in the web server conﬁguration ﬁles for the web server hosting the site. A site on one system can use the same port number as another site on that system, as long as the IP addresses are different. The port number is required; the default is set to 80.

Chapter 362

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

4. Choose [OK] in the Add Site Configuration dialog box.

5. If you wish to conﬁgure other options for the site such as classiﬁcation rules, service level objectives, or threshold policies, go to the next section, “Prioritizing Requests to the Site”.

Prioritizing Requests to the Site

To prioritize requests to the site, you add request classiﬁcation rules which affect how quickly the request is processed, as well as if the request is processed at all. Adding request classiﬁcation rules is optional.

1. In the main WebQoS window, select the site whose conﬁguration you want to edit from the Services/Systems view.

2. Choose the Edit task icon button on the task bar or the Actions: Edit menu command.

3. Select the Classification Rules tab (Figure 3-16, "Edit Site Conﬁguration Classiﬁcation Rules Dialog Box").

Figure 3-16 Edit Site Conﬁguration Classiﬁcation Rules Dialog Box

4. Add a Classiﬁcation Rule by choosing the [Add] button.

Chapter 3 63

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-17 Add Request Classiﬁcations Rules Dialog Box

5. Select the appropriate Classification Type from the pull down menu in the Add Request Classification Rules dialog box (Figure 3-17, "Add Request Classiﬁcations Rules Dialog Box"). For a description of request classiﬁcation rules, see “Request Classiﬁcation Rules” on page 156.

6. Depending on which Classification Type you selected, enter the appropriate information in the Path, Address, Name, or Port Number ﬁeld:

• Address is the IP address from which the site is being accessed or

the IP address used to access the site.

• Port Number is the number of the port used by the session to

access the site. A port number is any integral from 1 to 65535.

• Path is the URL Document Path. This is the directory path and

ﬁlename of the URL used to access the site. Forexample, given the URL http://some_system.domain.com/my_path/index.html, the URL document path is /my_path/index.html. The leading backslash is optional for the case of a wildcard URL document path, but it is required for the non-wildcard case. For further information on wild card usage, see the online help for adding classiﬁcation rules.

• Name is the virtual server name or alias for the site.

7. If necessary, select the Class from the pull down menu. Class assigns a session or request to the selected request class. The level of service for each request class is deﬁned in the SLOs. Some classiﬁcation rules do not require a value to be entered.

Chapter 364

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

8. Choose [OK]in the Add Request Classification Rules dialog box.

9. To add more request classiﬁcation rules, repeat the previous steps. Or, to conﬁgure service level objectives for the site, go to the next section “Setting Site Service Level Objectives”.

10.To apply your conﬁguration, when you have completed conﬁguring your site, select [OK] in the Edit Site Configuration dialog box.

Setting Site Service Level Objectives

Service level objectives (SLOs) are business oriented policies that set limits on maximum response time delays and state minimum concurrent session capacity. WebQoS monitors the objectives. When they are not met, WebQoS uses the corrective actions and relative priorities you have speciﬁed in order to meet the highest priority SLOs. Follow the instructions below.

1. In the main WebQoS window, select the site whose conﬁguration you want to edit from the Services/Systems view.

2. Choose the Edit task icon button on the task bar or the Actions: Edit menu command.

3. Select the SLOs tab from the Add Site Configuration dialog box (Figure 3-18, "Add Site Conﬁguration SLOs Dialog Box").

Chapter 3 65

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-18 Add Site Conﬁguration SLOs Dialog Box

4. Add a service level objective by choosing the [Add]button in the Add Site Configuration SLOs Dialog Box.

Chapter 366

Conﬁguring WebQoS from the Management User Interface

Figure 3-19 Add Service Level Objectives Dialog Box

Conﬁguring HP WebQoS

a. Select the SLO Type from the pull down menu in the Add Service

Level Objectives dialog box (Figure 3-19, "Add Service Level

Objectives Dialog Box"). For speciﬁc information on the SLOs supported by WebQoS and descriptions of Instance and Class parameters, see “Service Level Objectives for Site” on page 158.

b. Enter an appropriate number (based on the SLO type) in the

Number input box. c. Select the Class from the pull down menu if appropriate. d. Enter the appropriate SLO Priority. The SLO priority deﬁnes

the relative priority across SLOs and thresholds to be maintained

for the site. WebQoS performs the corrective actions that are

deﬁned for the highest priority SLO or threshold violated before

taking other corrective actions. When multiple SLOs and

thresholds are violated, the corrective action with the highest

priority is taken. The SLOs are prioritized in ascending order

(from lowest to highest) meaning a priority 1 SLO is higher in

Chapter 3 67

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

priority than a priority 2 SLO. e. Add corrective actions if desired by following the instructions in

the sections that follow. Otherwise choose [OK].

To Specify Corrective Actions for Site SLOs

1. If you would like WebQoS to perform corrective actions when an SLO is violated, choose [Add] in the Add Service Level Objectives dialog box (Figure 3-19, "Add Service Level Objectives Dialog Box").

Figure 3-20 Add Corrective Actions Dialog Box

2. In the Add Corrective actions dialog box (Figure 3-20, "Add Corrective Actions Dialog Box"), select the type of corrective action from the If Violated pull down menu.

3. Enter the appropriate Number if applicable. Number is the number of times a session is redirected for the speciﬁed request class.

4. Select the Class from the pull down menu.

Chapter 368

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

5. Enter a number for the Order in Corrective Actions list. This number determines the order in which the corrective actions are taken. Each corrective action is conﬁgured for a speciﬁc class. If more than one action is conﬁgured for a certain class, the action with the highest priority occurs ﬁrst. Priority is based on the order assigned to the action, with order 1 having the highest priority.

For example, a set of corrective actions can be:

Order 1: Redirect low class sessions 3 times Order 2: Reject low class sessions

A low class session is redirected up to three times. If a session has been redirected three times, it is rejected.

It is recommended that the reject action be conﬁgured as the last action (lowest priority) for the class.

You can change the order of the corrective actions by moving their order using the [Move Up] and [Move Down] buttons in the Add Service Level Objectives dialog box.

Adding Site Threshold Policies

Threshold policies are a category of SLOs. They provide capacity protection for your system and site. Both threshold policies and SLOs are displayed in the service level objectives view on the management user interface.

1. In the main WebQoS window, select the site whose conﬁguration you want to edit from the Services/Systems view.

2. Choose the Edit task icon button on the task bar or the Actions: Edit menu command.

Chapter 3 69

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-21 Edit Site Conﬁguration Threshold Policies Dialog Box

3. Select the Threshold Policies tab from the Add Site Configuration dialog box (Figure 3-21, "Edit Site Conﬁguration

Threshold Policies Dialog Box").

4. Add a threshold by choosing the [Add]button.

Chapter 370

Conﬁguring WebQoS from the Management User Interface

Figure 3-22 Add Thresholds Dialog Box

Conﬁguring HP WebQoS

a. In the Add Thresholds dialog box (Figure 3-22, "Add Thresholds

Dialog Box"), select the Threshold type from the pull down menu. For speciﬁc information on the threshold policies supported by

WebQoS, see “Threshold Policies” on page 159. b. Enter an appropriate percent in the Percent input box. c. Select the Class from the pull down menu, if applicable. d. Enter the appropriate Threshold Priority. The threshold

priority deﬁnes the order in which the thresholds are checked. The

order is compared to both threshold policies and SLO priorities.

The thresholds are prioritized in ascending order (from lowest to

highest) meaning a priority 1 threshold or SLO is higher in

priority than a priority 2 threshold or SLO.

When multiple thresholds and SLOs are violated, the corrective

action with the highest priority is taken. The highest priority

starts at one.

Chapter 3 71

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

5. Toadd corrective actions for threshold policies, go to the next section. Otherwise choose [OK].

To Specify Corrective Actions for Threshold Policies

Corrective actions are those actions taken to bring a threshold policy into compliance. Corrective actions may involve making trade-offs between requests belonging to different classiﬁcations, or making trade-offs between requests going to different sites or services running on the same system. You can add, edit or delete corrective actions by selecting the appropriate button.

1. If you would like WebQoS to perform corrective actions when a threshold policy is violated, choose Add in the Add Threshold dialog box (see Figure 3-22, "Add Thresholds Dialog Box").

Figure 3-23 Add Corrective Actions Dialog Box

2. In the Add Corrective Actions dialog box (Figure 3-23, "Add Corrective Actions Dialog Box"), select the type of corrective action from the If Violated pull down menu.

3. Enter the appropriate Number if applicable. Number is the number of times a session is redirected for the speciﬁed class.

4. Select the Class from the pull down menu.

Chapter 372

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

For example, a set of corrective actions can be:

Order 1: Redirect low class sessions 3 times Order 2: Reject low class sessions

A low class session is redirected up to three times. If a session has been redirected three times, it is rejected.

It is recommended that the reject action be conﬁgured as the last action (lowest priority) for the class.

You can change the order of the corrective actions by moving their order using the [Move Up] and [Move Down] buttons in the Add Service Level Objectives dialog box.

6. To apply your conﬁguration, select [OK] in the Add Corrective Actions dialog box.

Conﬁguring Advanced Features for the Site

Conﬁguring the advanced features is optional, since defaults are supplied.

1. In the main WebQoS window, select the site whose conﬁguration you want to edit from the Services/Systems view.

2. Choose the Edit task icon button on the task bar or the Actions: Edit menu command.

3. Select the Advanced tab from the Edit Site Configuration Advanced dialog box (Figure 3-24, "Edit Site Conﬁguration Advanced Dialog Box").

Chapter 3 73

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Figure 3-24 Edit Site Conﬁguration Advanced Dialog Box

4. Select the feature that you want to conﬁgure. Advanced features are described in the following sections.

Modifying Session Timeouts

A session consists of all requests from a user within a certain time frame. Once a user has been granted a session, all requests from that user are forwarded to the web server, even when new sessions are no longer being accepted due to an SLO or threshold violation. If the session timeouts are exceeded, the current session ends and WebQoS starts a new session unless prevented by a corrective action. There are two types of session timeouts:

• The request interval timeout has a default setting of 15 minutes. The minimum value is 10 seconds. The maximum value is 60 minutes. If the time between requests exceeds the request interval, the session ends and WebQoS starts a new session unless prevented by a corrective action.

If you have enabled URL encoding and conﬁgured the BroadVision system and user names in the /etc/opt/webqos/qos.conf ﬁle, you cannot conﬁgure this session timeout.

• The session duration timeout has a default setting of 2 hours. The

Chapter 374

Conﬁguring WebQoS from the Management User Interface

minimum value is 10 seconds. The maximum value is 100 hours. If a session continues longer than the session duration, the session ends and WebQoS starts a new session unless prevented by a corrective action.

If both timeouts are set, the current session ends if either timeouts are exceeded and WebQoS starts a new session unless prevented by a corrective action.

To change the session timeouts, do the following:

1. Select Session Timeouts ... in the Edit Site Configuration Advanced dialog box (Figure 3-24, "Edit Site Conﬁguration Advanced Dialog Box").

Figure 3-25 Site Advanced Session Timeouts Dialog Box

Conﬁguring HP WebQoS

2. In the Site Advanced Session Timeouts dialog box, you can modify the “Session Timeouts” by clicking the hours, minutes or seconds number and changing it.

3. You can turn off either one of the Session Timeouts but not both. One Session Timeout must always be enabled. Both can be enabled simultaneously.

4. When you have completed your changes, choose [OK].

Assigning Web Server Request Queues

WebQoS assigns requests to queues based on the classiﬁcation of each request. Each request class (high, medium and low) has a separate Request Queue. Depending on the Scheduling Policy selected, requests are removed from the queues in the order speciﬁed and submitted to the web server. The selected policy affects the response times based on the priority of their requests.

Chapter 3 75

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

To assign requests to queues, do the following:

1. Select Web Server Request Queues... from the Edit Site Configuration Advanced dialog box.

Figure 3-26 Site Advanced Web Server Queue Management Dialog Box

2. In the Site Advanced Web Server Queue Management dialog box (Figure 3-26, "Site Advanced Web Server Queue Management Dialog Box"), you can modify the Scheduling Policy by selecting the appropriate policy from the pull down menu.

The scheduling policies supported by WebQoS are:

• Weighted Fairshare - Process entries from the queue based on the

weight assigned to the queue. The higher the weight, the higher the priority of the entry. Default weights are: high priority = 6, medium priority = 3, low priority = 1.

Forexample, if a weight of 6 is assigned to the high priority queue, 3 to the medium, and 1 to the low, then six entries are processed in the high priority queue for every three entries processed in the medium priority queue and every one entry processed in the low priority queue.

• Strict Priority Order - Process all requests in the high priority

queue ﬁrst, process all requests in the medium priority queue next, and ﬁnally process all requests in the low priority queue.

• Fairshare - Process one request from each queue: one from the

high priority queue, one from the medium priority queue, and one from the low priority queue. Then begin again. No priorities are

Chapter 376

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

assigned.

3. Tomodify the maximum queue size allowed in the queue, double-click Queue Size and enter new values. The minimum number of queue requests is 10. The maximum number you set depends on the ﬁle descriptor limit of your system, but it cannot exceed 2,400. Each request in the queue takes up one ﬁle descriptor. To save the new parameters press [Enter].

Increasing these values can greatly affect the performance of WebQoS.

4. If you selected the Weighted Fairshare policy, you can modify the Weight. The weight determines how many requests in a given queue are processed in relation to the number of requests in another queue. The higher the weight, the higher the priority. The maximum weight is 100. The default values are: High 6, Medium 3, Low 1. To save the new parameters press [Enter].

5. When you have completed your changes choose [OK].

Modifying Web Server Accept Threads

WebQoS web server accept threads are those WebQoS threads that accept incoming connections. The number of WebQoS accept threads affects the speed at which WebQoScan process requests and queue these up for the web server.More accept threads could mean faster processing, but might also increase the load on your system.

To modify accept threads, do the following:

1. Select Web Server Accept Threads... from the Edit Site Configuration Advanced dialog box.

Figure 3-27 Site Advanced Accept Threads Dialog Box

2. In the Site Advanced Accept Threads dialog box (Figure 3-27, "Site Advanced Accept Threads Dialog Box"), modify the Number of Web

Chapter 3 77

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

Server Accept Threads by changing the number and selecting [OK]. The default is 5.

3. Choose [OK] to apply your change.

The web server must be restarted if the accept threads value is changed. The value must be greater than zero.

Specifying Site-Wide Corrective Actions

Once you have conﬁgured corrective actions for SLO violations, you may at times want to defer, redirect, or reject corrective actions. Follow the steps in the sections below.

To Defer Site-Wide Corrective Actions

1. Select Corrective Action Policy Details... from the Edit Site Configuration Advanced dialog box.

Figure 3-28 Site Corrective Action Conﬁguration Defer Dialog Box

Chapter 378

Conﬁguring HP WebQoS

Conﬁguring WebQoS from the Management User Interface

2. In the Site Corrective Action Defer dialog box (Figure 3-28, "Site Corrective Action Conﬁguration Defer Dialog Box"), enter the following information: