MDB listens to a queue different from input queue in WAS5.1x

[Sam Gehouse]

I am using MDB (Message Driven Bean) under WAS5.1.2 for listening to messages put in a queue for P2P application. I put messages in a queue (e.g. Q1) and can successfully pick up messages from Q1 using MDB. I can successfully configure WAS for that.

For scalability purpose, the requirement is to put message in a queue (e.g. Q2). MDB should pick up those messages from a different queue (e.g. Q3).

MQ admin has configured the queues properly. As such, if messages are placed in Q2, they are successfully transferred from Q3. I can also verify it. I use MQ command to put messages in Q2. I use MQ command to successfully pick up same messages from Q3.

But I am having trouble configuring Q2-Q3 scenario in WAS. I know I have to configure ConnectionFactory, Queue and ListenerPort in WAS to accomplish Q2-Q3 scenario. But I think that certain parameters are different for Q2-Q3, as opposed to using the same queue (Q1).

Does anyone know specific WAS configurations for accomplishing Q2-Q3 scenario?

[Kyle Brown]

You just have to create a new Queue object in WAS (there are two Queues -- Q2 and Q3 but you can use the same ConnectionFactory). If you only have one MDB you only need one ListenerPort -- just make sure that it points at Q3 and not Q1.

If you've successfully created one Queue in the WAS Admin, then you can just follow the bouncing ball and create another one, right? The underlying queue name mapping to MQ will be different but that's about it.

Kyle