IBM Tivoli Composite Application Manager for Transactions Response Time 7.4 Fix Pack 2 README Tivoli Composite Application Manager for Transactions 7.4.0.0 7.4.0.0-TIV-CAMRT-FP0002 Readme

To download this update, you must first login to IBM Fix Central. Once logged in, you may select from the individual download packages. Note - The image of Tivoli Integration Support and Rational Integration Support(RIS) are packaged in Windows image 7.4.0.0-TIV-CAMRT-Windows-FP0002.zip.
http://www.ibm.com/support/fixcentral/

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

This upgrade needs to be applied to T3, T5 and T6 agents where the version of ITM framework (ax on Linux/Unix, GL on windows) on the agent is equal to or higher than v6.3 FP7. If the condition is not true, you MUST NOT apply this fixpack.

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

• 7.4.0.0
• 7.4.0.1

It's a cumulative upgrade; any updates in the following releases are included in this upgrade.

• 7.4.0.1
• 7.4.0.1 - IF0001
• 7.4.0.1 - IF0008
• 7.4.0.1 - IF0011
• 7.4.0.1 - IF0014
• 7.4.0.1 - IF0016
• 7.4.0.1 - IF0019
• 7.4.0.1 - IF0022
• 7.4.0.1 - IF0023

Installing

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

• AIX : 7.4.0.0-TIV-CAMRT-AIX-FP0002.tar
• Linux : 7.4.0.0-TIV-CAMRT-Linux-FP0002.tar
• Windows : 7.4.0.0-TIV-CAMRT-Windows-FP0002.zip
• Solaris : 7.4.0.0-TIV-CAMRT-Solaris-FP0002.tar

1. Extract the 7.4.0.0-TIV-CAMRT-Windows-FP0002.zip file to a temporary directory (i.e. C:\temp\7.4.0.0-FP0002).
   
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.4.0.0-FP0002\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.4.0.0-FP0002\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.4 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:
   Perform a silent install of a monitoring agent (Windows)
   
4. RESTART THE COMPUTER.
   After the installation of the upgrade of a TEMA in Windows, it is necessary to restart 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 linux upgrade package and extract it to a temporary directory (i.e. /tmp/7.4.0.0-FP0002).
      
   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.4.0.0-FP0002/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, respond "2" to the following option.
      Do you want to check prerequisites for the above components? [ 1=Yes, 2=No ; default is "1" ] ?
      
      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, 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/Linux environments:
      Perform a silent install and configuration for a monitoring agent (UNIX or Linux)
      
   
   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 are 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
   
   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


   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


   
   Rational Integration Support
   
   This maintenance vehicle also provides an updated Rational Integration Support 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 RIS installation instructions:
   Installing integration support for Rational Performance Tester
   Installing integration support for Rational Functional Tester
   
   

Performing the necessary tasks after installation

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

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

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

When RIS of FP2 is applied on RPT,
Version: 7.4.0.2
Builde id: 201710120127

The Version and Build id value information shown in Rational Performance Tester menu 'Help' -> 'About Rational Performance Tester' -> 'Rational Performance Tester Installation Details' -> 'Features' -> Provider 'IBM Tivoli'

The version of JREs for T6 agent can be obtained through following steps:
Check version number of JRE 1.6, for example
> c:
> cd c:\ibm\itm\tmaitm6
> java60\jre\bin\java.exe -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr16fp50-20170814_01(SR16 FP50))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 x86-32 jvmwi3260sr16fp50-20170718_356955 (JIT enabled, AOT enabled)
J9VM - 20170718_356955
JIT - r9_20170718_356955
GC - GA24_Java6_SR16_20170718_0955_B356955)
JCL - 20170812_01

Check version number of JRE 1.7, for example
> c:
> cd c:\ibm\itm\tmaitm6
> java70\jre\bin\java.exe -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build pwi3270sr10fp10-20170726_05(SR10 FP10))
IBM J9 VM (build 2.6, JRE 1.7.0 Windows Server 2008 R2 x86-32 20170718_357001 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR10_20170718_1208_B357001
JIT - r11_20170718_357001
GC - R26_Java726_SR10_20170718_1208_B357001
J9CL - 20170718_357001)
JCL - 20170725_01 based on Oracle jdk7u151-b14

Check version number of JRE 1.8, for example
> c:
> cd c:\ibm\itm\tmaitm6
> java80\jre\bin\java.exe -version
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 8.0.5.0 - pwi3280sr5-20170905_01(SR5))
IBM J9 VM (build 2.9, JRE 1.8.0 Windows Server 2008 R2 x86-32 20170901_363591 (JIT enabled, AOT enabled)
J9VM - d56eb84
JIT - tr.open_20170901_140853_d56eb84
OMR - b033a01)
JCL - 20170823_01 based on Oracle jdk8u144-b01

Troubleshooting installation problems from the Support site

For more detailed information, refer to the Troubleshooting Guide:
https://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/rt/TSG/rt_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.

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.

The Secure Hash Algorithm 1 (SHA1) checksum of the images are as follows:
SHA1(7.4.0.0-TIV-CAMRT-AIX-FP0002.tar)=74dcf64b9bbacb00066f81ff08d2704cdb95d4be
SHA1(7.4.0.0-TIV-CAMRT-Linux-FP0002.tar)=70365b4c4f34980b423e16b525055280688aec06
SHA1(7.4.0.0-TIV-CAMRT-Solaris-FP0002.tar)=74abd464f80ae028eb7e7a9288eb5a4be6f7461d
SHA1(7.4.0.0-TIV-CAMRT-Windows-FP0002.zip)=bc4450b793cb06c8c9c911f004afcb7cbf0d08bc

A) New Features:
N/A

From superseded fixes:
T6 - Supports Rational Performance Tester version 9.1.0.x

B) APAR Content:
IJ00026 PSIRT 9227 IBM SDK, Java Technology Edition Quarterly CPU - Jul 2017 - Includes Oracle Jul 2017 CPU
IV98604 CONTENT CAPTURE FAILED TO OPEN BY IE 11

From superseded fixes:
IV94339 T3, T5, T6 APP SUPPORT INCORRECT VERSION, RESULTING IN "APPLICATION SUPPORT MISMATCH" REPORTED IN TEP
IV93911 T3/T5/T6 AGENT ON LINUX CRASHES AFTER UPGRADING ITM FROM 6.3 FP06 TO 6.3 FP07
IV93568 URL and Status_Code attributes in WRT Transaction Instance Table can occasionally miss match on HTTP pipelining
IV87235 WRT terminates when processing persistent HTTP connection containing multiple requests and missing packets
IV88234 WRT network timing calculations not processed correctly for HTTP transactions containing a 100-continue expectation
IV76483 CHUNKS THAT START WITH CRLF ARE NOT PROCESSED CORRECTLY BY WRT
IV79325 WRT TCP Sequencer uses wrong payload length when packets are truncated
IV78532 kfcm120 on AIX can occasionally consume excessive kernel CPU resource without BPF optimization
IV77635 T3 NEEDS TO RETURN ALL DATA FOR HISTORY REQUEST
IV76481 CHUNKED POSTS WITH 100 CONTINUE ARE NOT PARSED CORRECTLY BY WRT
IV76849 WRT does not support IP frames tagged by more than one 802.1Q VLAN tag
IV76185 When Citrix Connection Failure Event or Citrix Create Window Failure Event happens, no Citrix Server Address shows in TEP Event record
IV86304 AMCE 7401 SLOW WITH LARGE ZIP FILES IN THE RFT AND RPT RUNTIME FOLDERS IN THE KT1DEPOT
IV85027 T3 applications are offline when failed to connect to TEMS
IV79637 KT6 Agent set wrong KT6_JAVA_HOME in Runtime Environment on Linux platform
IV78697 TEMS RECYCLE STOPS AMC STH FILE GENERATION
IV84400 PSIRT 5154 CODE BLUE [SE-2012-01] Broken security fix in IBM Java
IV77457 RIS7401 install - wrong message of unsupported version for RFT 8.6 and RPT 8.6
IV78180 Some information is missing in VP Failure Event on TEP
IV74161 When enable Content capture In Windows Platform, Content Capture zip files continue to generate without VP failure Event
IV72305 wfcrun32.exe must be restarted periodically, if not some unexpected VP failure will happen
IV73894 RIS: The VP added by ITCAM Test Editor has some problems, it will make the VP failure message be incorrect
IV76162 RPT script playback failed with error message Test virtual user setup failed. startStatus=-14

C) Additional Non APAR Defects:
31246 D - PSIRT ALERT: 9137 Open Source SQLite Vulnerabilities CVE-2017-10989

From superseded fixes:
31022 PSIRT ALERT : 7621 zlib Vulnerabilities
30818 PSIRT ALERT: 5934 xerces-C Vulnerability & possible mitigation
30922 PSIRT ALERT: 6888 Open Source SQLite SQLite Vulnerabilities
30420 PSIRT 5417 Open Source Apache Xerces-C XML parser Vulnerabilities - CVE-2016-0729
30644 Update ARM with newer version TRANS_5907 for xerces-c PSIRT
29817 T3 writes blank value to ORIGINNODE column when the AMC ISM table is being queried
85102 WRT stops showing data after 1 day running
28937 Fix buildWhereClause SQL insertion vulnerability in CTableManager
28390 kfcm120 segmentation fault on shutdown with incomplete SSL sessions
28813 WRT crash in CSpec_DecryptAESGCM()
28820 PSIRT 3528 IBM SDK, Java Technology Edition Quarterly CPU
29758 RPT Citrix playbacks timeout after starting new playbacks
25603 RIS: Default password incorrect when exporting a script using SSL
29347 Make RRT work well when the installation directory contains SPACE
25603 RIS: Default password incorrect when exporting a script using SSL
20392 RIS: RFT Export of script inside folder fails

D) Enhancements
N/A

From superseded fixes:
30645 kfcm120 allow support for multiple X-Forwarded-For headers
29954 Port PacketRateFrameChecker from tx_dev to 7.4 maint
28534 RFE67857 Add NTLM Secure Service Provider User Authentication Support for WRT