Linux® or UNIX: Installing the hub monitoring server

Use the following steps to install and configure the hub monitoring server on a Linux or UNIX® computer.

Installing the monitoring server

Use the following steps to install the monitoring server on a Linux or UNIX computer:

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). If you want to use a different installation directory, type the full path to that directory and press Enter.
3. If the directory you specified does not exist, you are asked whether to create it. Type 1 to create this directory.
4. The following prompt 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) Install TEMS support for remote seeding
   4) Exit install.
   Please enter a valid number:

   Type 1 to start the installation and press Enter.

   The end user license agreement is displayed. Press Enter to read through the agreement.

5. Type 1 to accept the agreement and press Enter.
6. Type a 32-character encryption key and press Enter. If you want to use the default key, press Enter without typing any characters.
   Notes:
   1. Do not use any of the following characters in your key:
      • =
      • '
      • |
   2. Ensure that you document the value you use for the key. Use this key during the installation of any components that communicate with this monitoring server.

   A numbered list of available operating systems is displayed.

7. Type the number for the operating system on which you are installing the monitoring server. The default value is your current operating system. Press Enter.
8. Type 1 to confirm the operating system and press Enter.

   A numbered list of available components is displayed.

9. Type the number that corresponds to the Tivoli Enterprise Monitoring Server option. Press Enter.

   A list of the components to install is displayed.

10. Type 1 to confirm the installation.

    The installation begins.

11. When prompted, type a name for your monitoring server. For example: HUB_hostname. Do not use the fully qualified host name. Press Enter.
12. After all of the components are installed, you are asked whether you want to install components for a different operating system. Type 2 and press Enter.

Installation is complete. The next step is to configure your monitoring server.

Configuring the hub monitoring server

Use the following steps to configure the hub monitoring server:

1. At the command line, change to the /opt/IBM/ITM/bin directory (or the directory where you installed IBM Tivoli Monitoring).
2. Run the following command:

   ./itmcmd config -S -t tems_name

   where tems_name is the name of your monitoring server (for example, HUB_itmdev17).
3. Press Enter to indicate that this is a hub monitoring server (indicated by the *LOCAL default).
4. Press Enter to accept the default host name for the monitoring server. This should be the host name for your computer. If it is not, type the correct host name and then press Enter.
5. Enter the type of protocol to use for communication with the monitoring server. You have four choices: ip, ip.pipe, ip.spipe, or sna. Press Enter to use the default communications protocol (IP.PIPE).
6. If you want to set up a backup protocol, enter that protocol and press Enter. If you do not want to use backup protocol, press Enter without specifying a protocol.
7. Depending on the type of protocol you specified, provide the following information when prompted:

   Table 32. UNIX monitoring server protocols and values

   Protocol	Value	Definition
   IP.UDP	IP Port Number	The port number for the monitoring server. The default is 1918.
   SNA	Net Name	The SNA network identifier for your location.
   	LU Name	The LU name for the monitoring server. This LU name corresponds to the Local LU Alias in your SNA communications software.
   	Log Mode	The name of the LU6.2 LOGMODE. The default value is "CANCTDCS."
   IP.PIPE	IP.PIPE Port Number	The port number for the monitoring server. The default is 1918.
   IP.SPIPE	IP.SPIPE Port Number	The port number for the monitoring server. The default is 3660.

8. Press Enter to not specify the name of the KDC_PARTITION. You can configure the partition file at a later time, as described in Appendix C. Firewalls.
9. Press Enter when prompted for the path and name of the KDC_PARTITION.
10. If you want to use Configuration Auditing, press Enter. If you do not want to use this feature, type 2 and press Enter.
11. Press Enter to accept the default setting for the Hot Standby feature (none).

    For best results, wait until after you have fully deployed your environment to configure the Hot Standby feature for your monitoring server. See Configuring failover support for information about configuring Hot Standby.

12. Press Enter to accept the default for the Optional Primary Network Name (none).
13. Press Enter for the default Security: Validate User setting (NO).
    Important:
    Do not change this to set Security: Validate User. You can configure security after configuring the monitoring server, as described in Configuring user authentication.
14. If you want to forward situation events to either IBM Tivoli Enterprise Console (TEC) or the IBM Tivoli Netcool/OMNIbus console, type 1 and press Enter to enable the Tivoli Event Integration Facility. Complete the following additional steps:
    1. For EIF Server, type the hostname of the TEC event server or the hostname of the Netcool/OMNIbus EIF probe and press Enter.
    2. For EIF Port, type the EIF reception port number for the TEC event server or the Netcool/OMNIbus EIF probe and press Enter.
15. To disable Workflow Policy Activity event forwarding, type 1 and press Enter. Otherwise, press Enter to accept the default (2=NO). See the note in Event integration with Tivoli Enterprise Console for more information.
16. Type 5 to accept the default SOAP configuration and exit the configuration.
    Note:
    You can configure any SOAP information at a later time. See Configuring IBM Tivoli Monitoring Web Services (SOAP Server) for information.

The monitoring server is now configured.

A configuration file is generated in the install_dir/config directory with the format host_name_ms_tems_name.config (for example, itmdev17_ms_HUBitmdev17.config).

Adding application support to the hub monitoring server

All monitoring agents require that application support files be installed on the monitoring servers (hub and remote), portal server, and portal desktop clients in your environment. Application support files contain the information required for agent-specific workspaces, helps, predefined situations, and other data.

When you installed the monitoring server on Linux or UNIX, following the instructions in Installing the monitoring server, the application support files for all base monitoring agents and other supported agents were automatically installed on the monitoring server. (The base monitoring agents are the monitoring agents included on the IBM Tivoli Monitoring installation media. Now you must enable the application support for those agents. The process of enabling application support is also referred to as activating or adding application support, and in the case of the monitoring server, as seeding the monitoring server.

Follow the instructions in this section to add application support for agents to a monitoring server on Linux or UNIX. For detailed information about application support, and for instructions to install and enable application support for non-base agents, refer to Installing and enabling application support and Configuring application support for non-Base monitoring agents.

Use one of the following procedures to add application support for Base monitoring agents to a monitoring server:

Command-line procedure

Complete the following steps to enable application support on the monitoring server for base monitoring agents, using the Linux or UNIX command line:

1. Start the monitoring server by running the following command:

   ./itmcmd server start tems_name

2. Run the following command to add the application support:

   ./itmcmd support -t tems_name pc pc pc

   where tems_name is the name of the monitoring server (for example, HUB_itmserv16) and pc is the product code for each agent for which you want to enable application support.

   To view the product codes for the applications installed on this computer, run the following command:

   ./cinfo

   Type 1 when prompted to display the product codes for the components installed on this computer.

   See your product documentation for the product code for other agents.
3. Stop the monitoring server by running the following command:

   ./itmcmd server stop tems_name

4. Restart the monitoring server by running the following command:

   ./itmcmd server start tems_name

GUI procedure

This section describes how to use the Manage Tivoli Enterprise Services window on a Linux Intel or UNIX computer to enable application support on a monitoring server that is located on the local computer. You can use this procedure as an alternative to the itmcmd support command. (This command applies only to monitoring servers that are installed on the local computer. To enable application support on a monitoring server that is located on a remote computer, see Configuring application support on a non-local monitoring server from a Linux or UNIX system.)

This procedure assumes that you have installed the support files on this computer, and that X Windows is enabled on this computer.

Complete the following steps to enable application support from the Manage Tivoli Enterprise Services window on the local Linux or UNIX monitoring server:

1. Log on to the computer where the Tivoli Enterprise Portal Server is installed.
2. Start the Manage Tivoli Enterprise™ Monitoring Services utility:
   1. Change to the bin directory:

      cd install_dir/bin

   2. Run the following command using the parameters described in Table 33:

      ./itmcmd manage [-h ITMinstall_dir] 

      where:

      Table 33. Parameters for the itmcmd manage command

      -h	(optional) An option used to specify the installation directory.
      ITMinstall_dir	The directory where the monitoring server is installed. The default installation directory is /opt/IBM/ITM.

   The Manage Tivoli Enterprise Monitoring Services window is displayed.

3. Start the monitoring server if it is not already started: Right-click Tivoli Enterprise Monitoring Server and click Start.
4. Right-click Tivoli Enterprise Monitoring Server and select one of the following options:
   • To enable all application support packages installed on this computer, click Quick (all available support).
   • To select which application support packages you want to enable, click Advanced . . .
5. If you selected the Advanced option, the Install Product Support windows is displayed. Select the application support packages you want to install and click Install.
6. Stop and restart the monitoring server:
   1. Right-click Tivoli Enterprise Monitoring Server and click Stop.
   2. Right-click Tivoli Enterprise Monitoring Server and click Start.

[ Top of Page | Previous Page | Next Page | Contents | Index ]