Dan,
If you are at WMQI v2.1 you could use the PROPAGATE function to put to
different queues within one compute node.
You would select each desired output queue via the following code:
--
-- Set Message Destination on LocalEnvironment
--
SET OutputLocalEnvironment.Destination.MQ.DestinationData.queueName
= "queue name";
At the end of the compute node use the RETURN function as follows:
--
-- Prevent default action to propagate message to output terminal at end of
compute node
-- by ending execution of esql.
--
RETURN false;
On the advanced tab of the compute node, you must set the "Compute Mode" to
"Local Environment And Message".
On the MQOutput node leave the "Basic" tab blank and select "Destination
List" under "Destination Mode" on the advanced tab. Also, under Message
Context, if you want to "Pass All", this does not work when using
"Destination List", you must instead use, "Pass Identity".
If you are at an earlier version, you could pass the message through a
series of Filter nodes, with the true terminal of each Filter node wired to
a different MQOutput node.
"Capodicci, Dan (CAP, MMF, ITSS)"
<[EMAIL PROTECTED]> To:
[EMAIL PROTECTED]
Sent by: MQSeries List cc:
<[EMAIL PROTECTED]> Subject: filtering
incoming messages....
Wednesday July 31, 2002 09:22 AM
Please respond to MQSeries List
Hi....
I may have an answer or two for this scenario myself but I was hoping to
get the best/correct answer instead....:)
Trimming a long story down to the details, I and a business partner are
exchanging info via an MQ link between us. He is using MQSI on his side to
receive the messages into a "custom" built message flow. The need has now
come up to send several different types of messages between the companies.
However, their flow can only handle the 1 message type it expects and at
this point altering that is not an option. At this point, we would like to
stay with just the one set of queues between us (input/output). Changing
the app on our side to put to many different queues is also not an option.
So, what I would like to do is put something in front of this message flow
to act as a traffic cop, i.e. message type 1, go here....message type 2 go
there....etc. so that I can just direct the messages that it expects to it
and peel the others off into a new message flow.
Any ideas on the easiest way to do this within MQSI?!? The messages are
being differentiated by a value placed in the MQMQ field "Message Type". I
thought of writing a simple "router" app to read the field and MQPut the
message into different MQInput nodes but was hoping there would be a
slicker/easier way to do this within MQSI(am just a relative novice in
MQSI!).
Thanks....
Dan....
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
