IBM Support

IBM Tivoli Composite Application Manager for Transactions Response Time 7.3.0.1 Interim Fix 26 README Tivoli Composite Application Manager for Transactions 7.3.0.1 7.3.0.1-TIV-CAMRT-IF0026 Readme

Fix Readme


Abstract

xxx

Content

Readme file for: 7.3.0.1-TIV-CAMRT-IF0026
Product/Component Release: 7.3.0.1
Update Name: 7.3.0.1-TIV-CAMRT-IF0026
Fix ID: 7.3.0.1-TIV-CAMRT-AIX-IF0026_TN, 7.3.0.1-TIV-CAMRT-LINUX-IF0026_TN, 7.3.0.1-TIV-CAMRT-WINDOWS-IF0026_TN, 7.3.0.1-TIV-CAMRT-MULTIPLATFORM-IF0026_TivoliIntegrationSupport, 7.3.0.1-TIV-CAMRT-WINDOWS-IF0026_RationalIntegrationSupport
Publication Date: 1 Apr 2014
Last modified date: 1 Apr 2014

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. HPUX and Solaris downloads are no longer provided.
http://www.ibm.com/eserver/support/fixes/

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

Fix Download for AIX

Product/Component Name: Platform: Fix:
Tivoli Composite Application Manager for Transactions AIX
7.3.0.1-TIV-CAMRT-AIX-IF0026_TN
Tivoli Composite Application Manager for Transactions AIX
7.3.0.1-TIV-CAMRT-MULTIPLATFORM-IF0026_TivoliIntegrationSupport

Fix Download for Linux

Product/Component Name: Platform: Fix:
Tivoli Composite Application Manager for Transactions Linux
7.3.0.1-TIV-CAMRT-LINUX-IF0026_TN
Tivoli Composite Application Manager for Transactions Linux
7.3.0.1-TIV-CAMRT-MULTIPLATFORM-IF0026_TivoliIntegrationSupport

Fix Download for Windows

Product/Component Name: Platform: Fix:
Tivoli Composite Application Manager for Transactions Windows
7.3.0.1-TIV-CAMRT-WINDOWS-IF0026_TN
Tivoli Composite Application Manager for Transactions Windows
7.3.0.1-TIV-CAMRT-MULTIPLATFORM-IF0026_TivoliIntegrationSupport
Tivoli Composite Application Manager for Transactions Windows
7.3.0.1-TIV-CAMRT-WINDOWS-IF0026_RationalIntegrationSupport

Prerequisites and co-requisites

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

  • 7.3.0.0
  • 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 (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

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.

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.

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

Installation information

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-IF0026_TN.tar
  • Linux : 7.3.0.1-TIV-CAMRT-Linux-IF0026_TN.tar
  • Windows: 7.3.0.1-TIV-CAMRT-Windows-IF0026_TN.zip

  • Integration Support
  • Multiplatform : 7.3.0.1-TIV-CAMRT-Multiplatform-IF0026_TivoliIntegrationSupport.zip
  • Windows: 7.3.0.1-TIV-CAMRT-Windows-IF0026_RationalIntegrationSupport.zip

Notes on installation
    This Interim Fix provides significant updates over 7.3.0.0-TIV-CAMRT-FP0001 for:
  • Application Management Console (T3) agent
  • Web Response Time (T5) agent
  • Robotic Response Time (T6) agent
  • significant updates to Rational Integration Support
  • For RPT 8.3 support also upgarde the rational integration support package.

Installing the update on Windows TEMA
  1. Extract the 7.3.0.1-TIV-CAMRT-Windows-IF0026_TN.zip file to a temporary directory (i.e. C:\temp\7.3-IF0026).
  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-IF0026\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-IF0026\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-IF0026).
  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-IF0026/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-IF0026_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-IF0026_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.26'.

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.

Additional information

The Secure Hash Algorithm 1 (SHA1) checksum of the images are as follows:
7.3.0.1-TIV-CAMRT-AIX-IF0026_TN.tar 72c5236fb70f918139ad5c52f2e26b4bfe599ce6
7.3.0.1-TIV-CAMRT-Linux-IF0026_TN.tar c7f911e24c43cbe10597d9c1221cb53ae67f7eed
7.3.0.1-TIV-CAMRT-Windows-IF0026_TN.zip 3d443135542aa1ed93b1f97b9e10a1c54d357efe
7.3.0.1-TIV-CAMRT-Multiplatform-IF0026_TivoliIntegrationSupport.zip dbbc8087f4a3affff9d49b2768149be863311a82
7.3.0.1-TIV-CAMRT-Windows-IF0026_RationalIntegrationSupport.zip f38c46e610ec5f71243063f49fa1645987921bba

New Features

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

  • 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.
  • Robotics Response Time
    • Adding RPT v8.3 support, including NTLMv2 feature of RPT 8.3 (requires updated agent and rational integration support)
    • For customers using 7.3.0.1-TIV-CAMRT-LA0002 to gain RPT 8.3 support, this IFix supersedes that fix.
    • RPT v8.3.0.0 thru v8.3.0.2 has known memory leak issues when integrated with RRT. Please use RPT v8.3.0.3 or later fixpacks

List of fixes

A) APAR Content:

ITCAM
IV33477 CACHING ERROR WHEN USING BROWSER CLIENT TO ACCESS TEP
IV36499 LAUNCHPAD.SH FAILS WITH FIREFOX VERSIONS > 9.X
IV52076 7.3.0.1 maintenance Some HTTPS Sessions fail to have Requests processed
IV52770 7.3.0.1 maintenance WRT URL used for Filtering and Reporting should not contain Query String
IV53506 7.3.0.1 maintenance Web Response Time FORM post data search length increase may not work

T3
IV33258 T3 name appears as End User Response Time under Historical Configuration
IV33482 TRANSACTION COLLECTOR FILTERING STOPS WORKING AFTER UPGRADING AMC TO 7.3 FP1
IV36168 T3 fails to start when using the pthread.dll from C:\IBM\ITM\TMAITM6
IV47571 Creating a new component definition in AMCE will not cause the T3 to push the update to the agents
IV49652 AMC APPLICATION STOPPED AGGREGATE DATA

T5
IV00529 TRANSACTIONS FOR CLIENT MISSING FROM USER SESSION
IV32535 kfcm120 process can crash when monitoring HTTP traffic supplying very large content
IV32958 APPLICATION HISTORICAL ANALYSIS WKSPCE LISTS TX INSTANCES EXCEEDING 5 MN PERIOD IN APPLICATION HISTORICAL TREND DETAILS
IV34240 kfcm120 oldest session disposal cannot catch up with the rate of incoming packets
IV35433 KFC_CAPTURE_DEVICE not implemented (regression)
IV35438 KFC_BPF_FILTER not implemented (regression)
IV35439 Fragmented SSL data may result in the analyzer crashing, stop processing or session not tracked
IV36410 kfcm120 may occasionally core with chunk data and block cipher
IV38173 SECURITY APAR CVE-2012-2190 - 7.3 Stream
IV38227 SECURITY APAR CVE-2012-2191 - 7.3 Stream
IV38235 SECURITY APAR CVE-2012-2203 - 7.3 Stream
IV39416 KT5AGENT CRASHES WHEN "WRT PERIODS" HISTORICAL DATA COLLECTION
IV44110 Install and Upgrade problems with Web Response Time installer V7.3.0.1
IV44125 Configuration of ComponentName for Web Response Time transaction Definitions is not accessible in AMCE
IV44183 Web Response Time can calculate large response times under very high load
IV44184 WRT can calculate large response times under very high load - 7.3.0.1 maintenance
IV44475 HTTP Content-Type containing ; parameters are not handled by WRT port to 7.3.0.1 maintenance
IV44592 Situation queries to t5appcs table return no data after a warehouse query.
IV44863 WRT IP ADDRESSES SHOWING INSTEAD OF COMPONENT NAMES
IV46685 (Port) OR PREDICATE DOES NOT WORK IN NATIVE SQL SOAP QUERY ON WRT to 7.3.0.1 maintenance
IV47014 WEB RESPONSE TIME TCP LATENCY TIME IS PRESENTED AS ACUMULATIVE TOTAL. IT SHOULD BE AN AVERAGE.
IV48688 7.3.0.1 maintenance WRT KT5AGENT IGNORES KFC_API_MEDIASERVER_LISTEN_PORT CONFIGURATION
IV49635 Error running DC configuration when T5 agent is installed on a system with ITCAM for AD
IV49993 Total User Logins incorrectly for queries other than current, (i.e warehouse and situation) - 7.3.0.1 maintenance and 74. streams
IV50047 WRT TCP Status situation fires when metric being monitored is below the situation threshold value
IV50584 secureMain lock removes execute permissions from kfcm120 binary
IV51045 7.3.0.1 maintenance Add configurable option to set case in server hostnames
IV53326 kt5agent stops supplying data with "TakeSample call abended"

T6
IV33947 UNINSTALLER FOR TIVOLI RATIONAL INTEGRATION FAILS (V7.3.0.0 and V7.3.0.1)
IV34152 RFT image verification failure does not produce content capture
IV35607 Shipped JREs should be updated to resolve security vulnerabilities (JRE5.0)
IV35614 Shipped JREs should be updated to resolve security vulnerabilities (JRE6.0)
IV36520 RPT regex content verification has no violated/actual value
IV46357 Information messages BWMRA0252I with unicode characters in the profile name is visually corrupted in the agent message table. (7.3.0.2)
IV50339 REMOTE DEPLOYMENT OF 32-BIT PACKAGES TO 64-BIT OS FAILS DUE TO 'AX' PACKAGE NOT MATCHING (7.3.0.2)
IV54890 RRT: SECURITY UPDATES FOR JRE(S) - OCT 2013


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


B) Additional Non APAR Defects:

ITCAM
14248 Unable to start service - Robotic Response Time and Console
15681 SVT: Rational Integration Support unable export second RPTRUNTIME to T3
20229 WRT upgrade from 7.3.0.1 on Windows 64 fails to update the Analyzer

T3
19024 T3 agent crashes if it cannot connect to TEMS
19028 T3 agent jars camconfig.jar and kt3com.jar must BOTH or NEITHER be signed
19170 T3, T4 and T6 agent fail to start RHEL 6.0 64bit when some ITM agents installed in default directory and T3/T4/T6 installed in non-default directory (7.3.0.2)

T5
14679 KFC_CAPTURE_DEVICE_NAME ignored by kfcm120/kfcmserver
15868 SVT: The changed component not deliver to WRT
18619 Workspace query to T5PERIODS table crashes agent if its not Monitoring TCP
19076 The kilobytes sent and received metrics in the T5TCPSTAT table are incorrectly calculated from bytes - 7.3.0.x maintenance stream
19077 The WRT report incorrect bandwidth data - 7.3.0.x maintenance stream

T6
15573 SVT: Unable remove Rational Integration Support on Windows 7
16615 RT bundlegen certificate has expired in maintenance streams
19130 Content capture zip file is not created on RFT script
19134 RFT and RPT scripts playback cannot be run on windows 2012 64bit
19158 TEP WebStart launch failed with error unsigned entry in resource: http://tivvm340:15200/classes/mx4j.jar
19167 T6 fail to start after install ITM6.3 (and 6.2.3.1) OS agent NT
19538 RFT 8.2.1.1 script failed to playback on T6 agent.
20041 Rational Integration support can not be uninstalled from RPT and RFT


From superseded fixes:

N/A

C) Enhancements

N/A

From superseded fixes:

N/A


Document change history


Version Date Description of change
1.1 09 January 2014 Revised Version
1.2 14 January 2014 Revised Version
1.3 14 January 2014 HP and Solaris builds removed
1.4 17 January 2014 Various changes
1.5 22 January 2014 Fix broken links, update SHA1, sort APARs and defects
1.6 23 January 2014 Added intergation support files
1.7 24 January 2014 Minor changes
1.8 1 April 2014 Minor changes - APAR's list updated (IV54890)


















[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5MD2","label":"Tivoli Composite Application Manager for Transactions"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 April 2014

UID

isg400001731