| Author |
Message
|
| Maloum |
 Posted: Wed Feb 21, 2007 2:23 am Post subject: MQ filters |
 |
|
Newbie
Joined: 21 Feb 2007
Posts: 2
|
Hi All
i m a new to MQ we need to implement a filter that extract messages from queu regarding certain conditons. but i dont know where i can set up those filters . we are using dotnet 2.0 . can any one suggest some thing please ?
Thanks
Moncef |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Feb 21, 2007 2:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Firstly, are you really using MQ Everyplace or have you posted this in the wrong forum?
Secondly, assuming you're using the base product it only really allows for messages to be retrieved by specific identity, but your post is a bit fuzzy on what you're trying to achieve. Have you seen a specific reference to an MQ feature which you're interpreted as a "filter" that you could post a link to? Or post more detail about what you're trying to do?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Maloum |
| Posted: Wed Feb 21, 2007 3:23 am Post subject: |
|
|
Newbie
Joined: 21 Feb 2007
Posts: 2
|
hi
first : i probably made a mistake by posting my quesrion in this stream ...sorry.
second:i found something about MQSeries Integrator, were you can create filters to let you check messages in a queu and take only the ones you need .
i need to filter the messages based on the content not the header (the harder dont content the datas that prmit filtring)
i think i need to install MSQI and try to learn a little bit more about it , can anyone confirm me this point please??
thanks
Moncef |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 21, 2007 3:28 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are right. You will need to implement mqsi (or Websphere Message Broker or some similar product) to act on messages depending on content. I see it much less as filter and a lot more as content dependant routing...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 21, 2007 3:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Okay, I think you did post this in the wrong place - don't sweat it, happens to us all, a passing moderator will fix it in time. 
MQSI in now called Message Broker, it does provide significant functionality to work with messages based on content but does not display the kind of "out of box" filtering I think you mean. Developing a flow within WMB to sort messages on a queue so that they are then presented to the relevent application would be a straightforward development task, but still a development task.
WMB does not support .NET - you can access the queues of the base MQ product using .NET but the flows are in ESQL or Java (in the latest version).
I think learning a little more about the capabilities of the product and how it can best fit your needs is an excellent idea. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 21, 2007 3:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
NO, you do NOT need to implement WMB for this.
WMB allows for content-based filtering of SUBSCRIPTIONS, not "messages on a queue". And it's a design point to decide what information should be in the topic-hierarchy and what information should be in content-filters on the subscription.
Queues should, in general, not need to be filtered. It can be a good design pattern to implement a light-weight router, to separate different parts of an application from each other and isolate them from the rest of the enterprise.
But generally, every program that reads from a queue should be designed to process every message on a queue, and there should be a different queue for every program!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 21, 2007 3:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
I see it much less as filter and a lot more as content dependant routing...
|
Nice - wish I'd thought of that phrase..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 21, 2007 3:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
WMB allows for content-based filtering of SUBSCRIPTIONS, not "messages on a queue". |
It also allows for message flows with Filter nodes to segrigate messages by content, even if not possessed of topic information.
| jefflowrey wrote: |
Queues should, in general, not need to be filtered... generally, every program that reads from a queue should be designed to process every message on a queue |
The exception that proves this rule (and it's a very good design rule) is a program that listening for a specific reply by correl id.
| jefflowrey wrote: |
| there should be a different queue for every program! |
Indeed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 21, 2007 5:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Vitor wrote: |
| jefflowrey wrote: |
WMB allows for content-based filtering of SUBSCRIPTIONS, not "messages on a queue". |
It also allows for message flows with Filter nodes to segrigate messages by content, even if not possessed of topic information |
Filter nodes do not allow you to cherry-pick messages off a queue based on the contents of the message.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 21, 2007 5:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| Vitor wrote: |
| jefflowrey wrote: |
WMB allows for content-based filtering of SUBSCRIPTIONS, not "messages on a queue". |
It also allows for message flows with Filter nodes to segrigate messages by content, even if not possessed of topic information |
Filter nodes do not allow you to cherry-pick messages off a queue based on the contents of the message. |
Absolutely not, and it was not my intention to suggest otherwise. My point was it does allow an Input node to process all the messages off a queue, cherry pick certain of them by content to one Output node and the remainder to another destination (or destinations via further filters). This can be done even if the messages are not published.
I do accept this does mean all messages on the original input queue are read, and they are not cherry picked with unmatched messages remaining on the original queue. I did not intend to suggest anything different at any time.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
