IBM Tivoli Composite Application Manager for Transactions Response Time 7.3.0.1 Interim Fix 39 README Tivoli Composite Application Manager for Transactions 7.3.0.1 7.3.0.1-TIV-CAMRT-IF0039 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 supersedes 7.3.0.1 IF0020, 7.3.0.1 IF0026, and 7.3.0.1 IF0033 and may be applied to the following base versions.

• 7.3.0.1

Note: Supported base version includes interim fixes applied to the above release level.

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 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 to upgrade the integration support files with RT 73 Interim Fix 39. Otherwise, it is recommended that the integration support files be upgraded to the most recent version supplied with this interim fix.

AIX 32-bit agents only - Incorrect behaviour for Session Timeout and Minimum and Maximum Response Time Threshold

Problem Description
Minimum and Maximum Response Time Threshold will be interpreted as 0.000, regardless of AMCE settings
causing data in TEP workspaces to be reported as Slow even though actual response times are within the
threshold values defined in AMCE.
WRT User and Session Tracking behaviour does not accurately reflect AMCE configuration. Session Timeout
is interpreted as if zero was specified (regardless of actual setting), resulting in session tracking data
being discarded immediately.

Non APAR Defect 19594 - CVT: Missing lastest AC (Agent Compatibility bundle) in FP2 build, remote deploy T6 to windows 64-bit machine failed

Problem Description
Remote deploying T6 agent to a Windows 64-bit machine failed because the latest Agent Compatibility bundle is not found in the TEMS depot.
Please see this technote.

Non APAR Defect 14346 - Installing KT1 on Linux 64-bit overwrites TEMS 6.2.2.2+ TRANSFER module

Problem Description
TEMS from ITM 6.2.2 FP2 onwards ships their own TRANSFER module and T1 support. If you install RT's File Transfer Enablement (T1) module on Linux 64-bit it does not warn or prompt you, but silently overwrites the existing TEMS file. You end up with two entries in cinfo, t1 ITCAM File Transfer Enablement lx8263 Version: 07.21.00.00 (from ITCAM) lx8266 Version: 07.30.00.00 (from TEMS) but they both write to the same TRANSFER file: /opt/IBM/ITM/lx8266/ms/lib/TRANSFER This prevents some KT1 functions working, like RRT's content capture display site. There is a similar issue on Windows, although that is more difficult as the T1 is not its own versioned component on that platform.

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 immediately 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

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 interim fix, ensure that you comply with the prerequisites and corequisites for this interim fix. 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).
• Tivoli Enterprise Portal (TEP) desktop clients.

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.1-TIV-CAMRT-AIX-IF0039_TN.tar
• Linux : 7.3.0.1-TIV-CAMRT-Linux-IF0039_TN.tar
• Windows: 7.3.0.1-TIV-CAMRT-Windows-IF0039_TN.zip
• Solaris: 7.3.0.1-TIV-CAMRT-Solaris-IF0039_TN.zip
• HP: 7.3.0.1-TIV-CAMRT-HP-IF0039_TN.zip

• Integration Support
• Multiplatform : 7.3.0.1-TIV-CAMRT-Multiplatform-IF0039_TivoliIntegrationSupport.zip
• Windows: 7.3.0.1-TIV-CAMRT-Windows-IF0039_RationalIntegrationSupport.zip

Notes on installation

This Interim Fix provides significant updates over 7.3.0.0-TIV-CAMRT-IF0026 for:
• Application Management Console (T3) agent
• Web Response Time (T5) agent
• Robotic Response Time (T6) agent

Installing the update on Windows TEMA

1. Extract the 7.3.0.1-TIV-CAMRT-Windows-IF0039_TN.zip file to a temporary directory (i.e. C:\temp\7.3-IF0039).
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-IF0039\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-IF0039\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, linux) upgrade package and extract it to a temporary directory (i.e. /tmp/7.3-IF0039).
   
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-IF0039/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.1-TIV-CAMRT-Multiplatform-IF0039_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.1-TIV-CAMRT-Multiplatform-IF0039_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.1-ITCAM_Transactions_Installer.Unix.tar
7.3.0.1-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.39'.

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 Troubleshooting Guide:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=%2Fcom.ibm.itcamt.doc_7.3.0.1%2Frt%2FTSG%2Frt_trouble_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.1-TIV-CAMRT-AIX-IF0039_TN.tar af3767e4c264aa4edddada0356e1fc565ddd11e4
7.3.0.1-TIV-CAMRT-HP-IF0039_TN.tar 2a0546f965779a9c82556fcf72c1b4ee8880fddf
7.3.0.1-TIV-CAMRT-Linux-IF0039_TN.tar 763c0fb330cb4f2dcc1014a2fb92f6a54f415e67
7.3.0.1-TIV-CAMRT-Solaris-IF0039_TN.tar 1d86719e354658a97ae07b454e5d9985394b2333
7.3.0.1-TIV-CAMRT-Windows-IF0039_TN.zip ebcd786ec1035a586c8258f2c070ba374ec00739
7.3.0.1-TIV-CAMRT-Multiplatform-IF0039_TivoliIntegrationSupport.zip 5d63d00d18c7f18bb2d606a7104e99d3676b42a0
7.3.0.1-TIV-CAMRT-Windows-IF0039_RationalIntegrationSupport.zip fbcd44ff16c2cb0a1ed9ffaaf68b0b4e08acd94c

New Features

The following new features are included in ITCAM for Transactions - Response Time 7.3.0.1 IF0039:

• Web Response Time
• Add support to allow WRT to track users via HTTP cookie.

A) APAR Content:

ITCAM
IV77042 QUERY TO T3ISMTSPAN TABLE DOES NOT RETURN PROPER ORIGINNODE VALUE
IV69502 WRT unable to parse T5 config file when system uses FQDN hostname
IV69357 Expired HTTP Data may be leaked
IV69064 WRT Analyzer incorrectly matches all transactions in session after a 401 response
IV66100 T6 agent generates blank APPNAME and TRANNAME in T6PBSTAT history file after ITM upgrade from V6.2.2 to V6.2.3 FP04
IV65962 WRT decompression of XML Post content incorrect
IV61381 WRT AGENT RETURNS INCORRECT DATA FROM T5TCPSTAT WHEN FILTERS SPECIFIED FOR COLUMNS 'SEND BANDWITH (KB)',RECEIVE BANDWIDTH(KB)
IV62835 WRT Queries comprising of multiple expressions separated by logical OR may return incorrect data
IV63094 WRT Network Time incorrectly calculated
IV63354 WRT to handle "TCP segmentation off loading" allowing for IP Headers with 0 Length and CheckSum
IV60728 WRT AGENT GETS WRM_DECRYPT_FAILURE WITH INCORRECT PMS SIZE IF SSL VERSION CHANGES DURING HANDSHAKE
IV56770 WRT Subtransactions for embedded objects in web pages are not reported by kt5agent
IV56765 WRT kt5agent can bloat with unique URLs when not collecting subtransactions
IV56740 WRT CRASHES WITH MULTIPLE HTTP REQUEST/REPLY SEQUENCE WITH REQUEST CONTENT AND MISSING PACKETS
IV54977 Track Anonymous users by client hostname
IV53926 Web Response Time Protocol Processor threads can exit prematurely on Windows
IV53000 T3 IGNORES SUBNODE LIST FROM SUBNODE QUERY
IV59249 AMC RESOLVED AN UPDATED PROFILE TWICE
IV76162 RPT script playback failed with error message "Test virtual user setup failed. startStatus=-14"
IV74161 When enable Content capture In Windows Platform, Content Capture zip files continue to generate without VP failure Event


From superseded fixes:
7.3.0.1 IF0039 is a cumulative interim fix release and supersedes IF0020, IF0026 and IF0033 APAR fixes.
(Please refer to release notes for ITCAM for Transactions - Response Time 7.3.0.1 IF0020 APAR list)
(Please refer to release notes for ITCAM for Transactions - Response Time 7.3.0.1 IF0026 APAR list)
(Please refer to release notes for ITCAM for Transactions - Response Time 7.3.0.1 IF0033 APAR list)


B) Additional Non APAR Defects:

ITCAM
30511 PSIRT 5417 Open Source Apache Xerces-C XML parser Vulnerabilities - CVE-2016-0729
30651 Update ARM with newer version TRANS_5907 for xerces-c PSIRT for 7301
25435 PSIRT 2290 CVSS 4.3 Record 44640 - SSLv3 POODLE Attack - CVE-2014-3566 (AMC)
19165 T3 can not restart due to wrong KT3_JAVA_HOME on Window 64bit platform
20582 Incorrect metric values in transaction step table from oracle TNS addon


From superseded fixes:

N/A

C) Enhancements

RFE55848 Add support to allow WRT to track users via HTTP cookie

From superseded fixes:

N/A

Version	Date	Description of change
1.0	04 August 2016	Initial Version - no AIX