IBM Tivoli Composite Application Manager for Transactions Response Time 7.3 Fix Pack 1 README Tivoli Composite Application Manager for Transactions 7.3.0.1 7.3.0.0-TIV-CAMRT-FP0001 Readme

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.

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.

For up-to-date ITCAM for Transactions v7.3.0.1 software prerequisites, please visit:
Prerequisites for ITCAM for Transactions V7.3.0.1

ITM Minimum Prerequisites for this MDV:
Same requirements as ITCAM for Transactions v7.3.
For more information refer to the Compatible software for ITCAM for Transcations 7.3.0.1

For additional download packages or ITM support information, visit the ITM support portal at:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Monitoring_V6

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.

********************************************************************
*
* 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 might negatively
* affect existing product function.
*
* Please refer to APAR(s)
* IV33482
* IV33258
* for problem description(s) and corrective action(s).
*
* Evaluate these APARs for the potential impact in your environment.
********************************************************************

********************************************************************
* 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):

- ECLIPSEHOME\dropins\
- ECLIPSEHOME\rt_plugin_uninstall\
- ECLIPSEHOME\rptse\dropins\ (RPT only)

Non APAR Defect 14248 - Application Management Console (T3/AMC) and Robotics Response Time Agent (RRT/T6) fails to restart after reconfiguration. (ITM 6.2.3 FP2 with Windows)

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."

For more information, please refer to the technote.

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.

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.

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

The information included in this document is published at product release time. For the latest updates on this release please refer to the Installing Response Time documentation:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.3.0.1/rt/install_rt_oview.html

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.

It is recomended that the Application Management Console is updated before updating any other Response Time agent. Refer to the documentation for more information: Upgrading from previous versions of Response Time to V7.3.

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.

For more information, refer to the Installing Response Time monitoring agents and related software guide and look for the Installing application support links for the appropriate Operating System.

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

1. Extract the 7.3.0.0-TIV-CAMRT-Windows-FP0001_TN.zip file to a temporary directory (i.e. C:\temp\7.3-FP0001).
2. 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.
   
3. 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
   
4. 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.
   

Installing the update on Unix/Linux TEMA

1. Download the corresponding UNIX platform (aix, hp, linux, sun) upgrade package and extract it to a temporary directory (i.e. /tmp/7.3-FP0001).
   
2. 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
   
3. USING THE SILENT INSTALL CLI.
   Prepare the silent install file to configure appropriate values for the installation program to use while running the installation process.
   Refer to the following section of the product documentation for additional information in using the silent installation in Unix environments:
   http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.3.0.1/rt/Install_Guide/silent_unix.html
   

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:

1. Tivoli Enterprise Monitoring Server
2. Tivoli Enterprise Portal Server
3. Tivoli Enterprise Portal Desktop Client
4. Tivoli Enterprise Portal Server Browser client (for Linux and UNIX Only)

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.

For step by step application support installation information refer to the documentation:
Install application support for Linux and UNIX
Install application support for Windows system

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:

1. 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
   
   b. Log onto the TEMS using the following command:
   tacmd login -u sysadmin -p password -s <TEMS.HOST.NAME>
   
   c. Issue the following command:
   UNIX : tacmd addBundles -i <directory>\unix
   Windows: tacmd addBundles -i <directory>\windows\deploy
   
   <directory> is the full path to the directory where you extracted the file. For example:
   tacmd addBundle -i C:\temp\TN\WINDOWS\deploy
   
   d. The tacmd command asks whether or not to include the bundles and the prerequisites in the depot.
   Choose Yes.
   
   
2. UPDATE A TEMA AGENT VIA THE TEMS REPOSITORY:
   
   Execute the following command:
   C:\IBM\ITM\cms>tacmd login -u sysadmin -p <password> -s <hostname>
   
   For example: C:\IBM\ITM\cms>tacmd login -u sysadmin -p password -s utms15.tivlab.austin.ibm.com
   
   You must specify the -s option with a host name or address, or you see the following message:
   KUIC00001E: The host name is not specified.
   
   Optionally, you can specify PROTOCOL and PORT as [PROTOCOL://]HOST[:PORT].
   
   The system responds:
   

    Validating user... KUIC00007I: User sysadmin logged into server on https://utms15.tivlab.austin.ibm.com:1889. 

   
   Execute the following command:
   C:\IBM\ITM\cms>tacmd updateAgent -t <agentd> -n <node> -v <version>
   
   For example: C:\IBM\ITM\cms>tacmd updateAgent -t t6 -n Primary:UTMA7:NT -v 7301
   The system responds:
   

    KUICUA012I: Are you sure you want to update the T6 agents that manage <node>:T6 to version 7301 Updating these agents stops any that are running, applies the changes, and restarts them. 

   
   Enter Y for yes or N for no.
   
   The system responds:
   

    KUICUA011I: Updating the T6 agents. KUICUA009I: The T6 agents were updated. 

Specific Installation Instructions for Agents

T3 AMC-APPLICATION MANAGEMENT CONSOLE (END USER DASHBOARD) 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 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:

1. Stop the T6 agent.
2. 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\"

3. 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.

For RPT installation instructions:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.3.0.1/rt/Install_Guide/install_rpt.html
For RFT installation instructions:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.3.0.1/rt/Install_Guide/install_rft.html


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.

1. TBSM Integration
   TBSM integration consists of installing the TBSM support, adding Omnibus support, and importing a Discovery Library Adapter (DLA) book. The 7.3.0.0-TIV-CAMRT-Multiplatform-FP0001_TivoliIntegrationSupport.zip contains separate .zip files for this integration
   a) Omnibus integration with ITCAMT073001_Omnibus.[zip|tar.gz]
   
   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.
   
   
2. 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/

Troubleshooting installation problems from the Support site

For more detailed information, refer to the Installation and Configuration Guide:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.3.0.1/rt/install_rt_oview.html

Uninstalling if necessary

This maintenance package cannot be rolled back. The uninstallation instructions require that the TEMA agent be uninstalled and reinstalled.

Uninstalling the TEMA on Windows

1. Go to the Windows Control Panel.
2. Choose "Add or Remove Program".
3. Click on the TEMA you want to uninstall.
4. Choose "Change/Remove" to uninstall it.

Uninstalling the TEMA on Unix

1. Issue the following command from the /IBM/ITM/bin directory:
   ./uninstall.sh
2. Follow the instructions to uninstall the TEMA that you want to remove.

If the ITM OS Agent is installed on the machine where the uninstall procedure is required, you may proceed as follows:

1. Log onto the TEPS.
2. Right click on the TEMA you want to remove.
3. Choose Remove and follow the dialog buttons for removal.

The Secure Hash Algorithm 1 (SHA1) checksum of the images are as follows:
7.3.0.0-TIV-CAMRT-AIX-FP0001_TN.tar 03ec07599cf38ac9b87864264405a4437ad51078
7.3.0.0-TIV-CAMRT-HP-FP0001_TN.tar f1e16014dd599978654c37a664f0177e7488e9c6
7.3.0.0-TIV-CAMRT-Linux-FP0001_TN.tar a96c58077bcacf85fee1776e3926fbe6833652ca
7.3.0.0-TIV-CAMRT-Solaris-FP0001_TN.tar 3f64d9f6b470746bf7045776cca6fc5fc3fc97fd
7.3.0.0-TIV-CAMRT-Windows-FP0001_TN.zip e97969dbbef180ddd0a9cfcac14b4c6006a04157
7.3.0.0-TIV-CAMRT-Multiplatform-FP0001_TivoliIntegrationSupport.zip 35683e97d78292c8b7c0ad8efdaada658e5ea419
7.3.0.0-TIV-CAMRT-Windows-FP0001_RationalIntegrationSupport.zip ced7ce70e5ffeaae76554a828edd829ca4cd57cb

New Features

The following new features are included in ITCAM for Transactions - Response Time 7.3 Fix Pack 1:

• Web Response Time
• Improved accuracy of metrics reported when certain HTTP communication parameters are used.
• Overall robustness (stability) of the processes when processing a variety of HTTP traffic and when run under a very high processing load.
• Increased breadth of scenarios in which we test the WRT agent.
• Some improvements in the data written to the log files to ease troubleshooting and increase serviceability.

A) APAR Content:

IV00454 KT6AGENT ABORTS DURING SAP PLAYBACKS WITH ACCESS VIOLATION ERROR
IV00529 TRANSACTIONS FOR CLIENT MISSING FROM USER SESSION
IV00840 TIVOLI RATIONAL WRAPPER INSTALL FAILS ON WINDOWS 2008 R2
IV01413 GAPS IN WRT DATA WHILE PROCESSING HEAVY HTTPS TRAFFIC
IV02707 RPT SCRIPT PLAYBACK RESULTS IN ORPHANED SAPGUI PROCESSES
IV03350 WRT PROCESSING IS INEFFICIENT
IV03587 RPT PLAYBACK DATA MISSING ON WINDOWS 7 AND 2008
IV03668 WRT HTTP TRANSACTION COUNTS NOT REPORTED ACCURATELY
IV06736 WRT response times wrong when referrer URL is missing the :port number
IV07019 WRT TO MERGE OBJECTS INTO PAGES CORRECTLY WHEN LOAD BALANCED
IV07483 ITCAM CONSOLE SPELLING ERROR IN CONFIGURATION PANEL
IV07946 SUPRESS KT1 QUERY FAILED MESSAGE
IV08665 WRT CAN CALCULATE INCORRECT LARGE RESPONSE TIME WHEN USER NAVIGATES AWAY FROM WEB PAGE BEFORE IT COMPLETELY RESOLVES
IV09168 POST SUBSTITUTION IN TRANS REPORTING NOT CONVERTED TO UTF-8
IV09213 UNABLE TO SHOW ROBOTIC SCREEN CAPTURE ON XLINUX
IV09854 ENABLE SAP GUI RPT PLAYBACK FOR 64-BIT WINDOWS
IV09878 CORRUPTED FIELDS IN SSL ERRORS WORKSPACE
IV10251 T7.3 STATES LOCATION OF TCR REPORTS INCORRECTLY
IV10291 KT1 CRASH DUE TO RACE CONDITION IN CONNECTION MANAGEMENT
IV10857 ADDING WRM LOG MESSAGES TO INDICATE MISSING DATA DETECTION
IV11132 AMC DATA COLLECTION STOPS UNEXPECTEDLY FOR ISM
IV11856 ITCAM FOR TRANSACTIONS RRT TO SUPPORT RPT V8.2.1
IV12189 MAXIMUM CONCURRENT PLAYBACKS SETTING OF 1 USES 2 THREADS
IV12203 NO ARM DATA FROM RPT 8110 SCRIPT USING 7.3 RATIONAL INTEGRATION
IV12204 7.3 AGENT IMAGES MISSING XML FILES FOR ADDBUNDLE
IV12211 RRT (T6) TEMA LOGS ARE BEING OVERWRITTEN ON UNIX
IV12275 ort highlighting not working due to incorrect rule
IV12279 BIRT ITCAM4TX V73: TRCMD -MODIFY COMMAND FAILS TO OPEN .RPTDESIGN
IV12376 RRT PROFILE INCORRECTLY UPDATED
IV12561 KT5AGENT CRASHES WHEN ACCESSING T5SRVOT ODI TABLE WHEN SERVER
IV13721 KFCM120 BECOMES UNRESPONSIVE, WILL NOT SHUTDOWN AND MAY CRASH
IV13773 INVALID XML PREVENTS AMCE LAUNCH
IV14266 MISLEADING "COULD NOT OPEN /T3/CONFIG/COMPRESSED.ENCODED" MSG
IV14272 RPT W BENCH V8.2 W/ SIEBEL TEST - NULLPOINTER EXCEPTION
IV14739 EXPECTED AND ACTUAL MISSING WITH RPT 8.2.X SCRIPTS
IV14906 ENABLE RESTART OF JVM ON CITRIX TIMEOUT
IV14968 KT5AGENT FAILS TO START AFTER INSTALLATION ON LINUX 64 BIT TO A
IV15361 SUPPORT FOR SSL HANDSHAKE TYPE 21 AND 22
IV15488 WRT 7.3 DUPLICATE ENTRIES IN HISTORY TABLES
IV15768 MISSING RELATIVE DAY SELECTION FOR ITCAM FOR TRANSACTION
IV16545 SPACE IN SERVER MAP ENTRY TRUNCATES LIST
IV17383 KT5AGENT ABENDS WITH CORE FILE ON AIX
IV18330 KFCM120 CRASHES PROCESSING LARGE COOKIE OR OTHER HTTP HEADER
IV18331 KFCM120 PROCESS CRASHES UNDER HIGH LOAD
IV18436 KT5AGENT WAS CRASHING PROCESSING TRANSACTIONGROUP
IV19061 KFCM120 PROCESS CAN USE TOO MUCH MEMORY IN A VERY BUSY SYSTEM.
IV19083 EMBEDDED OBJECT WITH AN EMPTY REFERER MAY CAUSE KFCM120 TO CRAS
IV19257 KFCMSERVER.EXE OR KFCM120 CRASH WHEN PROCESSING HTTP TRAFFIC
IV21242 KFCM120 PORCESS CAN CRASH WITH LARGE HOST: HEADER
IV21646 RRT PROFILES INCORRECTLY DISTRIBUTED TO THE AGENT
IV21805 CHANGE SCHEMA NAME FROM ITMUSER TO BLANK
IV23027 BAD LOG MESSAGE ON ARM FILE RECURSION
IV24397 Transaction Reporter reports component name as N/A for WRT transactions when integrating with the TTAPI
IV24784 KT5AGENT BECOMES UNAVAILABLE/STOPS SYNCHRONIZING WITH T3 DEPOT WHEN FAILING TO BIND PORT 2222
IV24793 ON UNIX MACHINES WITH MIXED CASE HOST NAMES CANDLECONFIG CAN BECOME INEFFECTIVE.
IV24882 WRT NOT UNCOMPRESSING XML POST DATA AS STATED IN RELEASE NOTES
IV25267 WRT HTTPS DECODING OF HTTP HEADER FIELD NAMES CAN INCORRECTLY HANDLE LOWER CASE
IV25651 WRT DOES NOT LINK TTAPI EVENTS GENERATED FOR RELATED HTTP/S TRANSACTIONS IF THE PROTOCOL, PORT OR HOSTNAME CHANGES
IV25691 KT5 ON SOLARIS CAN GO OFFLINE IN TEP NAVIGATOR, THE KT5AGENT PROCESS IS STILL RUNNING BUT DOES NOT APPEAR TO BE ACTIVE
IV25899 TCR SQL SCRIPT INDEX NAME TOO LONG FOR DB2
IV26785 WRT INCORRECTLY SETS COOKIE AND QUERYSTRING VALUE IN THE HORIZONTAL STITCH WHEN THEY ARE NOT PRESENT IN THE HTTP HEADER
IV26872 T5 AGENT FAILS TO START WHEN CONFIGURED TO USE IP.SPIPE ON 64-BIT OS
IV27485 WEB RESPONSE TIME AGENT ON WINDOWS CAN HAVE HIGH CPU RESULTING FROM SSL DECRYPTION FAILURES
IV27488 WEB RESPONSE TIME AGENT CONSUMES MEMORY WHEN RECEIVING SSL ERRORMESSAGES, SUCH AS DECRYPTION FAILURES
IV28235 AMCE FAILS TO DISPLAY SUBTRANSACTIONS OF RPT SCRIPTS
IV29549 WEB RESPONSE TIME INTEGRATION WITH TRANSACTION TRACKING CAN FAIL TO STITCH TO WAS WHEN USING RPT
IV29550 MEMORY BLOAT OF KFCM120 PROCESS OBSERVED TO CONTINUOUSLY INCREASE OVER TIME EVENTUALLY CONSUMING AVAILABLE RESOURCES.
IV30470 KT5AGENT CRASHES WHEN CLIENTS.XML CONTAINS CLIENT GROUP WITH OVER 1000 FILTER ENTRIES
IV31237 Web Response Time agents TTAPI integration sends incorrect events with Server Mask configuration
IV31238 Web Response Time agent Page Elements Current view inconsistent with Transaction Pages when User and Session tracking enabled
IV31245 Web Response Time agent restricts warehousing of T5TXINS and T5SUBTXINS
IV31249 Web Response Time agent fails to warehouse 5 minutes of data from User/Sessions Table and SSL Alarms Table
IV31260 Core file generated from kfcm120 when processing http post data
IV44507 'DLADAPTER.SH/BAT -ENCRYPT ' COMMAND NOT CLEARLY DOCUMENTED, AND PASSWORD APPEARS IN CLEAR IN TRACE-DLA.LOG
IZ98704 T6 TRACE-ROBOTIC.LOG SERVICEABILITY ISSSUE FOR RPT SAP GUI PlayBACK

From superseded fixes:
(Please note the below fixes are accumulated from ITCAM for Transactions - Response Time 7.2 FP3)

IZ99764 KFCM120 ABORTS ON SOLARIS WHILE IN APPLIANCE MODE
IZ99670 RRT END TIME IS BLANK OR CORRUPTED IN TRANSACTION HISTORY
IZ98970 MISSING REQUESTS IN TEP WORKSPACES FOR RESPONSE TIME DATA
IZ98865 CONTENT CAPTURE FAILS TO RENDER DUE TO UNHANDLED EXCEPTIONS
IZ98704 T6 TRACE-ROBOTIC.LOG SERVICEABILITY ISSSUE FOR RPT SAP GUI PBAC
IZ98691 WRT REPLY SIZE BUFFER IS 8X LOWER THAN CONFIGURED VALUE
IZ97380 T5 KFLM CREATES MALFORMED SM3 RECORDS AND KT5AGENT ABENDS
IV00454 KT6AGENT ABORTS DURING SAP PLAYBACKS WITH ACCESS VIOLATION ERROR

B) Additional Non APAR Defects:

8716 BSMIVT: TBSM 6.1 - Script for configuring Netcool/OMNIbus alerts failed with wrong JAVA_HOME
8718 BSMIVT: tbsmconfig.sh does not complete due to missing TBSM 6.1 files
8822 BSMIVT: omnibusUpdater.cmd does not work on TBSM 6.1 integration with Netcool/OMNIbus on windows 2003 server
9050 POST data sent over KFC1 unnecessarily.
9055 POST data searching should not be realiant on KFCMENV property KFC_POST_DATA_CAPTURE_LENGTH
9056 KFC_OVERRIDE_SOURCE_ADDR_HEADER should be lowercased since headers are lowercased
9892 kfcmserver spins when network device disabled and enabled
10519 CT4869: T3 of RT7.3 cannot startup when installed with ITM server 623 iFix01
10544 kfcmserver/kfcm120 crash on shutdown in KFCP_ApplicationServerTask
10610 Parsing of KFC_RESTRICT_HOST is incorrect
10797 RPT 8.1.1.2 scripts are not ARM enabled when hotfix is missing
11323 DataFetcher missing after ITCAM TBSM integration package install (BSMA Defect 28845)
11451 WRM crashes if user tracking is enabled and very long variables are used for username field.
11455 Connected T3 no longer displayed in AMCE
11632 Some client events arent matching BSM_Identity
11655 SVT:TBSM61:Exception pop out when visit the reports cam_perf_trend_report
11759 Integration package: Problem with aix i nthe tbsmconfig.sh script
12168 Conditionally remove quotes in kto.rules (aggregate_id/destination_id)
12308 All master files in the kt1depot/t3/camconfig directory are being updated every 5 minutes irrespective of whether any related profiles have changed
12664 SVT73FP1 CAM_RRT_SubTrans_DataFetcher is created with invalid policy file
12666 SVT73FP1:Fetch failed message in the two SQL datafetchers
12743 Remove the option in the AMCE that allows the user to report the WRT transaction name as $URL$
12825 WRM crash on shutdown.
13284 With Apache HTTP -> Tomcat proxy configuration, the TTAPI events at the Transaction/Component levels are incorrect
13774 ISA DC: T5 collection fails to collect unix wrm logs
13969 Components configuration data is not diplayed in the Profile Configuration workspace
13982 T5 installer doesn't warn about missing winpcap for Windows 32-bit
14067 T5:WRM gui fails to update kfcmenv file when exclude mask is removed from configuration panel
14164 SVT:Reg:Can not run tbsmconfig.sh successfully due to invalid characters
14236 RT Unable to add bundles for remote deployment with ITM 6.2.2.9
14247 SVT:Reg:Exception while visit the reports cam_perf_trend_report
14290 Problem with terminated protocol processor threads on AIX for kfcm120

From superseded fixes:

N/A

C) Enhancements

N/A

From superseded fixes:

N/A

Version	Date	Description of change
1.0	27 July 2012	Initial Version
1.1	7 September 2012	Modify Release Date
1.2	15 November 2012	Update Known Issues and APAR list
1.3	22 November 2012	Update Known Issues and APAR list
1.4	27 November 2012	Added New Features Section
1.5	30 November 2012	Minor Formatting Changes
1.6	3 December 2012	Use 7.3.0.1 Documentation links
1.7	14 January 2013	Update Known Issues
1.8	22 January 2013	Update Known Issues
1.9	1 February 2013	Update Known Issues
2.0	17 June 2013	Withdraw Fix Pack
2.1	3 July 2013	Update APAR list to include APAR IV44507