|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Global & Local publications |
« View previous topic :: View next topic » |
Author |
Message
|
solkit |
Posted: Sat Jun 10, 2006 1:18 am Post subject: Global & Local publications |
|
|
Novice
Joined: 25 May 2006 Posts: 21
|
I'm testing broker network now.
I've done pub/sub in a Queue Manger.
I used 2 each queues and 1 stream in one Queue Manager to test pub/sub model and it's working now.
But when I try the pub/sub with 2 queues thoes are located in each other Quene Manger and 1 stream then it's not working.
I think I should set Global publication on the publication in my application program.
Anybody knows how to set the Global and local publication on the publication in the application? _________________ ^^ have a good day ^^ |
|
Back to top |
|
 |
fjb_saper |
Posted: Sat Jun 10, 2006 4:47 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Do you have a collective ? A slave broker ?
Anyway isn't global vs local part of the RFH2 settings?
Have you used the IH03 support pack?
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
solkit |
Posted: Sat Jun 10, 2006 7:31 am Post subject: |
|
|
Novice
Joined: 25 May 2006 Posts: 21
|
fjb_saper wrote: |
Do you have a collective ? A slave broker ?
Anyway isn't global vs local part of the RFH2 settings?
Have you used the IH03 support pack?
Enjoy  |
I think IH03 means WebSphere Message Broker V6.
So Do I need WebSphere MEssage Broker to use the local and global option?
Do I need WebSpherer Message Broker to use Broker networking?
I've already done the pub/sub model in one Queue Manager with the pub/sub/broker service which is provided WMQ V6.0 not IH03.
What are collective and slave broker?
I think collective is in IH03 only not in the pub/sub model which is provided by WMQSeries V6.0.
slave broker means chieldren broker?
thanks for your reply.... _________________ ^^ have a good day ^^ |
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Jun 10, 2006 9:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
IH03 means "Support Pack IH03", which includes the rfhutil program.
It does not mean, nor require, Message Broker.
Broker collectives and cloned brokers, on the other hand, are only possible with Message Broker and not with the base MQ pub/sub broker.
Please explain in more detail what you have configured. You have configured two queue managers, connected them, configured pub/sub brokers on them, connected one of those brokers as a child of the other?
You have registered two subscribers, one on each broker? You have published a message to the parent broker?
You have read and understood what the difference between a 'global' and a 'local' publication is, in the Publish/Subscribe User's Guide?
Heck, you have read the Publish/Subscribe User's Guide? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
solkit |
Posted: Sat Jun 10, 2006 10:34 am Post subject: |
|
|
Novice
Joined: 25 May 2006 Posts: 21
|
jefflowrey wrote: |
IH03 means "Support Pack IH03", which includes the rfhutil program.
It does not mean, nor require, Message Broker.
Broker collectives and cloned brokers, on the other hand, are only possible with Message Broker and not with the base MQ pub/sub broker.
Please explain in more detail what you have configured. You have configured two queue managers, connected them, configured pub/sub brokers on them, connected one of those brokers as a child of the other?
You have registered two subscribers, one on each broker? You have published a message to the parent broker?
You have read and understood what the difference between a 'global' and a 'local' publication is, in the Publish/Subscribe User's Guide?
Heck, you have read the Publish/Subscribe User's Guide? |
I have configured two queue managers, connected them, configured pub/sub brokers on them, connected one of those brokers as a child of the other. I have registered two subscribers, one on each broker. I have published a message to the parent broker.
I've done all of above things.
But It is not working.
So i was trying to find the solution out from the Documents and get the part for 'global' and 'local' publication concept which I didn't know.
I underdtood what the difference between a 'global' and a 'local' publication is, in the Publish/Subscribe User's Guide.
I'm not sure it could be a solution or not but just want to try test with the option.
Should I set the option on RFH2 field?
I'll try it.
And one more question.
Can I use Broker network on base MQ pub/sub broker? _________________ ^^ have a good day ^^ |
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Jun 10, 2006 1:46 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You have already configured a broker network, when you told one broker that it was the parent of the other.
Base MQ pub/sub broker networking is limited to only parent/child relationships - strict hierarchy. MB Broker networks can be more flexible.
What the pub/sub user's guide says is that global publication is the default, so you should not need to explicitly set it.
Quote: |
Publishers can specify that they want a publication to be published locally. If they do not specify this, the publication is made available globally through all the brokers in the network. |
Did you create the stream queue manually or allow it to be created dynamically?
Are both of the subscribers registered before you publish? Can you see messages flowing from the parent to the child and vice versa?
Maybe try stopping the child-to-parent sender channel, and re-registering the child's subscriber. If nothing ends up on the xmitq, then try deleting the child broker from the network and re-registering it. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
solkit |
Posted: Sat Jun 10, 2006 2:10 pm Post subject: |
|
|
Novice
Joined: 25 May 2006 Posts: 21
|
jefflowrey wrote: |
You have already configured a broker network, when you told one broker that it was the parent of the other.
Base MQ pub/sub broker networking is limited to only parent/child relationships - strict hierarchy. MB Broker networks can be more flexible.
What the pub/sub user's guide says is that global publication is the default, so you should not need to explicitly set it.
Quote: |
Publishers can specify that they want a publication to be published locally. If they do not specify this, the publication is made available globally through all the brokers in the network. |
Did you create the stream queue manually or allow it to be created dynamically?
Are both of the subscribers registered before you publish? Can you see messages flowing from the parent to the child and vice versa?
Maybe try stopping the child-to-parent sender channel, and re-registering the child's subscriber. If nothing ends up on the xmitq, then try deleting the child broker from the network and re-registering it. |
Thanks for your replying.
I'm not using distributed model.
I'm using Clustering.
The 2 managers are belong to same Cluster But the 2 Queues are not belong to the Cluster.
Thant is my intention that not include the two queues in the Cluster because I've read the sentence 'Stream queues must not be cluster queues ' on amqnar10.pdf.
I think I should make the 2 queues be a part of cluster and test again. _________________ ^^ have a good day ^^ |
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Jun 10, 2006 4:48 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
It shouldn't be necessary to make them cluster queues.
But I'm not sure that clustering will work, either. Broker connections seem to want regular distributed queueing routing in place.
So try creating xmitq and sdr/rcvr pair, and see if publications work. _________________ I am *not* the model of the modern major general. |
|
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
|
|
|
|