Author |
Message
|
sri_csee1983 |
Posted: Mon May 12, 2008 12:02 am Post subject: Number brokers on ConfigMgr in Version 5? |
|
|
 Centurion
Joined: 25 Mar 2008 Posts: 125 Location: Chennai,India
|
Dear Friends,
Sorry if this question is answered in any of the previous post. It is a simple question. How many brokers can be added to Configuration manager in Message Broker 5. I have one broker in Windows and the other in Z/OS, need to debug both at a time. I am not able to add more than one broker to the domain, if add the other one, it doesnt shows the execution groups of that broker. Connect lists are checked. Everything created. I get the following error when I add the other broker
BIP2045E: Broker MQD1BRK (UUID 964c01d5-1401-0000-0080-8c98057e08c9) running on WebSphere Business Integration queue manager MQD1 could not process an internal configuration message because the broker identity received in the message (UUID f87620dc-1901-0000-0080-8c98057e08c9) did not match that of this broker.
An internal configuration message could not be processed and was rejected. Each broker is identified by a universally unique identifier called a UUID which is allocated when the user creates a definition for the broker. The configuration message received contained a broker UUID (f87620dc-1901-0000-0080-8c98057e08c9) that does not match the UUID of broker MQD1BRK running on WebSphere Business Integration queue manager MQD1. There are two possible reasons for this. Either a user has accidentally specified queue manager MQD1 when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker MQD1BRK was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker MQD1BRK a new, different UUID.
If the queue manager name specified in the Message Brokers Toolkit was incorrect then use the Message Brokers Toolkit to correct the broker definition in error. The mqsilist command may be used to display broker queue manager names. Otherwise, if the broker definition was deleted and recreated, you must use the mqsideletebroker and mqsicreatebroker commands to recreate the broker, then redeploy the configuration for the broker in order to re-establish the correct broker identity. To avoid loss of data when recreating the broker, make sure that you follow the sequence of actions defined in the WebSphere Business Integration Message Brokers online documentation section "Recovery and restart".
I have seen this error in the previous posts, but their purpose was different. Please reply _________________ With Cheers,
Sri |
|
Back to top |
|
 |
AkankshA |
Posted: Mon May 12, 2008 12:06 am Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
You can add more then one broker to one config manager...
you can only debug one execution group at a time.... _________________ Cheers |
|
Back to top |
|
 |
Gaya3 |
Posted: Mon May 12, 2008 12:10 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Purpose could be different,
But the solution is same.
So please search and resolve the issue
Clue 1:
If the broker you are now trying to create was previously deleted, it is possible that the UUID was not.
Better do a clean deploy.
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
mqmatt |
Posted: Mon May 12, 2008 1:36 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
You can add many brokers to a single Configuration Manager.
As Gaya3 says, the error you're seeing could be due to several things. For your scenario, the most likely candidates are:
(1) you're trying to add the same broker to a second Configuration Manager, or
(2) you've configured MQ incorrectly. |
|
Back to top |
|
 |
sri_csee1983 |
Posted: Mon May 12, 2008 6:24 pm Post subject: |
|
|
 Centurion
Joined: 25 Mar 2008 Posts: 125 Location: Chennai,India
|
Dear All,
thanx for ur replies. I deleted both brokers and recreated using mqsideletebroker and mqsicreatebroker and then added to the configMgr. It was successful.
Now another question. Client is having two different application, Say for eg Appl1 and Appl2. These two applications are no way related in functionality with each other (I mean the business logic). Message flows for appl1 is developed by a diff vendor, and for Appl2 by another vendor. Now is it advisable to have two different brokers or one broker with different execution groups. Already both the application has different execution groups.
I suggested to the client, let us have two different brokers(I am vendor for Appl2). but the vendor for appl1 told we can have single broker with different exec groups. Looking at the tag of the vendor of appl1 the client went the suggestion made by vendor of appl1.
Now advise which is the best soln.
Broker is to be deployed in Z/OS _________________ With Cheers,
Sri |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon May 12, 2008 7:34 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Let the client decide. It is a question of horse power and money.
Capacity planning should be done and measurements be taken...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
sri_csee1983 |
Posted: Mon May 12, 2008 9:42 pm Post subject: |
|
|
 Centurion
Joined: 25 Mar 2008 Posts: 125 Location: Chennai,India
|
Will there be any problem on having two separate brokers.
If they are going to be on a single broker,
If any of the execution group of Appl1 causes the broker to go down, Appl2 will also be affected. This I thought a very valid point. But client are telling that if any additional broker and additional QM, they need to increase the system resources on Z/OS. Is that true. Since I am new to Z/OS I am not sure abt it. _________________ With Cheers,
Sri |
|
Back to top |
|
 |
Gaya3 |
Posted: Mon May 12, 2008 10:14 pm Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
sri_csee1983 wrote: |
Will there be any problem on having two separate brokers.
|
No problem, if the system permits.
Licence matters
Administration of the same etc etc...
All these are accountable.
sri_csee1983 wrote: |
If they are going to be on a single broker,
If any of the execution group of Appl1 causes the broker to go down, Appl2 will also be affected. This I thought a very valid point. |
Depends upon how it being designed, Each execution group is a process
so there is no dependency. Easy to administrate etc etc.
sri_csee1983 wrote: |
But client are telling that if any additional broker and additional QM, they need to increase the system resources on Z/OS. Is that true. Since I am new to Z/OS I am not sure abt it. |
Yes, Exactly, its required.....(Read the System Requirements manual)
taking all these in to considerations, what would be your decision?
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue May 13, 2008 1:16 am Post subject: One point that may hqave been missed |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Is that the relationship of Broker to WMQ Queue Manager is 1:1.
AFAIK, you can't have two brokers reading messages from different queues on the same QM.
If you have two separate brokers on the same Server then there are IMHO no licensing issues.
Your underlying WMQ architecture would have to change if you used TWO brokers.
Multiple Execution Groups in the same broker is probably the way to go. _________________ 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 |
|
 |
Vitor |
Posted: Tue May 13, 2008 2:14 am Post subject: Re: One point that may hqave been missed |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
smdavies99 wrote: |
Is that the relationship of Broker to WMQ Queue Manager is 1:1. |
It is
smdavies99 wrote: |
AFAIK, you can't have two brokers reading messages from different queues on the same QM. |
Quite true
smdavies99 wrote: |
If you have two separate brokers on the same Server then there are IMHO no licensing issues. |
Quite true
smdavies99 wrote: |
Your underlying WMQ architecture would have to change if you used TWO brokers. |
And if you used 2 execution groups; you'd probably want separate queues. Easier than 2 queue managers
smdavies99 wrote: |
Multiple Execution Groups in the same broker is probably the way to go. |
It's what I'd do _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|