IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install and enable application support > Configure application support on nonlocal monitoring servers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configure application support on a nonlocal monitoring server from a Linux or UNIX system
This section describes how you can install and enable application support on a nonlocal monitoring server from your local Linux or UNIX system. The nonlocal monitoring server can be a hub or remote monitoring server installed on a Windows, Linux, or UNIX system.
Before you begin:
- As a prerequisite, 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 Enterprise Monitoring Services available on the local computer. If you do not have a monitoring server, install the support files on the local computer using the procedure described in Install application support files on a computer with no monitoring server.
- Determine which monitoring agents you want to support on the nonlocal 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:
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/ATTRLIB .sql install_dir/tables/cicatrsq/SQLLIB
- The file names of the application support files have the following format:
kpc.extwhere 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 for Linux, UNIX, and Windows monitoring agent. See IBM Tivoli product, platform, and component codes for a list of product codes.
- If you cannot find application support files for some agents 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 Install the monitoring server.
- To install missing files for nonbase 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 Install 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.
Verify that the hub monitoring server to which this remote server sends its data 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.
If you are running in a Hot Standby environment, shut down your Hot Standby monitoring server before completing this procedure. You may restart the Hot Standby monitoring server only after you have seeded the acting hub server.
- Copy the CAT and ATR files to the nonlocal monitoring server
- Add application support (SQL files) to a nonlocal hub
To add application support SQL files to a hub monitoring server on a nonlocal system, complete this procedure.
- Install 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 nonlocal monitoring server.
Parent topic:
Configure application support on nonlocal monitoring servers