My PMR to IBM Tivoli support

I’d be surprised if there wasn’t already an ER for this, but if you
don’t mind, please submit one.

Do you know if anybody else has asked or criticized this major
limitation.

Its hard to believe that there isn’t something that emulate what a
simple one line script would accomplish.

In the ER, I would expect support for perl regex pattern, where patterns
can be indexed to return the matching index as a displayable value.

match process string against /opt/IBM*\s+(\S+java*\)s+server1 pattern and return pattern matching (\S+java*\)

IBM’s Response

Yes, we already have an ER opened for this case, please note down the
request number: MR0108092213

****

ITM 6 has limitations when monitoring processes.

Customer needs to monitor processes with very long names, in this case
the WebSphere NodeAgent process with 4999 characters. The unique string
“nodeagent” is at the very end of the process name and the Unix OS agent
cannot find this process: The attribute command_name is limited to 100
characters and for command_name_U to 768 Bytes.
Cust needs a possibility to monitor such long process names using the
standard ITM 6 OS agent.

****

It is already a recognized request. You can follow up on the progress of
the request with your IBM Rep. Please let me know if you have any other
questions.

Obtaining Product Codes for IBM Tivoli Monitoring (ITM v6)

Local method:

Parse the proddsc.tbl file on a UNIX/Linux system to get the list by doing this:

UNIX
awk -F\| '/^[^*#]/ {print $1,$2}' ${CANDLEHOME}/registry/proddsc.tbl | sort | uniq


Or, IBM’s site http://www-01.ibm.com/support/docview.wss?rs=2366&context=SSZ8F3&dc=DB520&dc=DB560&uid=swg21265222&loc=en_US&cs=UTF-8&lang=en&rss=ct2366tivoli

Par for the course with IBM Tivoli’s porting of aqcuired products and their attempt at integrating them together, the ITM Agent for the a Netcool’s Omnibus  does not install in the expected $CANDLEHOME.

IBM has opened an enhancement request based on the PMR I opened. My workaround below.

Problem title
TEMA for Omnibus does support optional $CANDLEHOME paths
.
Problem description Read the rest of this entry »

Not all of them mind you, but some important ones none-the-less:

• KFW_STARTJVM=N
• KFW_USE_EMBEDDED=Y
• KFW_EWAS_SERVER_PID_FILE=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\logs\ITMServer\ITMServer.pid
• KFW_EWAS_STARTSERVER_SCRIPT=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\bin\startServer.bat
• KFW_EWAS_STOPSERVER_SCRIPT=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\bin\stopServer.bat

I verified the following by modifying all the variables in my %CANDLEHOME%\CNB\kfwenv file where numerical values like ports and max where incremented by one, and the string vlaues had _XXX_ inserted

The modified kfwenv was backed up, then I reconfigured the TEPS and ran a diff on both files, and the above variables are the resulting default values.

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

Over the past 10 years of consulting, I’ve come up with various scripts that others would find useful: perl, shell and otherwise, including vbscripts for windows WMI and ITM5.x Resource Model visitTrees.

As I get around to organizing this blog, I’ll make them available in some kind of structure.

Go to the Scripts Tag