| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to deploy to a new broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| MSV |
 Posted: Wed Apr 12, 2006 12:57 pm Post subject: Unable to deploy to a new broker |
 |
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
hi all,
I had created a new BROKER(named as V6BROKER2) which belongs to the BROKER DOMAIN that is associated with the DEFAULT CONFIGURATION MANAGER.(before this i had created a database for the new broker)
my new broker is visible when i give "mqsilist"
Inorder to communicate my new broker with the configuration manager,I had connected the components of the 2 queue managers(one is the queue manager of my new broker,other is the queue manager of the DEFAULT BROKER).
I started my broker service.
but, in the toolkit(alerts window) it is showing me that both the broker and the execution group are not running.
when i tried to deploy a sample flow,it is giving the following error:
BIP1533E: Unable to deploy configuration data: unknown WebSphere MQ queue manager v6brk2_QM associated with broker V6BROKER2.
An attempt was made to deploy configuration data to one or more brokers. The WebSphere MQ queue manager v6brk2_QM associated with broker V6BROKER2 is not known to the Configuration Manager's WebSphere MQ queue manager. The deploy operation was not performed.
Check that the name of the queue manager is spelled correctly. Note that WebSphere MQ queue manager names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager v6brk2_QM, or a transmission queue called v6brk2_QM, is defined to the Configuration Manager's queue manager. For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2087.
____________
I had even set my transmission queue names as suggested in the error message.But still i am unable to deploy.
I appreciate ur help.
Thank U |
|
| Back to top |
|
 |
| dipankar |
| Posted: Wed Apr 12, 2006 7:21 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi MSV,
| Quote: |
| Inorder to communicate my new broker with the configuration manager,I had connected the components of the 2 queue managers(one is the queue manager of my new broker,other is the queue manager of the DEFAULT BROKER). |
How did you connect the 2 qmgrs (broker's qmgr and configmgr's qmgr)?
_________________
Regards |
|
| Back to top |
|
|
| MSV |
| Posted: Thu Apr 13, 2006 6:10 am Post subject: |
|
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
hi dipankar,
At first i had created 2 Transmission Queues one on each of the queue managers.
Then i had created sender and reciever channels.
On Queuemanager1,
sender channel by name "QM1_QM2"
reciever channel by name "QM2_QM1"
On Queuemanager2,
sender channel by name "QM2_QM1"
reciever channel by name "QM1_QM2"
while creating the sender channels, i had mentioned the respective transmission queue name and the connection name.
All the channels,channel initiators and the listeners are in starting state.
Is there anything else that i am ignoring ?(inorder to communicate 2 queue managers).please let me know. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 13, 2006 6:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should, instead, create transmit queues named after the Broker QM (on the configmgr qm) and after the configmgr qm (on the broker qm).
So if the configmgr qm is "QM1", then the xmit q on broker qmgr is "QM1", and if the broker qm is "QM2" then the xmitq on configmgr qmgr (QM1) is "QM2".
Isn't this clearly documented?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MSV |
| Posted: Thu Apr 13, 2006 6:34 am Post subject: |
|
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
| jefflowrey wrote: |
You should, instead, create transmit queues named after the Broker QM (on the configmgr qm) and after the configmgr qm (on the broker qm).
So if the configmgr qm is "QM1", then the xmit q on broker qmgr is "QM1", and if the broker qm is "QM2" then the xmitq on configmgr qmgr (QM1) is "QM2".
Isn't this clearly documented? |
Hi jeff,
I had given the transmission queue names correctly.
| MSV wrote: |
I had even set my transmission queue names as suggested in the error message.But still i am unable to deploy.
I appreciate ur help.
Thank U |
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 13, 2006 1:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
You should, instead, create transmit queues named after the Broker QM (on the configmgr qm) and after the configmgr qm (on the broker qm).
So if the configmgr qm is "QM1", then the xmit q on broker qmgr is "QM1", and if the broker qm is "QM2" then the xmitq on configmgr qmgr (QM1) is "QM2".
Isn't this clearly documented? |
I thought that what was clear is: you needed a default path from the configmgr to the broker's qmgr and back. Which ever way you implement that path (see intercommunications manual and qmgr alias) is up to you and your topology 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 13, 2006 1:52 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, but this is the simplest way to create a default path, and so would be the simplest to verify and implement if necessary and not require a lot more explanation of what "default path" means, and where to find more information.
MSV - Do your channels start, if you start them manually? Do they start if you create a remote queue on configmgr that points to a qlocal on broker, and put a message to that remote queue?
_________________
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
|
|
|
|
