Sunday, January 1, 2012

A new year

It's been just under a year since I last posted...

I've resolved to update much more often this year!

Not that it will be hard, of course...

One of my first decisions will be how to continue with this blog. Perhaps the Tivoli stuff should be offloaded to an IBM managed blog?

I'll think about it during the week.


Monday, February 14, 2011

A new fix pack for TADDM -

A new fix pack is out for TADDM. This one doesn’t have anything really major, just lots of bugfixes.

A lot of them seem to center around Out Of Memory and Storage Errors during discovery or just having the discovery engine or console hanging.

Unless you’ve got specific problems, there’s no reason to get excited over this one.

On the other hand, TADDM 7.2.1, which will lots and lots of NEW shiny features, should be coming out quite soon.

I wonder if anyone is (a) reading this and (b) as excited as I am about it :)

-- Robert

Monday, January 17, 2011

Astronomy Picture of the Day : 2011 begins

After just under a year without new classical content, here are a few new Astronomy Pictures of the Day with classical content: - Night and Day above Almost Planet Sounio - Quadrantids over Qumis - The Antikythera Mechanism

-- Robert

Sunday, January 16, 2011

Direct upgrade from OMEGAMON Platform 350/360 to the current IBM Tivoli Monitoring release is not supported

Recently I encountered this error while installing support files on the TEPS together with a colleague.

At first we thought that perhaps it was a problem with the files we had downloaded, but trying to reinstall something that had just succeeded failed with the same message.

The cause of the problem seems to be a corruption in the file

Replacing it with the .bck file (which resided in the same directory) solved the problem.

Well, I haven’t posted in quite a while… but I’m back!
-- Robert

Tuesday, July 13, 2010

Extended Attributes Sensor

When using TADDM, you will probably come across a case where you want to extract information which TADDM does not do out of the box.

For example, you want to record the date on which the antivirus was last updated on each server.

The extended attributes feature enables you to add a field to those TADDM recognizes. The Custom Server option enables you to run OS commands and scripts and populate them.

However, writing a script that extracts the data can be time consuming – this isn’t what we want to be doing. Populating the extended attributes is also a bit more complex than populating regular ones.

Fortunately, there are a number of shortcuts. The DeveloperWorks TADDM wiki has a sensor which will read a config file, create the extended attributes and populate them when TADDM discovers the relevant computer. All you need to do is enter the attribute name and the registry key (or WMI object, etc…) in the config file.

Extended Attributes Sensor and Tools

I used it today and when it runs, it’s a big timesaver.

However, I did have to tweak a few things for it to run on TADDM 7.2FP1 on Windows. In case this helps you, here is what I did:

  • in the file ea_cli.bat, I changed the line
    @../support/bin/jython_coll.bat ea_cli.jy %*
    @../support/bin/jython_coll.bat ea_cli.jy %*
  • in the file, I changed the line
    from import IpUtils
    from import IPv4Utils
  • in the file, I changed the line
    from import JdbcConnectionFactory
    from com.collation.topomgr.util import JdbcConnectionFactory

Without the first change, nothing works. The second and third changes are because I got the error “ImportError: no module named ” when I ran the script.

Another useful sensor is this generic sensor.

-- Robert

Caesar’s Birthday

Today, July 13th, is the birthday of perhaps the most famous person who ever lived; Gaius Julius Caesar.

How many of us will be remembered for over 2,000 years? (this week, might not work in the future)


-- Robert

Thursday, May 6, 2010

Error 500: system#notboundexception

There are a number of reasons to encounter the Error 500: system#notboundexception message in your browser windows when you try to access a Maximo/TPAE/CCMDB/TSRM/EAM/etc system after a startup.

In general, the cause of the problem is that the application cannot connect to the database properly, for whatever reason.

I encountered the problem this week when I visited a customer’s test site. I could not login to the system, until I realized that I had been directed to an old server, which had it’s database tables truncated!

-- Robert