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.

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 »

Reference: http://help.mosso.com/article.php?id=180

Your script is calling for the “REMOTE_ADDR” and receives the IP of a server in front of one of our back-end servers. The web facing server is then passing the scripts output without giving the expected REMOTE_ADDR of the visitor. In order for your scripts to recognize that they are on a cluster and log the correct IP of your visitors, you will need to replace and add the code below.

For PHP:
Locate any lines of code that are similar to this snippet of code,
$_SERVER['REMOTE_ADDR'];
And replace it with this snippet of code,
$_SERVER['HTTP_X_CLUSTER_CLIENT_IP'];

For ASP:
Locate any lines of code that are similar to this snipper of code,
Request.ServerVariables(“REMOTE_ADDR”)
And replace it with this snipper of code,
Request.ServerVariables(“HTTP_X_CLUSTER_CLIENT_IP”)

My fix for this required a unix shell (if you’re on a Windows look at installing cygwin on your system.

# Ftp your web content down to your local system

$ for file in `find <path_to_files> -exec grep -l REMOTE_ADDR {} \;`; do base=`basename $file`; sed ‘s/REMOTE_ADDR/HTTP_X_CLUSTER_CLIENT_IP/g’ $file > /tmp/$base; grep HTTP_X_CLUSTER_CLIENT_IP /tmp/$base >/dev/null 2>&1 && grep REMOTE_ADDR $file && echo “Updated $base” && mv
/tmp/$base $file; done

# Then simply upload the changed files to your system.