Running the IBM HTTP Server monitoring extension

The HTTP Server monitoring extension monitors and reports activity from IBM HTTP Server for WebSphere Application Server. The information is then passed to the MVMM  Extensible Agent. Each monitoring extension monitors one HTTP Server.

The monitoring extension files are contained in an archive file that must be extracted into the MVMM  Extensible Agent directory.

For information on installing this extension on the various supported platforms, see Installing-the-IBM-HTTP-Server-monitoring-extension.

When the HTTP Server monitoring extension is running, MainView Middleware Monitor displays HTTP Server performance data in the Monitor Console. The following are the types of information collected by the monitoring extension:

  • busyServers - number of servers running.
  • bytesPerRec - number of bytes to a request.
  • bytesPerSec - number of bytes sent in a second.
  • HostStatus - is the monitored HTTP Server running.
  • idleServers - number of servers not running.
  • requestsPerSec - number of requests received in a second.
  • totalAccesses - total number of times the HTTP Server has been accessed.
  • totalKBytes - total number of kilobytes transferred.
  • uptime - length of time the HTTP Server has been running.

IBM offers two HTTP Server products. One HTTP Server product is provided with the z/OS base operating system, and the other is provided with WebSphere Application Server. The qphttp monitor works with the HTTP Server that is provided with WebSphere Application Server.

If you have not already distributed your MVMM  Extensible Agent and monitoring extension files, then do so now. See Using-Deployments-to-distribute-the-agent-and-extensions-packages.

This section includes:

 

Related topics

Running-performance-and-availability-monitoring-extensions

Agent-and-Extension-Preferences

Configuring the IBM HTTP Server for monitoring

  1. Open the httpd.conf file in a text editor.
  2. Uncomment the line:
    • Windows: LoadModule status_module modules/ApacheModuleStatus.dll

    • UNIX:
      LoadModule status_module 

      libexec/mod_status.so

      or

      LoadModule status_module modules/mod_status.so

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

For Http server version 9.0 and up use following example:
<IfModule mod_status.c>
<Location /server-status>
SetHandler server-status
Require ip hostname.host.com
</Location>

where hostname.host.com is the IP where the extension is running.

  1. Save and close the file.
  2. Restart the HTTP Server.
  3. Repeat this process for each HTTP Server you are monitoring.

Note

Local HTTP Server monitoring with the HTTP Server monitoring extension is not the only configuration option. You can remotely monitor a supported HTTP Server with the HTTP Server monitoring extension. Contact BMC Support for details.

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.

  1. Open a command prompt and change to the directory containing the distributed files.
  2. 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.

  3. On unix only , run the setqphttp script, for setting the environment :

    ./setqphttp.sh

  4. Run the Configuration Utility to configure the monitored Http server:

    server:
    For Unix : Run the qphttp.sh -–config , than type
    insert host-name-of-HttpServer port-number-of-HttpsServer
    For Windows: run qphttp.bat, than type
    insert host-name-of-HttpServer port-number-of-HttpsServer

  5. Start the qphttp extension by running the following commands:
    For Windows: qphttp.bat --start
    For UNIX: ./qphttp.sh --start

Note

The kill -9 command. (UNIX only) If you use the kill -9 command to stop the IBM HTTP Server monitoring extension, remove the .lock files (qpea.lock and qpwas.lock).

If the MVMM Extensible Agent or monitoring extension did not shut down gracefully, remove the .lock files (qpea.lock, and qpwasmon.lock) before starting it again. The lock file prevents multiple processes from running at the same time.

BEFORE STARTING: Change to the agent installation directory and enter qpea --status to check if the MVMM Extensible Agent is running. If it is not running, enter qpea --start

When starting the monitoring extension, if you have not installed the monitoring extension as a Windows service, enter qphttp --console to start the monitoring extension in the foreground. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*