| Author |
Message
|
| Sue_2828 |
 Posted: Tue Aug 04, 2009 11:29 pm Post subject: creating additional broker |
 |
|
Apprentice
Joined: 14 Feb 2009
Posts: 37
|
Hello Folks,
Our environment is configured as follow:
Broker : BRK1
Configuration manager : CMR1
Queue Manager: QM1
Broker Database : BRKDB1
What I am trying to do is create another broker so I was able to :
create
Broker : BRK2
Broker DB : BRKDB2
Queue Manager: CMR2
Now I was assuming I can use the same conifugration manager for the second broker I created without making any change or affecting the first broker. Is this valid ? Am I missing something here . I was able to see the broker from the toolkit , however the min I try to deploy a smiple flow fro the new broker , I get the following error :
BIP1533E: Unable to deploy configuration data: unknown WebSphere MQ queue manager amouraTest associated with broker BRK2.
An attempt was made to deploy configuration data to one or more brokers. The WebSphere MQ queue manager QM2 associated with broker BRK2 is not known to the Configuration Manager's WebSphere MQ queue manager. The deploy operation was not performed
Please advice ..
Thanks |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Tue Aug 04, 2009 11:41 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Hi,
What have you done to make sure the "queue manager QM2 associated with broker BRK2" is known to the Configuration Manager's WebSphere MQ queue manager?
It is not clear from your post but presumably BRK1 and your config mgr are using the same queue manager so that you may not be familiar with the need to set up channels etc. to allow communication from the congigmgr qmgr to the bnroker qmgr.
Regards,
Vicky |
|
| Back to top |
|
|
| Sue_2828 |
| Posted: Wed Aug 05, 2009 12:24 am Post subject: |
|
|
Apprentice
Joined: 14 Feb 2009
Posts: 37
|
Hi vmcgloin, thats exactly what I am trying to understand , what do I need to do to associate the new queue manager to the existing configuration manager. I know for the old broker , I did that when I created the configuration manager first time. but what do I need to do in the case of adding a new broker?
Thanks |
|
| Back to top |
|
|
| gregop |
| Posted: Wed Aug 05, 2009 12:43 am Post subject: |
|
|
Voyager
Joined: 24 Nov 2006
Posts: 81
|
You need channels both ways between QM1 amd CMR2. Transmission Queues named as target queue managers.
See info centre: Configuring a Broker Domain / Connecting Components |
|
| Back to top |
|
|
| Sue_2828 |
| Posted: Sat Aug 08, 2009 12:02 am Post subject: |
|
|
Apprentice
Joined: 14 Feb 2009
Posts: 37
|
Hello there, I have managed to created the second broker and I can see it running on the toolkit , however , when I try to deploy a flow to the second broker "the new one" , I get the following error :
BIP2047E: Broker TSBKR (UUID e460a4e4-2201-0000-0080-c68c601a40b6) could not process an internal configuration message because the broker name received in the message (TSBKR ) did not match that of this broker.
An internal configuration message could not be processed and was rejected. Each broker is given a name when the Message Brokers Toolkit user creates a definition for the broker. This name must match the name supplied on the mqsicreatebroker command used to create the broker itself. Although the configuration message received contained the correct broker identity (UUID), it contained a broker name, TSBKR , that did not match the name of this broker, TSBKR. The probable cause is that a Message Brokers Toolkit user has incorrectly renamed the broker in the broker definition.
Use the Message Brokers Toolkit or Config Manager Proxy to rename the broker back to the name specified on the mqsicreatebroker command. This name can be found using the mqsilist command.
The old broker is functioning fine , it just the new one seem to be out of sync with the configuration manager. I read about the command mqsiservice , but I am concern if I use this command to register the new broker , a problem or I might affect the existing old broker. Can someone please advice ? What is it I am missing here.
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Aug 08, 2009 8:28 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The error text is quite clear
| Quote: |
| Use the Message Brokers Toolkit or Config Manager Proxy to rename the broker back to the name specified on the mqsicreatebroker command. This name can be found using the mqsilist command |
So leave mqsiservice alone!! 
Use mqsilist -a to verify the broker name as specified in the error text...
| Quote: |
This name can be found using the mqsilist command.  |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Mon Aug 10, 2009 1:14 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
I have had similar issue in the past. First , try not to use mqsiservice. If you are sure you don't have any mismatch in the naming or you are not referencing the correct broker, then why just not re-create the broker. Just delete the new broker you created , and create it again , make sure sender and recivers between broker qm and cm qm are up and start the new broker .
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| Sue_2828 |
| Posted: Mon Aug 10, 2009 1:28 am Post subject: |
|
|
Apprentice
Joined: 14 Feb 2009
Posts: 37
|
| Thanks for all the help, I just had to re-create the broker and solved the issue. |
|
| Back to top |
|
|
|
|
