IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install monitoring agents

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Windows: Installing a monitoring agent

Use the following steps to install a distributed monitoring agent on a Windows computer.

  1. If you are installing on either an x86-32 CPU or an x86-64 CPU, launch the installation wizard by double-clicking the setup.exe file in the \WINDOWS subdirectory on the installation media. However, if you are installing on an Itanium CPU, launch the wizard by double-clicking on the setup.exe file in the \WIA64 directory.

    Use either the IBM Tivoli Monitoring Agent DVD or a distributed agent product CD for Windows. Do not use a Data Files for z/OS CD.

  2. Click Next on the Welcome window.

    If you have another IBM Tivoli Monitoring component already installed on this computer, select Modify on the Welcome window to indicate that you are updating an existing installation. Click OK on the message telling you about preselected items. Then skip to Step 6.

  3. Read and accept the software license agreement by clicking Accept.

  4. Choose the directory where you want to install the product. Click Next.

    1. This step applies only to those agents that you install from the IBM Tivoli Monitoring installation image. Agents installed from the agent installation image do not have this step. If you are installing an agent from an agent installation image, skip to step 6.

    2. If you specify an incorrect directory name, you will receive the following error:

      The IBM Tivoli Monitoring installation directory cannot exceed 80 characters
      or contain non-ASCII, special or double-byte characters.
      The directory name can contain only these characters:
      "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ _\:0123456789()~-./".

  5. Type a 32-character encryption key. This key must be the same as the key that was used during the installation of the monitoring server to which this monitoring agent connects.

    Click Next and then click OK to confirm the encryption key.

  6. On the Select Features window, expand Tivoli Enterprise Monitoring Agents.

  7. Select the names of the agents that you want to install and click Next.

    1. Agents available on the IBM Tivoli Monitoring installation image include the Warehouse Proxy Agent and the Summarization and Pruning Agent. Before you install these agents, follow the instructions later in this book for setting up a Tivoli Data Warehouse solution, beginning with Tivoli Data Warehouse solutions.

    2. If both of these conditions are met:

      • The components you selected for installation would result in a mixed 32-bit and 64-bit environment.

      • No Agent Compatibility Package (see Install the Agent Compatibility (AC) component) can be found on the installation DVD, or the package found is not at the appropriate level.

      then this error message is displayed:

        The Agent Compatibility Package in version ver_num is required but unavailable.

  8. If a monitoring server is not installed on this computer, go to Step 9.

    If you are installing monitoring agents on a computer that already has a monitoring server installed, the Agent Deployment window is displayed.

    The Agent Deployment window lists monitoring agents on this installation image that you can add to the agent depot. The agent depot contains agents that you can deploy to remote computers. For information about how to deploy agents in the agent depot to remote computers, see Deploy monitoring agents across your environment.

    By default, the agent depot is located in the itm_installdir\CMS\depot directory on Windows. To use a different directory, create the directory (if it does not exist), and specify the directory using the DEPOTHOME key in the KBBENV file.

    Select the agents, if any, that you want to add to the agent depot. (You can add agents to the agent depot at a later time by updating your installation.) IBM strongly recommends you also add the agent compatibility (AC) package at this time. Click Next.

  9. This step applies only to agents that you install from the IBM Tivoli Monitoring installation image. If you are installing agents from an agent product installation image, go to Step 10.

    If no IBM Tivoli Monitoring component has been previously installed on this computer, a window is displayed for you to select a program folder for the Windows Start menu. Select a program folder and click Next. The default program folder name is IBM Tivoli Monitoring.

  10. Review the installation summary details. The summary identifies what you are installing and where you chose to install it. Click Next to start the installation.

    After installation is complete, a configuration window (called the Setup Type window) is displayed.

  11. Clear the check boxes for any components that are already installed and configured (at the current release level) on this computer, unless you want to modify the configuration. (For example, clear the check box for the Tivoli Enterprise Monitoring Server if it has already been installed and configured on this computer.) Click Next to start configuring all selected components.

  12. Define the communications between the monitoring agents and the monitoring server:

    1. If the agents must cross a firewall to access the monitoring server, select Connection must pass through firewall.

    2. Identify the type of protocol that the agents use to communicate with the monitoring server.

      You have seven choices: IP.UDP, IP6.UDP, IP.PIPE, IP6.PIPE, IP.SPIPE, IP6.SPIPE, or SNA. You can specify up to six methods for communication. If the method you identify as Protocol 1 fails, Protocol 2 is used as a backup. If Protocol 2 fails, Protocol 3 is used as a backup, and so on. When you configure the protocol for the Warehouse Proxy Agent, configure the same protocols used by the application agents and by the hub monitoring. If the proxy agent does not have the same protocol as the hub monitoring server, it cannot register with the hub. If the proxy does not have the same protocol as the application agents, then the application agents cannot communicate with the proxy when they to create a route to it.

      Do not select Optional Secondary TEMS Connection. You can set up the failover support for agents after installation, as described in the IBM Tivoli Monitoring High Availability Guide for Distributed Systems.

    3. Click OK. A second configuration window is displayed.

    4. Complete the fields shown in the following tableTable 1 for the protocol that you specified.


      Communications protocol settings

      Field Description
      IP.UDP and IP6.UDP settings
      Hostname or IP Address The host name or IP address for the hub monitoring server.
      Port # or Port Pools The listening port for the hub monitoring server. The default number is 1918.
      IP.PIPE and IP6.PIPE settings
      Hostname or IP Address The host name or IP address for the hub monitoring server.
      Port Number The listening port for the monitoring server. The default number is 1918.
      IP.SPIPE and IP6.SPIPE settings
      Hostname or IP Address The host name or IP address for the hub monitoring server.
      Port number The listening port for the hub monitoring server. The default value is 3660.
      SNA Settings
      Network Name SNA network identifier for your location.
      LU Name LU name for the monitoring server. This LU name corresponds to the Local LU Alias in your SNA communications software.
      LU 6.2 LOGMODE Name of the LU6.2 LOGMODE. The default value is "CANCTDCS."
      TP Name The transaction program name for the monitoring server.
      Local LU Alias LU alias.

    5. Click OK to exit the Configuration Defaults for Connecting to a TEMS window.

    For additional information about these parameters, press the Help button.

  13. Click Finish to complete the installation.

  14. Click Finish on the Maintenance Complete window if you are updating an existing installation.

  15. Open the Manage Tivoli Enterprise Monitoring Services utility (if it does not open automatically) to see if the monitoring agents that you installed have been configured and started. If Yes is displayed in the Configured column, the agent has been configured and started during the installation process.

  16. If the value in the Configured column is blank and Template is displayed in the Task/Subsystem column, right-click the Template agent and complete the following steps:

    1. Click Configure Using Defaults.

    2. Complete any windows requiring information using the agent-specific configuration settings in the user's guide for your agent

      Do not type non-ASCII characters on any of these windows. Typing characters from other character sets has unpredictable results.

    3. Repeat this step as necessary to create monitoring agent instances for each application instance you want to monitor.


Parent topic:

Install monitoring agents

+

Search Tips   |   Advanced Search