ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Browse MQ queue via a Message Broker Flow

Post new topic  Reply to topic
 Browse MQ queue via a Message Broker Flow « View previous topic :: View next topic » 
Author Message
mchillin
PostPosted: Mon Sep 10, 2007 1:51 am    Post subject: Browse MQ queue via a Message Broker Flow Reply with quote

Novice

Joined: 27 Sep 2006
Posts: 16

Is it possible to browse a MQ queue using Message broker flow?

As far as I can see the MQInput and MqGet only allow reading of the queue and there isnt the possibility of browse.

It is important that this particular queue is only accessed via browse and it is monitored and used an alarm system.

I appreciate any advice you can give.

Regards.

Michael.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Sep 10, 2007 1:54 am    Post subject: Re: Browse MQ queue via a Message Broker Flow Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mchillin wrote:
It is important that this particular queue is only accessed via browse and it is monitored and used an alarm system.


What requirement are you meeting here? If a message on a queue indicates an event, why is WMB not going to respond to it by reading the message?

WMB is not an ideal monitoring solution. Monitoring software is better at that.

You might fudge it with a custom node, but that's a sledgehammer to crack a nut. Not sure how you'd stop the broker repeatedly browsing the message over and over & soaking resources either sitting here.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mchillin
PostPosted: Mon Sep 10, 2007 2:13 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2006
Posts: 16

The message that is in the queue indicates that an error has occurred, this idea of browsing this queue is to give information about the error but without interfering with the separate monitoring system, which is already already in place.


An additional problem here being that this runs in z/OS.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Sep 10, 2007 2:20 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mchillin wrote:
The message that is in the queue indicates that an error has occurred, this idea of browsing this queue is to give information about the error but without interfering with the separate monitoring system, which is already already in place.


So you're monitoring a queue which is already monitored?

I remain unconvinced this is a good idea, and you'll need custom code to achieve it. Possibly a node, I wouldn't necessarially recommend it.

But it's your system.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Sep 10, 2007 2:55 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

mchillin wrote:
The message that is in the queue indicates that an error has occurred, this idea of browsing this queue is to give information about the error but without interfering with the separate monitoring system, which is already already in place.


An additional problem here being that this runs in z/OS.

You should capture the error in the flow where it occurs through error handling and take the adequate steps there. There is no need to browse the error queue the way you described.

If there is you need this to be a human task not an automated one...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Mon Sep 10, 2007 2:59 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

fjb_saper wrote:
You should capture the error in the flow where it occurs through error handling and take the adequate steps there.


Or wherever the error is occuring - no one's actually said the "alarm" message is added by a failing flow.

But yes, it should be handled by the failing "application" or the existing monitoring.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Browse MQ queue via a Message Broker Flow
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.