Installing the IBM HTTP Server monitoring extension

This section describes how to install the IBM HTTP Server monitoring extension on various platforms, and includes:

Installing the IBM HTTP Server monitoring extension on Windows

Before you begin

See Supported middleware monitoring technologies for performance and availability to verify the intended monitored technology is supported and that all footnote prerequisites are satisfied.

To install the IBM HTTP Server monitoring extension on Windows

1. At a command prompt, change to the directory where the TMTM Agents and Extensions are installed.
2. Unzip the contents of the pkg_*_qphttp.zip package, as appropriate for your platform, to a sub-directory of the TMTM Agents and Extensions (e.g. into a directory named qphttp).
3. If you are not using the provided Java Runtime Environment (JRE), verify that JAVA_HOME is set in your environment. Do not edit qphttp.bat to achieve this, because the file might be replaced during a reinstall or upgrade.
4. If you are reinstalling or upgrading TMTM Extensible Agents, restore your backup copy of the eaa.xml file.
5. To ensure that the TMTM Extensible Agent is running, enter qpea --status. If it is not running, enter qpea --start.
6. To install the HTTP Server monitoring extension as a Windows service, change to the directory where you extracted the HTTP Server TMTM Extensible Agent files and enter qphttp --install
7. To configure the HTTP Server monitoring extension, enter qphttp --config. The configuration program checks if any HTTP Server monitoring extensions already exist and are configured. If one does exist and is configured, its configuration settings are available through the query command. The configuration program runs until you enter exit.
8. From the HTTP Server monitoring extension's configuration prompt, enter one of the following:
   • insert host port to create a new configuration. If the HTTP Server monitoring extension is already configured and you attempt to use the insert command, the command fails and information about the monitored instance appears. You must use the update command.
   • update host port to update or change the existing configuration. You cannot change the host name with the update command. If you want to change the host name, delete the existing instance and insert the new one.
     
     where:
     host is an alpha-numeric character string of the HTTP Server monitor host name. This must be a valid host that already exists on the network.
     port is the port number of the HTTP Server. The default is 80. Connections to HTTPS on port 443 are not supported by the extension.
     
     
9. Enter exit to leave the HTTP Server monitoring extension configuration program.
10. To start the HTTP Server monitoring extension, change to the directory that contains the file qphttp.bat and enter qphttp --start.
11. (Optional) Set the sample interval by opening framework.props in a text editor and modify the line:
    
    com.bmc.mmpa.eaapi.framework.waitstate.SampleInterval=60
    
    This sets the sample interval to 60 seconds, the default.
    
    
12. (Optional) Set the logging level by opening and modifying the file qplog.props. The options are info, debug, and warn. Info and warn can be used every day, but debug contains a large amount of data and might not be useful for continual logging.
13. (Optional) Using the Windows Service Manager, configure the HTTP Server monitoring extension to start automatically when the computer is restarted.

Where to go from here

• To control and configure the extension, see Running the IBM HTTP Server monitoring extension.

• To define an alternative JRE, see Defining alternative JREs for Java extensions.
• To view uninstall instructions, see Uninstalling the HTTP Server monitoring extension.

Installing the IBM HTTP Server monitoring extension on UNIX

Before you begin

See Supported middleware monitoring technologies for performance and availability to verify the intended monitored technology is supported and that all footnote prerequisites are satisfied.

To install the IBM HTTP Server monitoring extension on UNIX

1. At a command prompt, change to the directory where the TMTM Agents and Extensions are installed.
2. Unzip the contents of pkg_*_qphttp.zip, as appropriate for your platform, to a sub-directory of the TMTM Agents and Extensions (e.g. into a directory named *qphttp).
3. If you are not using the provided Java Runtime Environment (JRE), verify that JAVA_HOME is set in your environment. Do not edit qphttp.bat to achieve this, because the file might be replaced during a reinstall or upgrade.
4. Change to the directory to where you extracted the HTTP Server TMTM Extensible Agent files.
5. (UNIX only) Use chmod +x filename to make the following files executable:
   • qphttp.sh (or qphttpl.sh for Linux)
   • setqphttp.sh. This file should be executed from the current shell using the dot operator (.). If the file is not executed from the current shell, then the variables are set only within the sub-shell in which it runs and not in the current shell. Additionally, you might want to add this script to your .profile file so that it runs and sets the variables when you log on.
   • Depending on your monitoring needs other files might need to be executable. The binary files and the *.ksh files for your operating system should be executable.
6. If you are reinstalling or upgrading TMTM Extensible Agents, restore your backup copy of the eaa.xml file.
7. To set the class path variable for the HTTP Server monitoring extension, enter:
   
   . setqphttp.sh


8. To ensure that the TMTM Extensible Agent is running, enter qpea --status. If it is not running, enter qpea --start.
9. To configure the HTTP Server monitoring extension, enter qphttp.sh --config. The configuration program checks if any HTTP Server monitoring extensions already exist and are configured. If one does exist and is configured, its configuration settings are available through the query command. The configuration program runs until you enter exit.
10. From the HTTP Server monitoring extension's configuration prompt, enter one of the following:
    • insert host port to create a new configuration. If the HTTP Server monitoring extension is already configured and you attempt to use the insert command, the command fails and information about the monitored instance appears. You must use the update command.
    • update host port to update or change the existing configuration. You cannot change the host name with the update command. If you want to change the host name, delete the existing instance and insert the new one.
      
      where:
      host is an alpha-numeric character string of the HTTP Server monitor host name. This must be a valid host that already exists on the network.
      port is the port number of the HTTP Server. The default is 80.
      
      
11. Enter exit to leave the HTTP Server monitoring extension configuration program.
12. To start the HTTP Server monitoring extension, change to the directory that contains the file qphttp.sh and enter qphttp.sh --start.
13. (Optional) Set the sample interval by opening framework.props in a text editor and modify the line:
    
    com.bmc.mmpa.eaapi.framework.waitstate.SampleInterval=60
    
    This sets the sample interval to 60 seconds, the default.
    
    
14. (Optional) Set the logging level by opening and modifying the file qplog.props. The options are info, debug, and warn. Info and warn can be used every day, but debug contains a large amount of data and might not be useful for continual logging.
15. (Optional) Using cron or the /etc/rc.d/init.d directory, configure the HTTP Server monitoring extension to start automatically when the computer is restarted.

Where to go from here

• To control and configure the extension, see Running the IBM HTTP Server monitoring extension.

• To define an alternative JRE, see Defining alternative JREs for Java extensions.
• To view uninstall instructions, see Uninstalling the HTTP Server monitoring extension.