Running the IBM HTTP Server monitoring extension
Configuring the IBM HTTP Server for monitoring
- Open the httpd.conf file in a text editor.
- Uncomment the line:
- Windows: LoadModule status_module modules/ApacheModuleStatus.dll
- UNIX: LoadModule status_module libexec/mod_status.so
- Do one of the following:
- Uncomment the line ExtendedStatus On
- If the line ExtendedStatus On is not present, add it after the LoadModule section (or anywhere in the file)
- Uncomment the Location elements change the settings as shown:
<Location /server-status>
SetHandler server-status
Order allow, deny
Allow from hostname.host.com
Allow from hostname.host.com
</Location> - Save and close the file.
- Restart the HTTP Server.
- Repeat this process for each HTTP Server you are monitoring.
Controlling the IBM HTTP Server monitoring extension on Windows or UNIX
The HTTP Server monitoring extension runs as a Java process. If you want to work directly with the process on UNIX, use the ps command to find the active Java processes. For Windows, use the Task Manager.
- Open a command prompt and change to the directory containing the distributed files.
- Enter the monitoring extension command qphttp (Windows) qphttp.sh (UNIX) followed by the required command parameter.
To list all available command parameters, enter:
For Windows: qphttp --help
For UNIX: ./qphttp.sh --help
For Linux: ./qphttpl.sh --help
For example, in Windows qphttp --start starts the monitoring extension; in UNIX ./qphttp.sh --start starts the monitoring extension.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*