ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker and QM

Post new topic  Reply to topic
 Broker and QM « View previous topic :: View next topic » 
Author Message
keenlearner
PostPosted: Thu Jan 15, 2009 6:12 am    Post subject: Broker and QM Reply with quote

Acolyte

Joined: 24 Aug 2006
Posts: 62

Hi
Can one explained me why do we need one individual Queue Manager per broker.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Thu Jan 15, 2009 6:16 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

because that is the way it was designed
_________________
Regards, Butcher
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Jan 15, 2009 6:19 am    Post subject: Re: Broker and QM Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

keenlearner wrote:
Can one explained me why do we need one individual Queue Manager per broker.


Short answer - that's how the software's built.

Slightly longer answer - because the broker uses a particular set of queues defined to the queue manager, and running two or more brokers would require either a) some means of individually naming the queues or b) the two brokers being able to identify "their" messages.

Better question - why would you want more than one broker on a queue manager? It would cause a number of issues with coding and scaling that occur to me sitting here, never mind the increased problems of administration!
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Jan 15, 2009 7:49 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

It is an annoying constraint and one that could have easily been avoided with a queue name prefix.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Jan 15, 2009 10:05 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

[quote="zpat"]It is an annoying constraint and one that could have easily been avoided with a queue name prefix.[/quote]

You could always make a format suggestion to IBM on the matter.

Personally, I don't find this an onerous restriction.
For example:-
Being able to configure the various QMGRs with the resources, objects and exits etc that it needs and being able to stop/start it independantly of other brokers improves the manageability & resillience of the overall subsystem.

AFAIK, there is no financial penalty in terms of licensing costs from IBM for using multiple QMGR's & Brokers on one system beyond the costs for a single broker and QMGR on the same system.
_________________
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.
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Jan 15, 2009 10:35 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

It's particularly annoying on development platforms when you don't need the (theoretical) resilience.

Even more true for configuration managers.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Thu Jan 15, 2009 11:55 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

zpat wrote:
It's particularly annoying on development platforms when you don't need the (theoretical) resilience.


We opted for multiple execution groups on one DEV QM/Broker versus multiple Broker/QMs. We use suffixes for the queue names, and UDPs in the bar files to be able deploy the same code to each EG. The q names determine which environment is used. Datasource names are set at bar file time. Code in the ESQL queries what EG the flow is running in to determine q names to use when building Destination Lists.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
keenlearner
PostPosted: Thu Jan 15, 2009 10:54 pm    Post subject: Reply with quote

Acolyte

Joined: 24 Aug 2006
Posts: 62

Agreed to to all of the above discussion. but there must something concrete which let to this decision. May be the administration, independent functioning of the each broker may be the some of the reasons and they are listed above also. But yet to find out the root reason which let to this.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Jan 16, 2009 1:16 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

keenlearner wrote:
But yet to find out the root reason which let to this.


Only the dev team at IBM know the truth.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker and QM
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.