| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Publishing Multiple Topics |
« View previous topic :: View next topic » |
| Author |
Message
|
| rentonsa |
 Posted: Thu Oct 20, 2005 6:34 am Post subject: Publishing Multiple Topics |
 |
|
Newbie
Joined: 07 Oct 2004
Posts: 6
|
Documentation I have on WMQI 2.1 suggests that it's possible to publish a message to multiple topics by generating multiple
OutputRoot.MQRFH2.psc.Topics. There's no guidance as to how this is done though, and currently just building up a group using standard eSQL looping logic results in this:
'"SET OutputRoot.MQRFH2.psc.Topic[v_topicloop]
= InputRoot.XML.CSLDerivativeRT.TopicHeader.TOPIC
Failed to navigate to path element because it does not
exist. " (this is on the inputroot topic, doing it one to one accepts it fine).
Has anyone tried this before, and know if it really IS possible? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Oct 20, 2005 6:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I remember someone else asking about publishing to multiple topics, a while ago. (three to six months).
I don't remember the resolution, but I do remember wondering why.
Does it really matter if you publish one time to multiple topics instead of publishing multiple times to one topic? I'm quite sure that the subscribers won't notice the difference.
Shouldn't you reconsider your topic hierarchy if you need to publish to multiple topics? Or maybe reconsider your subscriptions to subscribe to wild carded topics rather than single topics...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rentonsa |
| Posted: Thu Oct 20, 2005 7:46 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2004
Posts: 6
|
Thanks for replying Jeff.
The reason for this is that we 'hoped' that by publishing multiple topics we wouldn't be putting multiple messages out, thus reducing the danger that some applications could get multiple instances of the same message.
Basically, we want to preserve the model, so the granularity that we send out is dealt with within topics, and apps just subscribe to them, and don't need to work out if it's a relevant message to keep within the code.
If our understanding is wrong, though, is it possible to generate a list of group identifiers within the "usr" folder? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 20, 2005 7:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| rentonsa wrote: |
| The reason for this is that we 'hoped' that by publishing multiple topics we wouldn't be putting multiple messages out, thus reducing the danger that some applications could get multiple instances of the same message. |
Why would this be a problem? If the app is subscribed on multiple topics, then presumably the app will be handling each topic differently. In this case, a message with multiple topics presumably has to be dealt with for every topic, not just for some topic - and thus has to be handled multiple times.
| rentonsa wrote: |
| Basically, we want to preserve the model, so the granularity that we send out is dealt with within topics, and apps just subscribe to them, and don't need to work out if it's a relevant message to keep within the code. |
But to what purpose do you need to publish a message on multiple topics? And how do you know each topic doesn't count as a "different" message (with the same content)?
| rentonsa wrote: |
| If our understanding is wrong, though, is it possible to generate a list of group identifiers within the "usr" folder? |
Again, I don't remember whether it's possible to publish on multiple topics... and I don't know without looking it up whether or not it's possible to generate a list of group ids within the usr folder.
And you really should reexamine your topic hierarchy and your assumptions about publishing on multiple topics.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rentonsa |
| Posted: Fri Oct 21, 2005 1:50 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2004
Posts: 6
|
We've decided to take the course of putting a repeating group of these items within the main payload, and letting the subscribing apps decide whether or not they want the messages by interrogation. Not the cleanest option, but viable.
Thanks again for the advice. |
|
| 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
|
|
|
|
