MQSeries.net :: View topic

barda900 · Posted: Sun Dec 09, 2007 9:58 am Post subject:

Hello,

I'm probably missing something really obvious here, byt please bear with me,
as I'm not really familiar with Websphere Message Broker (I do know MQ though).

The thing is, I can't believe there's no "Subscribe" node which I can use
for dynamically subscribing to the topic. I've read "Developing publish/subscribe applications"
and "Publish/subscribe" sections of the library. I have also read messagebroker_Publish_Subscribe.pdf PDF
and have read all the www.mqseries.net messages related to publish/subcribing.

What I'd like to achieve is to have a flow with an input "Subscribe" node, in which
I would define my topic name and that would be all I'd have to do to publish messages
from a flow to another one, but from what I gather I must do it manually, because the docs say

"Subscribers issue subscription registration requests to their local broker when they want to receive published messages.
All the information associated with the subscription is recorded by the broker in the broker's subscription table."

And there's also a great deal of discussion here on the forum on how to properly set
the MQRFH2 headers for subcribing dynamically to messages, or how to use the rfhutil program,
or how to do it programatically (from Java, Visual Basic, etc.) But I'd really like
to avoid it and have the broker manage the subcription process.

The only way I can imagine right now is to use the JMSInput and JMSOutput nodes,
but that, on the other hand, would require me to administer the JNDI objects, which
I'm OK with but still it's a thing to do which could have been avoided (there will be ~600 topics)
had I have an access to a "Subscribe" node in the palette :-)

So, to sum it up, is what I describe doable at all? Because it sounds like a basic
requirement for a broker, right? Friends, how do you deal with it?

For development, I'm using Windows:

- broker toolkit - 6.0.2 ifix 010 Build id 20061201_1308
- broker 6.0.0 fixpack 6
- MQ 6.0.0.2

The target environment will run on z/OS.

Thanks for any help and suggestions!