Installation information

Download location

The information included in this document is published at product release time. For the latest updates on this release please refer to the on-line document: To download this update you must first login to IBM FixCentral. Once logged in, you may select from the individual download packages. http://www.ibm.com/eserver/support/fixes/

Below is a list of components, platforms, and file names that apply to this Readme file.

Prerequisites and co-requisites

This upgrade for ITCAM for Transactions Response Time may be applied to the following base versions.

7.2.0.0

7.2.0.1

7.2.0.2

7.2.0.3

7.3.0.0

Note: Supported base versions include interim fixes applied to any of the above release levels. This fixpack is also available as a refresh pack. Users can perform a base installation from a CD image at the FP01 maintenance level. The base install image is available from Passport Advantage.

Integration Support for TCR,DLA,Omnibus,TBSM,Cognos

The most recent release of the integration support files (07300100) have been included in this fix pack for convenience. If the currently installed integration support is at 7.30.01.00 or higher it is not necessary upgrade the integration support files with RT 73 Fix Pack 1. Otherwise, it is recommended that the integration support files be upgraded to the most recent version supplied with this fix pack.

Known issues

********************************************************************
*
* This Fix Pack is no longer available. Please see APAR
IV41150 * for a description of the problem and corrective action.
*
* 7.3.0.1 IFix 20 for CAMRT resolves this problem and is available
* here:
http://www.ibm.com/support/docview.wss?uid=isg400001541 *
********************************************************************

********************************************************************
* A change introduced by this Fix Pack is incomplete but will not
* adversely affect existing function.
*
* Please refer to APAR(s) IV36117 for a description of the
* problem(s) and corrective action(s).
*
* Evaluate these APARs for the potential impact in your environment.
********************************************************************

Non APAR Defect 8858 - kfcm120 process abends under high load

Problem Description
When running continuously under high load conditions, the kfcm120 process can exhibit rapid memory growth which eventually leads to the process abending.
Root cause
The kfcm120 process relies on system resources to communicate with the Web Response Time TEMA (kt5agent). If these system resources are not readily available then the process begins to consume vast amounts of memory until the process exceeds its memory capacity and fails. This can occur on certain operating systems with OS level resource management if the kfcm120 process is started immediatly after a previous failure or an abnormal shutdown ( such as a kill -9 on Unix/Linux). The issue is greatly exacerbated under high load conditions.
For more information, please refer to these articles on
performance tuning.
Workaround
The recommended action to prevent failures in the kfcm120 process is to restrict the amount of data being processed by the agent. This can be done by setting the KFC_RESTRICT_HOST variable in the kfcmenv file.
The format for setting the host restriction is:
KFC_RESTRICT_HOST=
:
[,
:
, ...]
For Example:
KFC_RESTRICT_HOST=10.98.123.12:80,10.98.123.13:80

Non APAR Defect 12906 - Rational Integration Support Uninstallation may not work

Workaround
If the uninstall fails, you can manually remove the plugin by first exiting RPT / RFT and then deleting the folders (where ECLIPSEHOME is the root folder of the RPT or RFT installation):

Problem Description
AMC and RRT agents on windows, installed on a machine also with ITM 6.2.3 FP2 fails to restart automatically after a reconfigure. Instead, the MTEMS displays error message "KCICF5100E: Unable to start service, see Event Log for information."

Workaround
Restart the agent again via the MTEMS (select agent, click the green traffic light). Failure occurs only on post-configure step, not on regular startup.

Non APAR Defect 14346 - File Transfer Enablement

Problem Description
In some scenarios installing components on a TEMS machine can backlevel the TRANSFER library. This is only an issue when installing on to TEMS v6.2.2.2 or higher (including v6.2.3 and subsequent releases). It is recommended that you backup your TEMS TRANSFER library before installing Response Time components on your TEMS. On a Windows TEMS the file is:
C:\IBM\ITM\CMS\TRANSFER.dll.
On Linux/UNIX TEMS systems the file is:
/opt/IBM/ITM/ <ARCH> /ms/lib/TRANSFER See here for more information:
Troubleshooting File Transfer Enablement.

APAR IV19061 - KFCM120 PROCESS CAN USE TOO MUCH MEMORY IN A VERY BUSY SYSTEM

Problem Description
The typical deployment scenario that this has been observed is having WRT monitor network traffic between a Load Balancer and a number of web servers, and the kfcm120/kfcmserver.exe process has had high memory and CPU use.

Root cause In analysis of customer environment leading up to this APAR it was identified that the Object Merge Task was responsible. It has also been identified since that it can also lead to very high CPU use.

Workaround In order to have the object Merge Task perform efficiently it is recommended to:
1. configure the Load Balancer to insert a HTTP Header such as x-forwarded-for that contains the original requests source IP address,
2. have the kfcmenv specify the environment variable "KFC_OVERRIDE_SOURCE_ADDR_HEADER" with the name of that HTTP Header.

Known limitations

Exceeding processing capacity can starve system resources

Problem Description
When running continuously under high load conditions, the kfcm120 process can exhibit memory growth which can eventually lead to the process abending. The recommended action to prevent failures in the kfcm120 process is to restrict the amount of data being processed by the agent. This can be done by setting the KFC_RESTRICT_HOST variable in the kfcmenv file.

For Windows installation, if you encounter the message "Another version of this product is already installed" follow the instructions in the following support document to diagnose and resolve the problem. Note that although this technote refers to ITM, the diagnosing and resolving steps are applicable to ITCAM for Transactions Response Time. http://www-01.ibm.com/support/docview.wss?uid=swg21587068

Prior to installation

Before attempting to apply this fix pack, ensure that you comply with the prerequisites and corequisites for this fixpack. For more information, please refer to the ITCAM for Transactions Prerequisites. Also, it is recommended to read the Known Limitations for issues you may encounter while applying this maintenance package.

This maintenance package is applied directly to the Tivoli Enterprise Management Agents (TEMAs). This package also includes required updates to the following ITM components:

Tivoli Enterprise Management Servers (TEMS) in the ITM infrastructure, including any Remote TEMS or fail over TEMS configurations.

Tivoli Enterprise Portal Server (TEPS).

You can install an RT agent either on a computer by itself or on a computer with an installed TEPS, TEMS, and/or portal. If you install an RT agent on a computer where the TEPS, TEMS and portal are already installed, the installer automatically stops the ITM agents and infrastructure (including TEMS and TEPS) running locally. If you install an RT agent on a computer by itself the ITM agents and infrastructure do not need to be stopped.

Installing

Download the corresponding executable file bundle for your operating system or package:

TN (Includes T3, T4, T5 and T6 agents)

AIX : 7.3.0.0-TIV-CAMRT-AIX-FP0001_TN.tar

HP-UX : 7.3.0.0-TIV-CAMRT-HP-FP0001_TN.tar

Linux : 7.3.0.0-TIV-CAMRT-Linux-FP0001_TN.tar

Solaris: 7.3.0.0-TIV-CAMRT-Solaris-FP0001_TN.tar

Windows: 7.3.0.0-TIV-CAMRT-Windows-FP0001_TN.zip

Installing the update on Windows TEMA

Extract the 7.3.0.0-TIV-CAMRT-Windows-FP0001_TN.zip file to a temporary directory (i.e. C:\temp\7.3-FP0001).

USING THE WIZARD INSTALLATION GUI. a. Execute the setup.exe command to start the Installation Wizard. The setup.exe is located under the WINDOWS directory in the chosen temporary directory. For example: C:\TEMP\7.3-FP0001\WINDOWS\setup.exe b. Follow the Installation Wizard panels by responding to each option that corresponds to the TEMA agent being upgraded. Default values are provided. It is possible to select or specify different options that must match the appropriate settings for your environment. Also, you may be required to fill in the values when a blank option is not permitted. NOTE: During the interactive installation, you can choose to add the TEMA to the TEMS depot so you can do remote installs for the platform you are adding into the depot.

USING THE SILENT INSTALL CLI. a. Prepare the silent install file to configure appropriate values for the installation program to use while running the installation process. The silent installation configuration file is located under the Windows directory of the directory image. (i.e. C:\TEMP\7.3-FP0001\Windows\silent.txt) b. Edit the silent install file to provide appropriate values for the desired configuration. By default, all options are commented out, and the installer uses the values from the previous TEMA configuration. The silent install file describes each option, and you can also find information in the monitoring agent's User Guide. For additional information on the options for the silent installation of the TEMA agents, please consult the ITCAMfTransactions v7.3 User's Guide. Refer to the following chapter in the product documentation for further instructions on the use of the silent installation features for this maintenance package: http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.3.0.1/rt/Install_Guide/silent_win.html

REBOOT THE COMPUTER. After the installation of the upgrade of a TEMA in Windows, it is necessary to reboot the computer to allow the system to properly register the latest settings in the ITCAM, ITM and Operating System registries. In environments where the TEPS and RT TEMA agents coexist in the same ITM instance, the update for the TEMAs offers the option to restart the computer, install the support packages for the TEPS first. Allow the TEPS to restart before restarting the computer as part of the TEMA update.

USING THE SCRIPT BASED INSTALLATION PROCEDURE. a. Execute the install.sh to start the Installation Wizard. The install.sh command is located directly under the main directory of the upgrade image. For example: # /tmp/7.3-FP0001/install.sh

b. Follow the text wizard panels by responding to each option that corresponds to the TEMA agent to be upgraded.

Default values are provided. You may select different options or you may be required to fill in the values when a blank option is not permitted. NOTE: During the interactive installation, you can choose to add the TEMA to the TEMS depot so you can do remote installs for the platform you are adding into the depot. The software prompts you for this option after you choose what you want to install. c. After the Installation Wizard completes, you must configure your agents. This is done by issuing the itmcmd ITM command as follows: $ITM_HOME/bin/itmcmd config -A <AGENT_TYPE> Where <AGENT_TYPE> is t3, t4, t5 or t6 For example, to configure the Robotic Response Time agent (t6), issue: # $ITM_HOME/bin/itmcmd config -A t6

Installing application support for TEPS/TEMS For each monitoring agent installed, you must install agent-specific application support on IBM Tivoli Monitoring components. You can choose to install application support on all components at one time, or you can install the application support on components separately. If installing components separately, the following order is recommended:

The procedure for installing agent-specific application support on the components is similar to installing the monitoring agent. The main difference is to select the application support components required.

Note: When installing application support any ITM components on the current machine is automatically stopped, including any TEMS or TEPS. Follow the Starting and stopping servers and agents guide to manually stop ITM agents and infrastructure. You should warn other users before beginning the installation.

Updating TEMA using the TEMS Depot Repository To facilitate the deployment of software updates to the TEMA agents, it is possible to add the upgrade images to the TEMS repository and transfer the updates to the agents. Follow the instructions below:

ADD THE UPDATE IMAGES TO THE TEMS DEPOT. a. Expand the TEMA tar or zip file into a temporary directory on the TEMS machine. For example: C:\temp\TN

After installing this maintenance package, the agent must be reconfigured using the ITM services console or the CLI interface, so that necessary configuration changes are done and the agent processes can be initialized with the new settings.
For example:
<ITM_HOME>/bin/itmcmd config -A t3

T4 CRT-CLIENT RESPONSE TIME AGENT.

After installing this maintenance package, the agent must be reconfigured using the ITM services console or the CLI interface, so that necessary configuration changes are done and the agent processes can be initialized with the new settings.
For example:
<ITM_HOME>/bin/itmcmd config -A t4

T5 WRT-WEB RESPONSE TIME AGENT.

When upgrading T5 agents that are monitoring local instances of the IBM HTTP Server, it is necessary to stop the IHS process prior to the upgrade. For all other web server instances it is also recommended to stop the server prior to running the upgrade and reconfiguration of the T5 agent. It is not required to stop web servers when monitoring remote transactions.
After installing this maintenance package, the agent must be reconfigured using the ITM services console or the CLI interface. For example:
<ITM_HOME>/bin/itmcmd config -A t5

T6 RRT-ROBOTIC RESPONSE TIME AGENT

After installing this maintenance package, the agent must be reconfigured using the ITM services console or the CLI interface, so that necessary configuration changes are done and the agent processes can be initialized with the new settings. For example:
<ITM_HOME>/bin/itmcmd config -A t6

MANUAL UPDATE OF ARM LIBRARIES.

For T6 agents configured to run IBM Rational Robot, this update package provides a new libarm4.dll library that needs to be manually updated in the Rational Robot project directories.
After having completed the upgrade process and reconfigured the T6 agent, proceed as follows:

Stop the T6 agent.

Replace the libarm4.dll in the Rational Robot directory: Copy the libarm4.dll file in the ITM_HOME\TMAITM6\t6\lib directory to the RATIONAL_HOME_BASE\Rational Test directory. For example if the ITM_HOME and Rational home base directories are: C:\IBM\ITM C:\Program Files\Rational\Rational Test\ from a DOS command prompt, you may execute: C:> copy C:\IBM\ITM\TMAITM6\t6\lib\libarm4.dll "C:\Program Files\Rational\Rational Test\"

Start the T6 agent.

Rational Integration Support This maintenance vehicle also provides an updated Rational Integration Support installer which must be installed on all RPT or RFT workbench installations that need to export scripts for monitoring. This installer automatically upgrades any previously installed Rational Integration Support packages, it can also be used to perform new installations.

Tivoli Integration Support This maintenance package includes the file 7.3.0.0-TIV-CAMRT-Multiplatform-FP0001_TivoliIntegrationSupport.zip containing integration support for Tivoli Business Service Manager (TBSM) and Tivoli Common Reporting (TCR).
The TBSM integration support allows for viewing ITCAM's Applications and Transactions inside the TBSM Portal and viewing correlated Omnibus events and custom charts. The TCR integration is an updated set of reports based on 7.3 summarized data in the Tivoli Data Warehouse for examining historical data.

This .zip file contains executables that run on Omnibus 7.2.1 server. It enriches forwarded situations from ITCAM for Transactions to the Omnibus EIF probe. These enriched events are better correlated in TBSM. After you unzip the .zip file, you execute the omnibusUpdater for your system. Windows is omnibusUpdater.cmd and Unix is omnibusUpdater.sh. Executing the command with no arguments prints the usage syntax to screen. For more information, please see the readme.txt included with the .zip. b) TBSM integration with ITCAMT073001_TBSM.[zip|tar.gz]

This .zip file contains executables that run on the TBSM 4.2 IF2 server. It creates ITCAM for Transactions specific TBSM templates, policies and service trees. After you unzip the .zip file, you execute the tbsmconfig for your system. Windows is tbsmconfig.cmd and Unix is tbsmconfig.sh (must add the +x permission first). Executing the command with no arguments prints the usage syntax to screen. For more information, please see the readme.txt included with the .zip. c) DLA creation with ITCAMT073001_DLA.[zip|tar.gz]

This .zip file contains executables that create DLA books against the ITCAM for Transactions data inside the Tivoli Data Warehouse. After you unzip the .zip file, you must configure the tool by editing both rt_71_dla.config.properties and dlAdpater file. You edit the dlApdater.bat file for Windows and dlAdapter.sh file for Unix. For more information on how to configure, please see the readme.txt file included with the zip file.

TCR Reports in ITCAMT073001_TCR.[zip|tar.gz]

ITCAM for Transactions includes an updated set of Tivoli Common Reporting charts found inside the Integration Bundle. When loaded into TCR these reports provide the ability to be scheduled, turned into PDF, or viewed as HTML. They are loaded into TCR via the import functionality and do not need to be unzipped. After loading them into, TCR you set the Data Source for the report to point to the Tivoli Data Warehouse and from there you can view the reports. Refer to the file ITCAM4T_Reports_README.pdf for further information.

Launchpad for ITCAM For Transactions installer update The following files correspond to updates for the Transactions Installer:
7.3.0.0-ITCAM_Transactions_Installer.Unix.tar
7.3.0.0-ITCAM_Transactions_Installer.Windows.zip

For additional information on usage of these packages, please refer to the
ITCAM InfoCenter

Performing the necessary tasks after installation

A successful installation modifies the Transactions Response Time version to 7.3.0.1. Ensure that the Version of all RT agents in the MTEMS is '07.30.01.00'.

On Windows the installation logs are written to the following directory: ITM\InstallITM\

On Unix the installation logs are written to the following directory: ITM/logs/