| Author |
Message
|
| jangochi |
 Posted: Fri Mar 10, 2006 3:27 am Post subject: Make message available on 2 queues-design thoughts please |
 |
|
Novice
Joined: 10 Jan 2005
Posts: 14
Location: UK
|
Hi,
I am pondering over a particular design request from an application team, who requires a message put on a queue(by application) to be available at one more queue. In short, the same message needs to be available on two different queues, under 2 different queue managers. Since a GET may be used to retrieve both the queues, clustering can't be an option as physically all the messages won't be available on all custer queues. This is my undestanding.
Since JMS is used, I believe that distribution list is not an option. I feel that Pub/Sub can be used here. But is it worth going for such a simple requirement?
Mirror queue can also be handy in this case. Since there isn't a C complier on the server, compiling that exit can be a problem. Is it alright to compile the code using any free compiler like GNU and use? I am not sure how to handle this.
One more relevant point is that only MQ Client is available on the machine where the application put the message.
Any other ideas to fulfill this particular requirement? Appreciate your thoughts on this. I am on MQ6 on AIX 5 and the application uses WAS 6. |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Fri Mar 10, 2006 3:37 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi jangochi,
Why don't you simply connect to both the queue managers and put the message on both the queues 
Not very clear why your trying or thinking of so many options ??? Maybe I haven't got your exact requirement....
Regards. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 10, 2006 12:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jangochi wrote: |
| Any other ideas to fulfill this particular requirement? Appreciate your thoughts on this. I am on MQ6 on AIX 5 and the application uses WAS 6. |
Well well well.... have you looked into the JMS Engine and the SIBus as well as the connection from the SI Bus to MQ. This is one answer to your requirements.
The other would be to define the same qmgr and queues to your WAS cluster so that each appserver (WAS) will access the same queues on the same qmgr.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Mar 14, 2006 2:38 am Post subject: Re: Make message available on 2 queues-design thoughts pleas |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| jangochi wrote: |
| Mirror queue can also be handy in this case. Since there isn't a C complier on the server, compiling that exit can be a problem. Is it alright to compile the code using any free compiler like GNU and use? I am not sure how to handle this. |
As long as you are using a supported compiler, you'll be ok. |
|
| Back to top |
|
|
| jangochi |
| Posted: Wed Mar 15, 2006 9:53 am Post subject: |
|
|
Novice
Joined: 10 Jan 2005
Posts: 14
Location: UK
|
| elvis_gn wrote: |
Why don't you simply connect to both the queue managers and put the message on both the queues
|
Elvis, whenever a new WAS cluster gets added, this message needs to be available at queues present there as well. So, this option will require an application code change at each such additions, isn't it?
| fjb_saper wrote: |
Well well well.... have you looked into the JMS Engine and the SIBus as well as the connection from the SI Bus to MQ. This is one answer to your requirements. |
I believe you are referring to the WAS configuration changes by which we can add broker Profiles to the MQ Link. Unfortunately, I have no much insight to WAS6 configuration..I couldn't find a complete document explaining this thru google.. the WAS admin guide sounded a bit vague to me. I am leaning more towards an MQ pub-sub setup by which we can ensure message arrival in all subscription queues(global as well as local) by establishing a parent-child relationship across MQ brokers. Based on my understanding, for any new additions(queue managers), creation of a 'child' broker to the existing 'parent' broker and subscription to the relevant topics should guarantee delivery of publications to the new queues. I am not so sure if this will be the simplest approach.
| fjb_saper wrote: |
The other would be to define the same qmgr and queues to your WAS cluster so that each appserver (WAS) will access the same queues on the same qmgr. |
I am lost on this. Are you suggesting to use the messaging facility within WAS 6?  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 15, 2006 10:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| jangochi wrote: |
| fjb_saper wrote: |
The other would be to define the same qmgr and queues to your WAS cluster so that each appserver (WAS) will access the same queues on the same qmgr. |
I am lost on this. Are you suggesting to use the messaging facility within WAS 6? |
I'm fairly certain he was advocating configuring WAS to make client connections from all WAS app server instances to a single queue manager.
Of course, then you lose XA (unless you use ETC).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
