RE: issues with ITM for BI (WebSphere MQ)

Hi Phillip,

 

Speaking from experience, regarding (1), check your endpoints to ensure you have an appropriate & compatible JVM installed & linked to ITMfBI/WSMQ.  If the endpoint is Windows, you can use the wdmprereq command to check this ... if the endpoint is Unix (any flavor) you have to manually check. 

 

For myself, I don't bother with checking at all, I just push out & link the JVM from the installation CDs without regard for any pre-existing JVM on the endpoint.  The reason for this seemingly risky behavior is because trying to validate existing JVMs and then linking them will almost always lead to trouble down the road -- i.e., if Tivoli changes their requirement for JVM version, which they have a couple times already, you cannot blindly upgrade the existing JVM because some other business application using that JVM may require the "back level" version ... I'm not prepared to verify & validate every application or tool on every server to ensure that it is 100% compatible with Tivoli's specified version of JVM, so to avoid conflict I push & link a JVM just for Tivoli. 

 

Please note that this is a lose-lose situation for all of us ... Tivoli's use of Java in this package has had consistently resulted in high overhead (high cpu & memory utilization) on endpoint servers just to keep Tivoli running.  Because of the potential incompatibility between JVMs, you are forced to have multiple installations which leads to even more overhead.  Every time any application (Tivoli or other) on the server changes requirements, you're at risk for swamping the box IMHO.

 

Regarding (2) and (3) ... well, I'm gonna go right back to (1) ... it's all JVM related in my view.  Fix problem (1) first, then let us know if problems (2) and (3) still exist.  :-)

 

 

hth,

 

John Guadagnino

Gap Inc.

-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx [mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]On Behalf Of Phillip Rhodes
Sent: Friday, February 25, 2005 1:53 PM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: [tme10] issues with ITM for BI (Websphere MQ)

Hi all, I have a couple of questions I'm hoping someone
can shed some light on for me.

I'm running TMF 4.1.1 with ITM 5.1.2, ITM for BI 5.1.1 and TEC 3.9, on a Win2K
server.  I have an endpoint running WebSphere MQ on Windows XP.  I've run the "Discover Queue Managers"
task on my TMR server and it did successfully locate the Queue Managers in question and I can do things
like list queues, start and stop queue managers, etc., from the Tivoli Desktop.

However...

1. If I distribute a monitoring profile with the Queue and/or Channel resource models
marked active, neither the Queue nor Channel RMs will start.  I get back a "retrying (110)"
message from both.

2. The QueueManager resource model starts (apparently) but I'm not convinced it ever does
anything.  In particular, there is an Indication for "Queue Manager Unavailable" in that RM.  But
if I stop Websphere MQ ( by any means, including manually killing the process), the indication never
seems to fire.  I never find an event in TEC based on that indication.  I've run wtdumprl to make sure
it isn't the case that it got sent but simply failed to parse due to a problem with the BAROC files, etc.
No dice.. it just isn't there.  Also, if I load Web Health Console and look at the status of the resource
model's, the QueueManager resource model always shows 100% health, no matter what.

3. Another bit of quirky behavior: if I stop MQ on the endpoint, the QueueManager icons in Tivoli Desktop
never switch to the "stopped' icons. They always show up as "running."  Maybe that's the expected behavior
but it seems odd to me.  


Anybody have any insight into any of these issues?


Thanks,

Phillip Rhodes
------------------------------------------------------------------
Pervasive Computing - RFID Server Development
E-Mail : prhodes-r/Jw6+rmf7HQT0dZR+AlfA@xxxxxxxxxxxxxxxx
Phone : (919) 486-1499
T/L       : 526-1499
-------------------------------------------------------------------