Installing a monitoring agent on Linux or UNIX computers

Before you begin

Keep the following guidelines in mind:
  • You must install and run Web Response Time agents as a root user. If you are not logged in as root:
    • You cannot install or run Web Response Time. If you install the Web Response Time agent and attempt to start the kfcm120 process as a non-root user, the process will fail because it cannot open the NIC. Root is required to access the Network Interface.
    • You must have write-access to the following:
      • CANDLE_HOME or the installation directory
      • TEMP directory for the system
      • JLOG directory for the Tivoli Enterprise Management Agent, typically /var/ibm/tivoli/common/BWM/logs/
    • Do not install two monitoring agents in the same CANDLE_HOME or installation directory using different user IDs. You can install two agents in the same CANDLE_HOME or installation direction if you use the same user ID for the installations.
  • You can install more than one Web Response Time agent on the same UNIX or Linux host, as long as the agents are installed in different file systems (for example, /opt/IBM/ITM and /var/IBM/ITM2). Some configuration customization is also required. For more information about installing agents, see Installing multiple Web Response Time agents on the same Linux or UNIX host.
  • If you have a previously installed Response Time Tracking, version 6.1, you must uninstall it and verify that the following dll files were deleted before installing Robotic Response Time.
    • /usr/lib/libarm4.*
    • /usr/lib/libarmjni4.*
    • /usr/lib/libarmjni.*
    • /usr/lib/libarm32.*
    • /usr/lib/libarmcli.*
  • If you want to record and play back Rational Performance Tester test scripts on Robotic Response Time, install Rational Performance Tester software. For more information, see Installing Rational products.
  • If your environment has installed a GSKit version newer than 7.0.3.18, the installation fails. Uninstall the GSKit and try installing the agent again.
  • For Web Response Time V7.3.0.0 and later installed on AIX 6.1 and later, add the following statement to the kfcmenv file in $CANDLE_HOME/tmaitm6/wrm to stop the kfcm120 process from continuously restarting:
    MALLOCOPTIONS=pool,multiheap:8,no_mallinfo; export MALLOCOPTIONS 

The following table provides an overview of what you need to for installation:

Table 1. Overview of installing a monitoring agent on Linux or UNIX computers
Steps Where to find information
Install the monitoring agent. Procedure: Installing the agent
Configure the monitoring agent.

Configuring Application Management Console from the GUI (UNIX and Linux)

Configuring Robotic Response Time from the GUI (UNIX and Linux)

Configuring Web Response Time from the GUI (UNIX and Linux)

Some agents require additional, agent-specific configuration parameters. See the agent documentation for the specific agents that you are configuring.

Start the monitoring agent. Starting and stopping monitoring agents

Procedure: Installing the agent

  1. In the directory where you extracted the installation files, run the following command: ./install.sh.
  2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default (/opt/IBM/ITM) or type the full path to a different directory.
  3. You are given a list of processes currently running. You are warned that these processes will be stopped and restarted during the installation. Type 1 and press Enter to continue the installation.
    A prompt similar to the following is displayed:
    Select one of the following: 
    1) Install products to the local host. 
    2) Install products to depot for remote deployment (requires TEMS).
    3) Exit install. 
    
    Please enter a valid number:
  4. Type 1 to start the installation and press Enter.
  5. Type the number that corresponds to the language in which you want to display the software license agreement in and press Enter. (In some cases, you might not be prompted for this step. so you can skip it.)
  6. Press Enter to display the agreement.
  7. Type 1 to accept the agreement and press Enter.
  8. (Optional) If installing from the IBM Tivoli Monitoring installation image, type a 32-character encryption key and press Enter. This key was specified during the installation of the monitoring server to which this monitoring agent connects.
  9. Type the number for the operating system on which you are installing and press Enter. The default value is your current operating system.
  10. Type 1 to validate your selection and press Enter.
  11. A list of available products for installation is provided. Type the number that corresponds to the monitoring agent or agents that you want to install and press Enter. To install more than one agent, use a comma (,) or a space to separate the numbers for each agent.
  12. Type 1 to validate your selection and press Enter to start the installation.
  13. When prompted to install additional products or product support packages, type 2 for no and press Enter.

Installing multiple Web Response Time agents on the same Linux or UNIX host

On supported Linux and UNIX systems, multiple Web Response Time agents can run on the same system, as long as the agents are installed in different file systems (for example, /opt/IBM/ITM and /var/IBM/ITM2). Some configuration customization is also required.

Complete the following steps to achieve this setup:
  1. Install multiple instances of the Web Response Time agent in different file systems. These path names must not be subsets of each other. For example, for an installation deploying two Web Response Time agents on the same box:
    • Correct:
      /opt/IBM/ITM
      /var/IBM/ITM2
    • Incorrect:
      /opt/candle
      /opt/candle/itcam_wrt/ServPoint
  2. In the CANDLE_HOME/tmaitm6/wrm directory, add the following line to the kfcmenv file for each Web Response Time agent, where port is an open port for the machine:
    KFC_API_MEDIASERVER_LISTEN_PORT=port;
    export KFC_API_MEDIASERVER_LISTEN_PORT

    Use port 12121 for the first agent, port 12122 for the second agent, port 12123 for the third agent, and so on.

  3. In CANDLE_HOME/config, add this same line to the t5.ini and t5.config files for each Web Response Time agent.
  4. In CANDLE_HOME/config, add the following line to the t5.config and t5.ini files for each Web Response Time agent. In CANDLE_HOME/tmaitm6/wrm, add the following line to the kfcmenv file for each Web Response Time agent, where port is an open port on the system:
    KT5ERRORMESSAGEPORT=port

    Ensure that the port is unique for each agent.

  5. In CANDLE_HOME/config, set the CTIRA_HOST variable in the t5.config and t5.ini files for each Web Response Time agent to define the node name that the Tivoli Enterprise Portal uses to identify each agent.
Avoid monitoring identical data: To avoid having each agent monitoring identical data, you must satisfy either of the following conditions:
  • Each agent monitors a different NIC.
  • In the CANDLE_HOME/tmaitm6/wrm/kfcmenv file for each Web Response Time agent, use the following option to define which servers each Web Response Time agent monitors:
    KFC_RESTRICT_HOST=ip1:port1,ip2:port2,...