| Author |
Message
|
| zhaobin |
 Posted: Mon Jan 13, 2003 11:05 pm Post subject: multiple brokers in the broker domain |
 |
|
Novice
Joined: 29 Oct 2002
Posts: 20
|
Hi,
What I understand is each execution group is in fact a separate process. So message flows belonging to different applications are assigned to different execution groups to achieve protection and isolation among different applications. Then at which point multiple brokers are necessary within a broker domain? Is there any "best practice" or guideline to help deciding how many brokers are needed? Is there a limitation on how many message flows or execution groups a single broker can support?
thanks |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Jan 17, 2003 5:35 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
You don't need multiple broker's on a single machine. A new broker will require additional license copy, which is very costly.
I don't think there is any limitation on the number of EG's or Message flows a Broker can handle, but you should make sure your hardware is selected and configured properly to process expected volume.
_________________
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 |
|
|
| zhaobin |
| Posted: Sun Jan 19, 2003 5:08 pm Post subject: |
|
|
Novice
Joined: 29 Oct 2002
Posts: 20
|
Thanks, Kirani. You are right, the license goes as per broker basis, which is very costly.
If from a technical perspective, within a department network, what kind of factors would lead multiple brokers being deployed on different machines? Or normally, within a LAN network, a single broker is sufficient as long as the physical machine is able to handle the load?
thanks, |
|
| Back to top |
|
|
| kirani |
| Posted: Sun Jan 19, 2003 9:37 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Yes, within a single project, if one machine is able to handle such load then multiple brokers are not required.
If you want to have highly available environment (24x7) then I guess you would need multiple brokers.
_________________
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 |
|
|
| fschofer |
| Posted: Mon Jan 20, 2003 12:14 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi Kirani,
where did you get your license information ?
>You don't need multiple broker's on a single machine. A new broker will
>require additional license copy, which is very costly.
Or do i understand the text in the Installation Guide wrong ?
License information
Under the terms of the WebSphere MQ Integrator Version 2.1 license
agreement, you can install one instance of each component at any one time on
any one system, with the exception of the Control Center. You can install the
Control Center on multiple systems providing that each Control Center is
interacting with the same single Configuration Manager. You can create
multiple brokers on a single system. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jan 20, 2003 2:11 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You need a WMQI/MQSI license for each system that runs a broker.
However you can have as many brokers on that system as you wish (each requires a queue manager though) without extra licenses.
Additionally you can have a standby system that is not processing any workload without paying extra licenses.
We have a 12-CPU P680 for our production brokers and a standby 6-CPU P680 with HACMP failover. We checked all this out very carefully with IBM in terms of licensing.
In addition (and a little known fact) you can reduce the MQSI Capacity Units (licenses) required for development Windows NT platforms by half as many as needed for production environments.
This was all true at the time we purchased MQSI in 2001 - it may have changed since. |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jan 20, 2003 5:50 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi fschofer,
I was referring to multiple brokers on different systems. As zpat said, you can create more than one broker on single machine without additional licenses.
I don't see many advantages of having multiple brokers on same hardware machine.
Regards,
Kiran
_________________
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 |
|
|
| zpat |
| Posted: Tue Jan 21, 2003 12:27 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
We have one broker for 24x7 that is never taken down. We have another one that is taken down nightly to ensure a consistent backup point (not that I personally like this design).
In a non-production environment, multiple brokers are useful for different levels of development testing. Consolidating onto one powerful server may well save license costs.
One of the biggest pains with MQSI is the limitation of only one CONFIGURATION manager per NT platform. Although we don't have to pay extra licenses - we do have to use extra servers and since IBM charge us to host each server - it does cost more.
Apparently the thing which causes this constraint is the fixed queue names used by the CM, why can't IBM apply a prefix per CM? |
|
| Back to top |
|
|
| zhaobin |
| Posted: Tue Jan 21, 2003 6:09 pm Post subject: |
|
|
Novice
Joined: 29 Oct 2002
Posts: 20
|
Thanks for your information, Zpat.
What do u mean by one configuration manager per NT platform? What I understand is only one configuration manager is allowed within one broker domain. In fact, what does broker domain mean?All inter-connected brokers? So each broker domain is like a island, which is isolated from other broker domains?
regards,
zhaobin |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jan 27, 2003 1:43 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
AFAIK you can't place multiple configuration managers on a single NT platform. Despite the fact that they spend 90% of their time idle.
We have around five types of broker domains, ranging from R&D test of new versions, developer levels, UAT, productions. We need to operate at least 5 CMs.
We are forced to have a separate (and in our case expensively hosted) NT server for each CM. |
|
| Back to top |
|
|
|
|
