| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQ Small Site - Monitoring |
« View previous topic :: View next topic » |
| Author |
Message
|
| Moose423956 |
 Posted: Thu Sep 20, 2007 8:05 am Post subject: WMQ Small Site - Monitoring |
 |
|
Newbie
Joined: 20 Sep 2007
Posts: 2
|
Hi folks. My first visit to this site, so bear with me.
I'm in the process of installing WMQ v6 onto a single Windows machine for a client. I've done lots of installs in a global client where they have Tivoli monitoring the system, but I've never done a small client before.
Can anyone recommend the best way for them to monitor MQ, and to be alerted if anything goes wrong. I mean in case there are any channel errors, or messages get sent to the DLQ, and so on - anything unexpected really.
I've been looking at the DLQ handler that comes with the product - does anyone use that?
Please point me to another thread if this has been discussed already. I've had a quick search, but time is of the essence. I'm there tomorrow, then that's it, they're on their own after that.
Cheers |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Sep 20, 2007 8:13 am Post subject: Re: WMQ Small Site - Monitoring |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Moose423956 wrote: |
I've been looking at the DLQ handler that comes with the product - does anyone use that?
|
Yes - though getting the procedures in place to back stop the rules by tomorrow (and indeed writing the rules) will be a challenge.
The "Monitoring MQ" manual sounds like a good place for you to be. There are also cheaper (and free) montoring tools than Tivoli. You'll find a list on Roger's site
www.capitalware.biz/mqseries
or some URL that looks like that - a search in the forum will turn in up.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 20, 2007 8:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think lots of people use the DLQ handler that comes with the product - merely because nobody wants to write their own.
I tend to avoid designing systems that need a DLQ Handler - merely something that alerts me if *anything* shows up.
The first question to ask is "Does the client have any system for alerting them of anything in their business now". It makes more sense to find out what the costs are of adding MQ capabilities to that than it does to uninformedly deciding to implement an entirely new system.
The second question to ask is "How much value does the client gain from the monitoring system", or in a different version of the same question - "What is the cost of assuming the risk of not having a system that alerts if things go wrong?"
Once you have those facts in place, you can decide what the cost-value proposition of monitoring is, and use that to decide what the investment should be and how to measure the ROI.
No matter what the cost of the actual software used to perform monitoring, there is still going to be costs to implement. So going for an open source system just because it's "free" doesn't mean that you won't be spending any money.
That said, likely the client won't want to outlay the costs of an enterprise monitoring system just to monitor one queue manager. The QFlex package from Netegrity may be an option here. Although I think I remember that their pricing model changed?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
