| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Channel exit to remove an RFH2 header. |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Thu Apr 05, 2007 6:31 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No, this seems to be straight forward pub/sub. The routing is the routing being done by the pub/sub broker, where it uses the topic to determine who gets a copy of the message.
dp111443 - the messages produced on the subscription queue are as identical to the published message as possible.
If you want to have the subscribers receive the messages withouth an MQRFH2, then you need to publish without an MQRFH2. That means that you are not using the normal means of instructing the Broker what topic the publication belongs to.
If you have a mix of subscribers, some who need MQRFH2s and some who don't... then you can look at using Subscription Points, and publish once with an MQRFH2 and once without.
Otherwise, you can reconsider the value you're getting out of using Pub/Sub in the first place. Pub/Sub and Point-to-Point are "equivalent", in that you can do the same things with either design (in fact Pub/Sub is built on top of point-to-point). It may be that you end up having what amount to very static subscriptions, and so you're not getting a lot of runtime value out of pub/sub.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| dp111443 |
| Posted: Thu Apr 05, 2007 7:13 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi,
Thanks for all the info... I'll sleep on it i think!!
just one question...when you mean subscription points or point-to-point.... do you mean MQ pub/sub (not broker)?
cheers,
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 05, 2007 7:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Subscription points are not the same as point-to-point messaging, and are only available with WMB. They're nominally like base MQ pub/sub STREAMS, but not really.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 05, 2007 1:44 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20769
Location: LI,NY
|
| dp111443 wrote: |
Hi Vitor, pretty much yes!
the only thing i should clarify is when the message comes into the broker there is no RFH2 header. We basically build the topic tree in the broker based on some content of data.
then publish it using publish node.
the subscription is on a non-RFH2 aware app.
and yes we do want to publish the message without the header.
thanks, |
You have basically 3 choices:
a) have the legacy app use XMS
b) have the legacy app just strip the RFH but remember to keep the format and encoding info from the RFH...
c) Write a fronting app that will do nothing but pick up the message from q A , strip the RFH and put it into q B.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dp111443 |
| Posted: Tue Apr 10, 2007 7:05 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi,
Thanks for your responses. I'll try and explore changing the applications sides to cater for the RFH2 headers. Really....they should anyway.
cheers again!
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
