MQSeries.net :: View topic - Questions about content filter in both ACE and IBMMQ

liamf · Posted: Tue Jan 03, 2023 1:32 am Post subject:

Environment:
IBMMQ V9.2
ACE V11

Descriptions:
In my case, what i want is a filter base on message payload rather than header/properties, and i found the content filter fits well.

After read the documentation, here are some of my interpretations:
1.when using a subscription selector that's not a regular properties, the selector type would be changed to Extended. In this case, the MQ would retrieve an extended message selection provider to decided whether the message should be routed to the subscriber.

2.the extended message selection provider is bound to a topic in a specific way (the Namelists?).

3.the entire process goes like this:
Publisher send a message to a topic
-> the topic has one or more subscriptions with an Extended selector
-> the MQ will go find the extended message selection provider bound to this topic, and send the message to it (along with the subscription selector expression??).
-> the extended message selection provider will process the message and return to the topic (if success) or return a error code(if fail)

Questions:
1. Does my interpretations right? please let me know

2. What is extended message selection provider? Is it a messageflow? if it is a messageflow then what is the input node or as to say, how does it be announced?
3. How did MQ find the correct extended message selection provider in broker, bind with what?
4. In my opinion, the extended message selection provider is a common project in broker, and the params that it recieves contains messages and selector expression of each subcription, am i right?[/list]