HP WebQoS Peak for HP-UX Concepts and Operation Guide

44 Chapter4
HP WebQoS Peak for the Zeus Web Server
Configuring HP WebQoS for Zeus
You can also use the /opt/webqospk/setup script which prompts you
for the type of web server (Netscape or Zeus) you want to remove.
Example
The following is an example of removing HP WebQoS from one of two
virtual servers configured on the system (remove HP WebQoS from
server2; keep HP WebQoS installed on server1). The web server is
installed in the default /usr/local/zeus directory. User input is in
bold.
#cd /opt/webqospk
#setup.zeus -r
Root pathname of Zeus server (/usr/local/zeus):
Remove AdmissionController from server server1 (y or n): n
Remove AdmissionController from server server2 (y or n): y
Uninstall HP WebQOS Peak for server server2 at
/usr/local/zeus/ns-config/https-server2
Done.
#
Other Configuration Considerations
This section covers tasks beyond basic configuration.
Tuning Your Web Server’s Cache
To control session admissions, HP WebQoS tracks the session state by
including cookies in HTTP responses. For HP WebQoS to operate
effectively, the server cannot generate all of its responses from the cache.
This may cause the performance of the web server to be slow.
However, you can tune the cache by configuring the
$ZEUSHOME /ns-config/https- server_name /config/hpac/config.ac file to
allow specified mime types to be cached or not cached.
For example, if you serve HTTP pages with embedded images, you can
cache the images by adding the following lines to the configuration file:
mime.cache
mime.type image/gif
mime.type image/jpeg
Or, if your pages are generated by an application such as an NSAPI