Configuring application support on non-local monitoring servers

The following sections contain procedures for installing and enabling application support on a monitoring server (hub or remote) that is located on a remote computer. For example, you might need to install application support on a hub monitoring server on z/OS for a monitoring agent running on Windows or a Linux operating system. Or you might want to install application support on a monitoring server or client on a different computer than the one on which you are installing an agent or a portal server. If you are using a z/OS hub and you want to aggregate and prune historical data for any agent, you must transfer the catalog and attribute files for the Summarization and Pruning agent to the hub.

The procedures in this section require that either a Tivoli Enterprise Portal Server or a Tivoli Enterprise Monitoring Server be installed on the Windows, Linux, or UNIX computer and configured to communicate with the monitoring server on the non-local computer.

• Configuring application support on a non-local monitoring server from a Windows system
• Configuring application support on a non-local monitoring server from a Linux or UNIX system

Configuring application support on a non-local monitoring server from a Windows system

This section describes how you can install and enable application support on a non-local monitoring server from your local Windows system. The non-local monitoring server can be a hub or remote monitoring server installed on a Windows, Linux, UNIX, or z/OS computer. A monitoring server or a portal server must be installed on the local computer and application support for the agent or agents must be installed on it.

You add support to a non-local monitoring server by copying the kpp.cat and kpp.atr files for each from the local computer to the non-local computer. If you are adding support to a non-local hub monitoring server, you use Manage Tivoli Monitoring Services to transfer the kpp.sql files for each agent.

Copying the CAT and ATR files to the non-local monitoring server

Copy the .cat and .atr files for the agents you want to support from the local Windows monitoring server to the non-local monitoring server. If you use ftp, copy the files in ASCII format. The .cat and .atr files are located in the following directories on the local monitoring server:

• .cat files are located in <install_dir>\cms\RKDSCATL
• .atr files are located in <install_dir>\cms\ATTRIB

Copy the files to the following directories on the remote computer:

where <install_dir> specifies the IBM Tivoli Monitoring installation directory. The IBM Tivoli Monitoring installation directory is represented by the %CANDLE_HOME% (Windows) or $CANDLEHOME (Linux and UNIX) environment variable. The default installation directory on Windows is /IBM/ITM. The default installation directory on Linux and UNIX is /opt/IBM/ITM.

Adding application support (SQL files) to a non-local hub

If you are adding application support to a non-local hub monitoring server, you must add the SQL files used by the EIB, in addition to the catalog and attribute files. Use the following procedure to seed the hub with SQL files using the Manage Tivoli Enterprise Services utility on your local Windows system:

1. Ensure that the hub monitoring server is started.
2. In the Manage Tivoli Monitoring Services window, select Actions > Advanced > Add TEMS application support.
3. On the Add Application Support to the TEMS window, Select On a different computer and click OK.
4. When you are prompted to ensure that the hub monitoring server is configured and running, click OK.
5. On the Non-Resident TEMS Connection window, provide the hub monitoring server TEMS name (node ID) and select the communication protocol to use in sending the application support SQL files to the hub monitoring server.
6. On the next window, provide any values required by the communication protocol.

   For example, if the protocol is IP.PIPE, you are prompted for the fully qualified TCP/IP host name and port number of the z/OS system where the monitoring server is installed. See for the values you recorded during installation planning.

7. On the Select the Application Support to Add to the TEMS window, select the products for which you want to add application support or click Select All to choose all available products. Click OK.

   The SQL application support files are added to the hub monitoring server. This might take several minutes.

8. The Application Support Addition Complete window gives you information about the status and location of the application support SQL files. Click Save As if you want to save the information in a text file. Click Close to close the window.

   If the Application Support Addition Complete window is not displayed after 20 minutes, look in the IBM\ITM\CNPS\Logs\seedkpp.log files (where pp is the two-character code for each monitoring agent) for diagnostic messages that help you determine the cause of the problem.

9. If the monitoring server is not already stopped, stop it.
10. Restart the monitoring server.

Configuring application support on a non-local monitoring server from a Linux or UNIX system

This section describes how you can install and enable application support on a non-local monitoring server from your local Linux or UNIX system. The non-local monitoring server can be a hub or remote monitoring server installed on a Windows, Linux, or UNIX system.

Before you begin:

• As a prerequisite, you must install a monitoring server, a portal server or a monitoring agent on the local Linux or UNIX computer. This step is necessary to make the Manage Tivoli Monitoring Services available on the local computer. If you do not have a monitoring server, you must install the support files on the local computer using the procedure described in Installing application support files on a computer with no monitoring server.
• Determine which monitoring agents you want to support on the non-local monitoring server. Ensure that the application support files (.cat, .atr, and .sql files) for those agents are available on the local monitoring server:
  • Application support files are located in the following directories on a Linux or UNIX monitoring server:

    Table 52. Locations of application support files on a Linux or UNIX monitoring server

    File type	Directory
    .cat	<install_dir>/tables/cicatrsq/RKDSCATL
    .atr	<install_dir>/tables/cicatrsq/ATTRIB
    .sql	<install_dir>/tables/cicatrsq/SQLLIB

  • The file names of the application support files have the following format:

    kpc.ext

    where pc is the product code for the agent and ext is the file extension.

    For example, kud.sql is the SQL support file for the DB2 monitoring agent. See Appendix D. IBM Tivoli product codes for a list of product codes.

  • If you cannot find application support files for some agents for which you want to install application support, install the missing files on this computer.
    • To install missing support files for base monitoring agents, follow the installation steps described in Installing the monitoring server.
    • To install missing files for non-base monitoring agents, follow the installation steps described in Linux or UNIX: Installing application support on a monitoring server.
    • If no monitoring server is installed on this computer, use the procedure in Installing application support files on a computer with no monitoring server.
• Gather the following information about the monitoring server on the remote computer:
  • The host name or IP address
  • The protocol and port number that was specified when the monitoring server was configured

    The monitoring server on the remote computer must be configured to use the IP.UDP, IP.PIPE, or IP.SPIPE communications protocol. This procedure does not support a monitoring server that was configured to use SNA.

• Verify that the monitoring server on the remote computer is running.
• In these instructions, <install_dir> specifies the IBM Tivoli Monitoring installation directory. You can enter either $CANDLEHOME or the name of the directory. The default installation directory on Linux and UNIX is /opt/IBM/ITM.

Copying the CAT and ATR files to the non-local monitoring server

Copy the .cat and .atr files for the agents you want to support from the local Linux or UNIX monitoring server to the non-local monitoring server. If you use FTP, copy the files in ASCII format. The .cat and .atr files are located in the following directories on the local monitoring server:

• CAT files are located in <install_dir>/tables/cicatrsq/RKDSCATL
• ATR files are located in <install_dir>/tables/cicatrsq/ATTRIB

Copy the files to the directory shown in Table 53 on the remote computer:

where <install_dir> specifies the IBM Tivoli Monitoring installation directory. The IBM Tivoli Monitoring installation directory is represented by the %CANDLE_HOME% (Windows) or $CANDLEHOME (Linux and UNIX) environment variable. The default installation directory on Windows is /IBM/ITM. The default installation directory on Linux and UNIX is /opt/IBM/ITM.

If the non-local monitoring server to which you are adding application support is a hub, you must also install the SQL files used by the EIB. See Adding application support (SQL files) to a non-local hub.

Adding application support (SQL files) to a non-local hub

To add application support SQL files to a hub monitoring server on a non-local system, complete this procedure.

1. Enable the GUI interface.

   Your Linux or UNIX environment might already have a GUI interface enabled. Otherwise, perform the following tasks to enable it:

   1. Enable X11.
   2. Make sure you have access to a native X-term monitor or an X-Window emulator.
   3. If using an X-Window emulator, enable X11 access to the X-Window server (command example: xhost +).
   4. If using an X-Window emulator, set the display environment variable to point to the X-Window server:

      export DISPLAY=pc_ip_address:0

2. Ensure that the hub monitoring server is running.
3. To start Manage Tivoli Monitoring Services, go to the $CANDLEHOME bin directory (example: /opt/IBM/ITM/bin ) and run this command:

   ./itmcmd manage &

   A GUI window opens for Manage Tivoli Monitoring Services.

4. Select Actions > Install product support.
5. On the Add Application Support to the TEMS window, select On a different computer and click OK.
6. When you are prompted to ensure that the hub monitoring server is configured and running, click OK.
7. On the Non-Resident TEMS Connection window, provide the hub monitoring server TEMS name (node ID) and select the communication protocol to use in sending the application support SQL files to the hub monitoring server.
8. Select the appropriate communications protocol and click OK.
9. On the next window, supply any values required by the selected communication protocol and click OK.
10. On the Install Product Support window, select the monitoring agents for which you want to add application support to the hub monitoring server, and click Install.
11. In Manage Tivoli Monitoring Services, look for this message:

    Remote seeding complete!

12. Stop and restart the hub monitoring server.

Installing application support files on a computer with no monitoring server

You can install application support files for a monitoring server on a UNIX or Linux computer where no monitoring server is installed and then use the files to configure support on a non-local monitoring server. Use the following procedure to install application support files on computer on which no monitoring server is installed for use on a monitoring server on another computer:

1. Run the following command from the installation media, either the IBM Tivoli Monitoring base media, the agent product CD for distributed agent products or the data files CD for z/OS agent products:

   ./install.sh

2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default (/opt/IBM/ITM) or enter the full path to the installation directory you used.

   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:

3. Type 3 and press Enter.

   The software license agreement is displayed.

4. Read through the software license agreement, then type 1 and press Enter to accept the agreement.

   The installer presents a list of currently installed products, the operating systems for which product packages are available, and component support categories.

5. Type the 32-character encryption key to use and press Enter, or just press enter to use the default. This key must be the same key as that used during the installation of the portal server to which the client will connect.

   The installer presents a list of products for which support packages are available.

6. Enter the numbers of the monitoring agents that you want to install or enter the number that corresponds to All of the above. Enter more than one number on the same line separated by spaces or commas (,).

   A list of the monitoring agents to be installed is displayed.

7. Confirm the selection by pressing Enter.

   The installer asks if you want to install additional products or support packages.

8. Type 2 and press Enter.

   The support packages are installed. When installation is complete, you will see the message

   ... finished postprocessing.
   Installation step complete.

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