IBM Tivoli Composite Application Manager for Transactions Transaction Tracking 7.4 Interim Fix 19 README Tivoli Composite Application Manager for Transactions 7.4.0.0 7.4.0.0-TIV-CAMTT-IF0019 Readme

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/support/fixcentral/

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

This upgrade for ITCAM for Transactions Transaction Tracking may be applied to the following base versions.

• 7.4.0.0 IFIX 1 for AIX (7.4.0.0-TIV-CAMTT-AIX-IF0001)
• 7.4.0.0 IFIX 1 for xLinux (7.4.0.0-TIV-CAMTT-LINUX-IF0001)
• 7.4.0.0 IFIX 1 for zLinux (7.4.0.0-TIV-CAMTT-LINUX-IF0001)
• 7.4.0.0 IFIX 1 for Solaris (7.4.0.0-TIV-CAMTT-SOLARIS-IF0001)
• 7.4.0.0 IFIX 1 for Windows (7.4.0.0-TIV-CAMTT-WINDOWS-IF0001)

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

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

1. The Transaction Reporter agent does not start. Logs indicate schema is incompatible.
   See Installation Information section regarding the change in database schema and the process to upgrade existing data.
   Note: The installer will rename the old todata to todata_.
2. The Transaction Reporter is missing its historic data on startup (eg baselines and topology).
   See Installation Information section regarding the change in database schema and the process to upgrade existing data.
3. The Transaction Reporter is not starting (Windows).
   See Installation Information section regarding the change in database schema and the process to upgrade existing data.
4. The Transaction Reporter does not show the old data
   See Installation Information section regarding the change in database schema and the process to upgrade existing data.
5. the toUpgradeTool fails on startup with segmentation fault.
   Ensure the target directory, where you are trying to migrate the data to, is empty.

There are no known limitations.

Prior to installation

Check and be aware of all releases of ITCAM for Transactions:
http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Composite+Application+Manager+for+Transactions

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 a TT agent either on a computer by itself or on a computer with an installed TEPS, TEMS, and/or portal. If you install a TT 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 the TT agents on a computer by themselves, the ITM agents and infrastructure do not need to be stopped.

Installing

For latest information on installation, please visit:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.4.0.0/tt/dita/concept/kto_tools_in.html

Installing Transaction Tracking
This maintenance package is applied directly to the Tivoli Enterprise Management Agent (TEMA).

On Windows systems, extract the files from the archive and double-click WINDOWS\setup.exe. Follow the prompts to install the update.

On UNIX systems, extract the installer from the archive using the tar -xvf <filename.tar> command. Then, execute the installer using the ./install.sh command. Follow the prompts to install the update.

For more information consult the following online documentation:
Installing Transaction Tracking on Unix systems

Performing the necessary tasks after installation

A successful installation sets the TT version to 7.4.0.0. Ensure that the version of the Transaction Reporter agents in the MTEMS is '07.40.00.19'. The Transaction Reporter Build number is 5273.

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

Transaction Reporter agent (TO)

1. Reconfigure the TO agent.
   The 'History' configuration section have been split into separate 'History' and 'Baseline' sections. New configuration items for this change are BASELINE_PERIOD_MINUTES, BASELINE_PERIOD_COUNT and BASELINE_CALCULATOR.
   Configuration items HISTORY_PERIOD_MINUTES and HISTORY_PERIOD_COUNT have been replaced with KHD_HISTRETENTION (Hours).
   Ensure that you reconfigure the Baseline settings to the desired settings as old settings may not be migrated. Note: Do not change the Baseline Period Minutes settings. All 3 supported Baseline Calculators are hourly based and should be left at 60 minutes.
2. Remove todata if it exists by removing the following directory (AIX location shown):
   |ITM_HOME|/aix536/to/bin/todata
   Note: This directory should have already been renamed by the installer.
   Note: The existing todata data (from previous versions) is incompatible with this software version.
Migrate the existing data: See instructions below Remove the backup directory ONLY once confident that it is no longer required.
3. Start the Transaction Reporter agent.

Migrate Existing Transaction Reporter Agent Data:

1. Check for the backup location of the old data. The existing todata directory is renamed during installation (time stamped).
   Note: Windows: This may not work for Windows so a manual rename should be done before restarting the TO or updgrading the data.
   |ITM_HOME|/aix536/to/bin/todata_YYYYMMDDTHHMM
2. Rename/Backup the todata directory if this has not been done by the installer.
3. Run the upgrade tool located in the location:
   |ITM_HOME|/aix536/to/bin/toUpgradeTool
   Note: This tool will require the locations of:.
   - ITM HOME
   - the input directory containing the data to migrate (see above step)
   - the output directory: |ITM_HOME|/aix536/to/bin/todata (default for KTO agent)
   Example: toUpgradeTool /opt/IBM/ITM /opt/IBM/ITM/aix536/to/bin/todata_201412011200 /opt/IBM/ITM/aix536/todata
   Important: Make sure the output directory (e.g. todata) is empty
   Important: Make sure the KTO agent is NOT running during the, especially if the output directory is todata (ie KTO's output directory)
   Important: Make sure there is enough disk space. Check how much room |todata_source| is taking, you will need 2.5x that free during the upgrade process.
   Note: If your todata directory is large, this could be an extremely time consuming process. You can monitor the progress by see the file size of [history|warehouse|baseline].db growing. For example as history.db ~3.2GB resulted in files ~3.9GB and took 1 hour to convert. The speed of this operation is highly dependent on the speed of your I/O subsystem.
   Note: This tool may require the library path to be set:.
   - Some of the paths below may vary slightly depending on you architecture, install location and ITM version
   - AIX: LIBPATH==|ITM_HOME|/aix536/to/lib:|ITM_HOME|tmaitm6/aix536/lib
   - Linux: LD_LIBRARY_PATH=|ITM_HOME|/lx8263/to/lib:|ITM_HOME|/tmaitm6/li6263/lib
   - zLinux: LD_LIBRARY_PATH=|ITM_HOME|/ls3263/to/lib:|ITM_HOME|/tmaitm6/ls3263/lib
   - Solaris: LD_LIBRARY_PATH=|ITM_HOME|/sol293/to/lib:|ITM_HOME|tmaitm6/sol283/lib
   - Windows: PATH=%PATH%;|GSKit_HOME|\lib;|ITM_HOME|\TMAITM6\tosupport
   - Windows Example: PATH=C:\IBM\ITM\TMAITM6\bin;C:\IBM\ITM\GSK8_x64\lib;C:\IBM\ITM\TMAITM6\tosupport
4. Wait for data to be migrated.
5. For zLinux and xLinux: The 'MetaData.xml' may not get copied from the bin/todata_YYYYMMDDTHHMM/topology directory to the output directory.
   If this is the case it will need to manually copied. If this is not done the TEP will not show the old data or the topology for the TO once it is restarted.
6. Backup the old todata directory (see step 1) if required and remove it from the current install area.

Troubleshooting installation problems from the Support site

For latest information on troubleshooting, please visit:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.4.0.0/tt/dita/tsg/concept/kto_ts_oview.html

Uninstalling if necessary

For latest information on uninstallation, please visit:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.4.0.0/tt/dita/concept/kto_tools_un.html

The Secure Hash Algorithm 1 (SHA1) checksum of the image is as follows:

A) APAR Content:

IV66334 TO spends too long reading metadata.xml
From superseded fixes:

N/A

B) Additional Non APAR Defects:

RTC 21225: T5 causes TO to stop aggregations.
RTC 21225: TO crashes if it recieves more than 20 periods (caused by T5).
RTC 22385: Database update tool not migrating interactions data correctly.
RTC 25207: toUpgradeTool does not work on xLinux when used to upgrade history.db > 3GB
From superseded fixes:

N/A

C) Enhancements


From superseded fixes:

From 7.4.0.0-IFix5: