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 > Configure application support on a nonlocal monitoring server from a Windows system

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Copy the CAT and ATR files to the nonlocal monitoring server

Copy the .cat and .atr files for the agents you want to support from the local Windows monitoring server to the nonlocal 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:

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


Locations of CAT and ATR files for the monitoring server

Remote computer on: File type Directory
.cat install_dir\cms\RKDSCATL
.atr install_dir\cms\ATTRLIB
.cat install_dir/tables/cicatrsq/RKDSCATL
.atr install_dir/tables/cicatrsq/ATTRLIB

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.

  1. If you export the CANDLEHOME environment variable to your current session, many of the installation and configuration commands do not require that CANDLEHOME be passed to them (usually via the -h CLI parameter).

  2. If you are adding support to a monitoring server on z/OS, you can use the FTP utility provided with Manage Tivoli Enterprise Monitoring Services. While checking existing files on the z/OS machine, the tool extracts the version line from the content of all files found. In a CAT file, the version line begins with the character @. In an ATR file, the version line begins with the comment marks //. The version numbers and timestamps that are obtained are used for version comparison. The following rules apply:

    • Files selected for FTP transfer that have a version higher than the corresponding file on z/OS, or have no corresponding file on z/OS, are transferred.

    • Files selected for FTP transfer that have a version lower than the corresponding file on z/OS are not transferred. You are alerted that some files cannot be transferred due to possible backleveling, and those files are excluded from the list of files to be transferred.

    • Files selected for FTP transfer for which it was impossible to determine a version are not transferred. This can be caused by, for example, file access error, or version text not found or incorrect. You are alerted that some files cannot be transferred due to the encountered errors, and those files are excluded from the list of files to be transferred.

    • If all files selected for FTP transfer are excluded from the transfer due to possible backleveling or reading version errors, the transfer is cancelled.

    • If some files selected for FTP transfer are excluded from the transfer due to possible backleveling or reading version errors, you are alerted that some files cannot be transferred and those files are excluded from the list of files to be transferred. The remaining files are transferred after confirmation.

    See Configure the Tivoli Enterprise Monitoring Server on z/OS.

  3. 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()~-./".


Parent topic:

Configure application support on a nonlocal monitoring server from a Windows system

+

Search Tips   |   Advanced Search