IBM Tivoli Composite Application Manager for Transactions Transaction Tracking 7.4 Interim Fix 15 README Tivoli Composite Application Manager for Transactions 7.4.0.0 7.4.0.0-TIV-CAMTT-IF0015 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.
   This can occur if the upgrade process were terminated prematurely. 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_|upgrade_date|.
2. The Transaction Reporter is not starting (Windows).
   Additional manual step is required during upgrade. See Installation Information section regarding the change in database schema and the process to upgrade existing data.
3. The Transaction Reporter is missing its historic data on startup (eg baselines and topology).
   This can occur if the upgrade process were terminated prematurely. 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 (xLinux and zLinux).
   Additional manual step is required during upgrade. See Installation Information section regarding the change in database schema and the process to upgrade existing data.

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

Transaction Reporter agent (TO)

1. Stop the Transaction Reporter agent
2. Backup the following files and directories (examples show AIX as an example, Simlar files/directories exist for other architectures (except Windows):
   • |ITM_HOME|/aix536/to/bin/ktocma
   • |ITM_HOME|/aix536/to/bin/todata/ (see Note below)
   • |ITM_HOME|/aix536/to/bin/to_config.jar
   • |ITM_HOME|/aix536/to/lib/libsql2.a
   • |ITM_HOME|/aix536/to/lib/libtransport.a
   • |ITM_HOME|/aix536/to/lib/libttapi.a
   • |ITM_HOME|/aix536/to/lib/libttcommon.a
   • |ITM_HOME|/aix536/to/lib/libttira.a
   • |ITM_HOME|/config/kto_config.ini
   • |ITM_HOME|/config/to.ini
   • |ITM_HOME|/config/to_dd.properties
   • |ITM_HOME|/InstallITM/plugin/plugins/plugin_to_comp-to_all_1.jar
   Note: The installer will attempt to rename the todata directory during installation
3. Run slibclean to unload any unused modules.

CICS TX Data Collector

1. Stop the CICS TX Data Collector agent
2. Backup the |ITM_HOME|/aix533/t7 directory
3. Run slibclean to unload any unused modules.

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 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.15'. The Transaction Reporter Build number is 5071. The CICS TX Data Collector Build number is 4893.

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.

CICS TX Data Collector

1. Reconfigure the T7 agent.
2. Start the T7 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).
   |ITM_HOME|/aix536/to/bin/todata_YYYYMMDDTHHMM
   Known issue (Internal Reference RTC 23333): On Windows, the installation process does not automatically rename todata directory. Rename |ITMHOME|\TMAITM6\todata to a backup directory before restarting the TO or updgrading the data.
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 |ITM_HOME| |InputDirectory| |OutputDirectory|
   Note: This tool will require the locations of:.
   1. ITM_HOME
   2. The input directory containing the data to migrate (see step 1)
   3. The output directory: e.g. |ITM_HOME|/aix536/to/bin/todata
   
   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
   1. AIX: LIBPATH=|ITM_HOME|/aix536/to/lib:|ITM_HOME|tmaitm6/aix536/lib
   2. xLinux: LD_LIBRARY_PATH=|ITM_HOME|/lx8263/to/lib:|ITM_HOME|/tmaitm6/li6263/lib
   3. zLinux: LD_LIBRARY_PATH=|ITM_HOME|/ls3263/to/lib:|ITM_HOME|/tmaitm6/ls3263/lib
   4. Solaris: LD_LIBRARY_PATH=|ITM_HOME|/sol293/to/lib:|ITM_HOME|tmaitm6/sol283/lib
   5. Windows: PATH=%PATH%;C:\IBM\ITM\GSK7\lib
4. Wait for data to be migrated.
5. Known Issue (Internal Reference RTC 23334): For zLinux and xLinux, the 'MetaData.xml' does not automatically get copied from the bin/todata_YYYYMMDDTHHMM/topology directory to the output directory.
   It will need to be 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:

N/A

From superseded fixes:

N/A

B) Additional Non APAR Defects:

Internal Reference RTC 21225: T5 causes TO to stop aggregations.
Internal Reference RTC 21225: TO crashes if it recieves more than 20 periods (caused by T5).
Internal Reference RTC 22385: Database update tool not migrating interactions data correctly.

From superseded fixes:

N/A

C) Enhancements


From superseded fixes:

From 7.4.0.0-IFix5: