You are referring to the "old" queue based pub/sub engine? Assuming the queue manager is configured to handle the "old" pub/sub queues requests.
But it's still not quite like the WMQ v7 MQSUB call.
How would using a queued subscription method allow a message flow to automatically subscribe? What would start the flow in the first place? I suppose you would need one flow to register the subscription and another to process the messages?
But it is another technique that I can consider, thanks. No doubt IBM will include MQSUB functionality at some point.
It is but just another form of the V7 MQSUB call. Just because you have a non JMS API does not mean you HAVE to use it. The RFH2 JMS way still works fine in V7.
You can have which ever flow or user subscribe... In the subscription you specify the delivery queue... so really no problems. You can have the subscription be an administrative one (we do) when you subscribe a flow...
I find it easier to subscribe via a message with an RFH2 than via PCF message, however the easiest of all is via mqsc...
Use whatever suits your purpose best! _________________ MQ & Broker admin
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
all of our services that use subscriptions subscribe themselves.
We send a message that contains 'Subscribe' or 'Unsuscribe'. The service sends the appropriate message.
This approach saves the PITA of having to correctly format a sub/unsub message.
Another place I worked had a generic sub/usub flow that everyone used.
These approaches remove a lot of the uncertainies about pub/sub. If you are going to be doing a lot then these approaches are worth considering. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
zpat wrote:
Still the chicken and egg question.
How would the subscribing flow start in the first place? IBM don't provide a "for no reason at all" input node (although it might be useful..).
We drop a message onto a queue. This can be done remotely using tools like rfhutil. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
I see JMSInput natively integrates with MQ V7 topic objects (Property "Subscription Topic") .. but wonder if there is any non-JMS equivalent for MQSUB call with in MB , especially for MQ input node ? OR as discussed earlier topic alias to queue or legacy queued pub/sub are the only options as of now to receive publications to a MQInput node ... ? thx.
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