|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
JMS Publish/Subscribe with Remote WMQI/WBIMB Pub/Sub Broker |
« View previous topic :: View next topic » |
Author |
Message
|
jsware |
Posted: Fri Nov 12, 2004 2:49 am Post subject: JMS Publish/Subscribe with Remote WMQI/WBIMB Pub/Sub Broker |
|
|
 Chevalier
Joined: 17 May 2001 Posts: 455
|
I want to setup a JMS environment that enables application to publish messages to a WMQI/WBIMB PubSub Broker. I do not want to use base MQ PubSub.
The JMS application will run on QMGRA and the PubSub Broker runs on QMGRB.
I know that I need to run the MQJMS_PSQ.mqsc script to create the JMS system queues, but I am not sure where they should be run. Do I create these queues on QMGRA (where the JMS app runs) or do I create them on QMGRB (where the pubsub broker runs) or is there a combination.
The documentation is not particularly clear and all the examples I can find use base MQ pubsub rather than a WMQI/WBIMB broker. _________________ Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Nov 12, 2004 6:17 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
If I understand what you want to do, you'll have to do a combination of both. Some of the queues will have to exist on the broker machine and need to be defined there. However, the subscriber will need to send messages to them and you'll need to define remote defintions on the subscriber to get over to the broker. You'll have the opposite situation for queues that need to exist on the subscriber machine needing to have remote definitions on the broker machine.
You'll also have to set up your xmit queues and channels to move the messages between the two qmgrs. |
|
Back to top |
|
 |
jsware |
Posted: Wed Nov 17, 2004 9:14 am Post subject: |
|
|
 Chevalier
Joined: 17 May 2001 Posts: 455
|
All I needed to do was create the SYSTEM.JMS.* queues on my local qmgr. When setting up the topic connection factory, it tell it the BROKERQMGR attribute and it puts things onto the default stream queue on the remote queue manager which puts them on the xmitq queue of the same name.
That was easy.
However, I notice that JMS seems to want a response from the broker. Is it possible to configure JMS so that it does a fire and forget message? I don't want JMS applications failing if we recycle the broker, I want messages to build up on the XMITQ and use MQ's assured delivery of messages. I can't see from the TCF/topic definitions anything that suggests this can be configured. _________________ Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|