As a Tivoli consultant, I’ve had to tweak, torque and tune ITM v6 to fulfill requirements not met out of the box. Several of my clients have felt ripped off by IBM for having paid for a product billed as covering best practices out of the box, only to discover, there is significant development costs involved.

I’m going to itemize and update the shortcomings as I think or run across them, and in all fairness, update if ITM fills the void.

Situations

1. Attributes, values and situation specific data is not passed to the ‘Take Action” command
   • Typically this is passed in the shell’s environment
   • However, these important pieces of info ARE passed to the EIF
2. Inability to determine what situations are running on which systems, or reversed, inability to derive which situations are running on any particular system

Windows Agent

1. No regular expressions for directory/file matching

Unix Agent

1. No regular expressions for directory/file matching (Unix and Linux)

Oracle Agent (ITMfDatabases)

1. (<= v6.2.0) Does not detect listeners if dynamically configured

This is a brain-dead situation, but I’ve been bit by the “ITM Connector” dialog box hiding behind the MTEMS configuration window.

Anytime you reconfigure the TEPS (Tivoli Enterprise Portal Server) via MTEMS (Manage Tivoli Enterprise Monitoring), sometimes that little box just hangs back there until you move the MTEMS window.

Very innocuous problem that isn’t really a problem, just an annoyance.

Tivoli MTEMS not responding or hangs