| Author |
Message
|
| svemula1 |
 Posted: Tue Feb 14, 2012 1:59 pm Post subject: WMB BIP2087E: Broker BRK_Local was unable to process the int |
 |
|
Newbie
Joined: 14 Feb 2012
Posts: 7
|
Hi,
I have WMB 6 bar file.But in my local WMB 7 is installed.I am not able to deploy the WMB 6 bar file in WMB 7 amd getting below error.
BIP2087E: Broker BRK_Local was unable to process the internal configuration message.
Your assistance is appreciated. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Feb 15, 2012 5:08 am Post subject: Re: WMB BIP2087E: Broker BRK_Local was unable to process the |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| svemula1 wrote: |
| Your assistance is appreciated. |
Are you trying to deploy with the WMBv6 tooling or the WMBv7 tooling?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| svemula1 |
| Posted: Thu Feb 16, 2012 8:18 am Post subject: |
|
|
Newbie
Joined: 14 Feb 2012
Posts: 7
|
| Bar file has been created in WMB 6 tool kit.I am just taking the bar file and deploying in WMB 7 too kit ie WMB 7 broker. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 16, 2012 8:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| svemula1 wrote: |
| Bar file has been created in WMB 6 tool kit.I am just taking the bar file and deploying in WMB 7 too kit ie WMB 7 broker. |
Fair enough. If you mean WMBv6.1 not WMBv6.0.
Without the rest of the error message (there should have been a lot more than just the 2087 error) my first guess would be there are nodes in the bar file (possibly user defined) that don't exist in the v7 install you're deploying to. But without the errors that's just a guess.
Best solution is to take the source from the old toolkit, rebuild the bar in the new toolkit & deploy that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 16, 2012 10:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
Best solution is to take the source from the old toolkit, rebuild the bar in the new toolkit & deploy that. |
Been there, done that, works like a charm after you've cleared up the odd error or 2 (Think message sets) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 16, 2012 11:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Vitor wrote: |
Best solution is to take the source from the old toolkit, rebuild the bar in the new toolkit & deploy that. |
Been there, done that, works like a charm after you've cleared up the odd error or 2 (Think message sets) |
Point taken, there may well be a few additional steps between import & build.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
