Fix Readme
Abstract
xxx
Content
Readme file for: 7.4.0.0-TIV-CAMTT-IF0009
Product/Component Release: 7.4.0.0
Update Name: 7.4.0.0-TIV-CAMTT-IF0009
Fix ID: 7.4.0.0-TIV-CAMTT-AIX-IF0009
Publication Date: 26 Sep 2014
Last modified date: 26 Sep 2014
Installation information
Download location
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.
| Product/Component Name: | Platform: | Fix: |
|---|---|---|
| Tivoli Composite Application Manager for Transactions | AIX | 7.4.0.0-TIV-CAMTT-AIX-IF0009 |
Prerequisites and co-requisites
The MDV contains a new data collector that is designed to utilise the Application Activity Trace (AAT) functionality of MQ 7.5.0.0:
- MQ AAT DC (KM0) requires MQ 7.5.0.0 or higher.
- KM0 should not be installed on a MQ Queue Manager that is already instrumented by KTH (i.e. pre-existing MQ Data Collector).
- There should only be one KM0 agent (or any other AAT consumer) per QueueManager. i.e. AAT Queue/KM0 can only support one monitor.
Pre-requisites
- ITCAM for Transactions 07.40.00.01+ - Transaction Reporter/Collector(KTO/KTU)
- Websphere Message Queue 7.5.0.0+
- See KNOWN DEFECTS, will require MQ Fixes when available.
- Websphere Message Broker 8.0.0.0+/9.0.0.0+
- ITCAM for Transactions - WMB Data Collector Build 161+ (included)
- See KNOWN DEFECTS for details.
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
Known issues
None.
Known limitations
Nodes on low traffic queues not showing up.
MQ AAT function means very low traffic queues might not generate tracking event in a timely manner (uncapped delay).Stitching does not work across MQ tracked across OS platforms
MQ Returned AAT has malformed fields, breaking Transactions Tracking Stitching when MQ Tracking applied across OS platforms.Topology Stitching between MQ and MB might be incomplete.
The MB DC collector was originally designed to work with the KTH MQ agent. Test has shown some cases where it does not properly stitch with the KM0 agent in the Transaction Reporter topology. WMB agent has been updated to work with both KM0 and KTH agents.Missing intermediary queues in Alias -> Remote -> Xmit -> QLocal scenario.
AAT reporting of destination/resolved queues leaves off the Remote queue in a 3 hop (Alias -> Remote -> Xmit) scenario. i.e. only show Alias -> Xmit.Installation information
Please see the included pdf documentation, "Tracking WebSphere MQ transactions.pdf", for all installation and configuration related tasks.
Additional information
The Secure Hash Algorithm 1 (SHA1) checksum of the image is as follows: 7.4.0.0-TIV-CAMTT-AIX-IF0009.tar 83a96de3d4d83ee758173de74afe8b7fa157910b
List of fixes
This interim fix delivers RFE41914.
Document change history
| Version | Date | Description of change |
| 1.0 | 30 Sep 2014 | Initial Version |
Was this topic helpful?
Document Information
Modified date:
30 September 2014
UID
isg400001929