- Thanks received
- 15
-
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Websphere MQ Question
- Thread starter Moose423956
- Start date
- Thanks received
- 14
What platform?
My Experience is on i5 - this may or may not give you mileage.
Í normally assume that MQ is going to work - it is "guaranteed delivery"after all. However you can have a problem with your read process not taking stuff off the queue (if for instance it's had a bit of a barney and needs re-starting).
You can monitor this by checking the queue depth on your incoming queue - if it goes above a number you're not happy with throw an exception, either with an e-mail or with Tivoli.
My Experience is on i5 - this may or may not give you mileage.
Í normally assume that MQ is going to work - it is "guaranteed delivery"after all. However you can have a problem with your read process not taking stuff off the queue (if for instance it's had a bit of a barney and needs re-starting).
You can monitor this by checking the queue depth on your incoming queue - if it goes above a number you're not happy with throw an exception, either with an e-mail or with Tivoli.
- Thanks received
- 15
Hi MM. It's more of a general question about how best to monitor MQ once it's running, in case there are any channel errors, or messages get sent to the DLQ, and so on - anything unexpected really.
In the past I've installed it in a large global site where they use Tivoli/Maestro, but I'm now doing it in a single installation site at the moment, and I just want to make sure they can monitor the system fully once I've gone.
Do you have any recomendations? Do you use the supplied DLQ handler at all? How do you get MQ to send an email - via a batch process attached to a queue, maybe the DLQ itself?
In the past I've installed it in a large global site where they use Tivoli/Maestro, but I'm now doing it in a single installation site at the moment, and I just want to make sure they can monitor the system fully once I've gone.
Do you have any recomendations? Do you use the supplied DLQ handler at all? How do you get MQ to send an email - via a batch process attached to a queue, maybe the DLQ itself?
- Thanks received
- 14
Do you have any recomendations?
Not really for your situation, I've only ever been concerned with my channel of choice not the whole system.
Do you use the supplied DLQ handler at all?
Nope, sorry.
How do you get MQ to send an email - via a batch process attached to a queue, maybe the DLQ itself?
i5 MQ has lots of handy commands for finding queue depth, status etc. I'm not sure if these exist on other platforms, but I guess they must in some form or other.
The one I use/wrote monitors lots of other things in Midas (banking software I work on) and runs as it's own background job (akin to a service in windows land). It's this that chucks the exception mail using the SMTP server on the i5 itself if it finds anything amiss.
I'm sure you could easily write your own similar DLQ monitor for general exceptions, but be aware that all sorts of crap goes to the DLQ that may or may not be terminal.
Not really for your situation, I've only ever been concerned with my channel of choice not the whole system.
Do you use the supplied DLQ handler at all?
Nope, sorry.
How do you get MQ to send an email - via a batch process attached to a queue, maybe the DLQ itself?
i5 MQ has lots of handy commands for finding queue depth, status etc. I'm not sure if these exist on other platforms, but I guess they must in some form or other.
The one I use/wrote monitors lots of other things in Midas (banking software I work on) and runs as it's own background job (akin to a service in windows land). It's this that chucks the exception mail using the SMTP server on the i5 itself if it finds anything amiss.
I'm sure you could easily write your own similar DLQ monitor for general exceptions, but be aware that all sorts of crap goes to the DLQ that may or may not be terminal.
- Thanks received
- 2
- Thanks received
- 15
