Author |
Message
|
jsware |
Posted: Fri Aug 06, 2004 2:54 am Post subject: Can I use WBIMB PubSub without writing message flows? |
|
|
 Chevalier
Joined: 17 May 2001 Posts: 455
|
I am investigating setting up PubSub for a project. I intend to use WBIMB (which we already have) as the pub-sub broker.
On reading all the manuls, examples, tutorials etc. that I can find, they all seem to involve writing a message flow to read a message, and wire up a Publication node.
Assuming I can create a message with an MQRFH2 header etc. etc. Can I allow applications to publish information themselves without having to write a message flow?
If so, which queue do I put the publication on so that it is sent to all the subscribers of the topic? (I've tried using the rfhutil support pack and can register a subscriber, but when I put a publish message on the SYSTEM.BROKER.CONTROL.QUEUE, it just disappears - no messages in the syslog - nothing). I assumed that SYSTEM.BROKER.CONTROL.QUEUE is the wrong queue, but I can't find any documentation where the correct queue is given for producing manual publications. _________________ Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
Back to top |
|
 |
vennela |
Posted: Fri Aug 06, 2004 8:22 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Why do you want to use WBIMB or WBIEB then. I think all you need is a QueueManager and the support pac MA0C.
Look at MQSeries Publish/Subscribe section of the Publish/Subscribe manual |
|
Back to top |
|
 |
kirani |
Posted: Sat Aug 07, 2004 12:13 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
John,
If you access to WMQI 2.1 manuals then please refer to Chapter 6. Topic: Publish/Subscribe in Introduction and Planning manual. I am sure that will answer your question. _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
jsware |
Posted: Mon Aug 09, 2004 12:32 am Post subject: |
|
|
 Chevalier
Joined: 17 May 2001 Posts: 455
|
We already have a large implementation of WMQI/WBIMB, but we don't use PubSub (yet). A project wants to use PubSub to allow JMS publishers to publish to JMS subscribers. The published messages are in the correct format for the subscribers (no message translation required). I wanted to use the "peer" nature of WBIMB brokers rather than the tree nature of base MQ Pub Sub and also wanted to make use of topic security.
I need to build a generic, pub sub environment that was not specific to the project, but could be used by other projects when they come along.
I expected WBIMB to come with a complete configuration that processes messages on SYSTEM.BROKER.DEFAULT.STREAM and follows all the ReplyTo, PAN and NAN report options that base MQ Pub Sub does. It doesn't seem to though and I'll have to write a flow that does... _________________ Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
Back to top |
|
 |
felfel |
Posted: Fri Mar 18, 2005 8:35 am Post subject: any other solution ? |
|
|
Apprentice
Joined: 02 Nov 2004 Posts: 26
|
I'm in the same case .
i'm looking for another solution than writing a message flow.
Do you know what does exactly the publication node ?
thanks for any help , _________________ "Mens sana in corpore sano" |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Mar 18, 2005 8:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
There are instructions in the documentation for setting up MAOC/JMS pub/sub stuff with Broker.
And I seem to recall that the Publication node writes messages to SYSTEM.BROKER.CONTROL.QUEUE. But that is just a hazy memory that may not be correct these days. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
malammik |
Posted: Fri Mar 18, 2005 11:29 am Post subject: |
|
|
 Partisan
Joined: 27 Jan 2005 Posts: 397 Location: Philadelphia, PA
|
It should be possible however I was only able to do it "half-way." Meaning I was able to successfully send subscribe and unsubscribe requests to the SYSTEM.BROKER.CONTROL.QUEUE however broker was rejecting my publications to that queue. Maybe I was doing something wrong although I doubt it because I was using rfhutil to generate publication messages. I think there is a way to trick the broker that it participates in the domain with other brokers and define a stream queue. You shold be able then send your publications directly to the stream queue. See if you can successfully publish messages to the BROKER.CONTROL.QUEUE. Let me know. _________________ Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Mar 18, 2005 1:04 pm Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
From the MA0C manual:
Quote: |
SYSTEM.BROKER.CONTROL.QUEUE
This is the broker's control queue. Publisher and subscriber applications, and other brokers, send all command messages (except publications and requests to delete publications) to this queue. |
So, if you were publishing to the control queue, that might be your problem. Try publishing to the stream queue. |
|
Back to top |
|
 |
Tibor |
Posted: Sat Mar 19, 2005 2:49 am Post subject: |
|
|
 Grand Master
Joined: 20 May 2001 Posts: 1033 Location: Hungary
|
John,
We use the message broker for publication with a "minimal" flow:
- mqinput
- trace
- publication
The main advantage for me the ability for tracing.
Tibor |
|
Back to top |
|
 |
felfel |
Posted: Sat Mar 19, 2005 4:56 am Post subject: |
|
|
Apprentice
Joined: 02 Nov 2004 Posts: 26
|
Hi ,
I tried to publish either in the SYSTEM.BROKER.DEFAULT.STREAM and in the SYSTEM.BROKER.CONTROL.QUEUE but it doesn't match.
I'm afraid that the publication node has some more hidden actions.
For Subscribers , since you need to prefix your queue with SYSTEM.JMS.ND. , I take this solution :
In the TopicConnectionFactory , I associate the broker ND queue with a wildcard SYSTEM.JMS.ND.TopicName.*.
Then all subscribers can create a dynamic queue like SYSM.JMS.ND.TpicName.myQueue and receive the publication
Anybody has another idea ?
thanks, _________________ "Mens sana in corpore sano" |
|
Back to top |
|
 |
|