ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deployment pb with WMB Toolkit V6

Post new topic  Reply to topic
 Deployment pb with WMB Toolkit V6 « View previous topic :: View next topic » 
Author Message
nphuclong
PostPosted: Mon Feb 19, 2007 6:52 am    Post subject: Deployment pb with WMB Toolkit V6 Reply with quote

Newbie

Joined: 19 Feb 2007
Posts: 5

Hi all,
We decided to upgrade to WMB V6 from V5. We tried to deploy old .bar (from V5) with the WMB Toolkit V6 but are stuck with the following error (sorry for the error message in french) :
"BIP2217E: Le nom de fichier '\Bip MessageFlows\META-INF\broker.xml' est invalide pour le gestionnaire de ressources '{1}'.

Le courtier de messages reçoit un nom de fichier '\Bip MessageFlows\META-INF\broker.xml' qui n'est pas valide pour le gestionnaire de ressources '{1}'. Il peut s'agir d'une extension de nom de fichier invalide ou inconnue, ou tout simplement d'un chemin d'accès invalide.

Assurez-vous de saisir un nom de fichier valide.
"

Translated to English :
"BIP2217E: The following file '\Bip MessageFlows\META-INF\broker.xml' is not valid for the resource manager '{1}'..."

We do not have the sources of these old .bar in Production Environment.
Thanks to any help.

Best regards,
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Feb 19, 2007 6:54 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

If you don't have sources, you probably shouldn't be deploying this flow - you won't ever be able to maintain it.

If it is only complaining about broker.xml, then try opening the BAR file in the Bar file editor in the v6 Toolkit, and then saving it again, and then see if it will deploy again.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
nphuclong
PostPosted: Tue Feb 20, 2007 1:48 am    Post subject: Reply with quote

Newbie

Joined: 19 Feb 2007
Posts: 5

In fact, we do have sources but not the tagged version deployed in the production environment. So, we don't want to deploy new .bar under tests & validation but plan 2 phases : technical upgrade (V5 -> V6) & business upgrade.

We tried to delete the broker.xml from the .bar in vain. Your tip does not help.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Feb 20, 2007 3:08 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I did not say to DELETE broker.xml. You need that file!

I said to use the version 6 Toolkit to open the Bar file. My thought is that the broker.xml is not converted to a v6 bar file somehow, and opening and closing it in the Toolkit will refresh/fix that.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
nphuclong
PostPosted: Tue Feb 20, 2007 6:41 am    Post subject: Reply with quote

Newbie

Joined: 19 Feb 2007
Posts: 5

We tried to follow your advice first but it didn't work. Then, we thought about removing the broker.xml because it's not generated with the WMB Toolkit V6. That doesn't work either.

Any idea ?

Best regards,
Long
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Feb 20, 2007 6:43 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You *need* the Broker.xml file.

I'm confused a bit about the path it mentions, though - '\Bip MessageFlows\META-INF\broker.xml' .

I would think that, in the BAR file, it should be just \META-INF\broker.xml.

What does the structure of the BAR file look like, when it's unpacked?

Probably you should open a PMR.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
nphuclong
PostPosted: Tue Feb 20, 2007 7:36 am    Post subject: Reply with quote

Newbie

Joined: 19 Feb 2007
Posts: 5

It's amazing, we have all these broker.xml
Quote:
\Bip MessageFlows\META-INF\broker.xml
and
Quote:
\META-INF\broker.xml
when decompressing the .bar.
At the root, we have the message flow .cmf and in the sub-directory 'Bip MessageFlows', .msgflow.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Feb 20, 2007 7:40 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It sounds like someone tried to put more than one BAR file in a single BAR file.

That doesn't work.

You may not have a deployable package.

I would create a new BAR file that uses the new version of code. Then, carefully, replace the .cmf and .dict files files in the new BAR file with ones in the old BAR file.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
nphuclong
PostPosted: Wed Feb 21, 2007 1:37 am    Post subject: Reply with quote

Newbie

Joined: 19 Feb 2007
Posts: 5

Great, that works We can now deploy all our .bar.
Thank you very much.

Best regards,
Long
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deployment pb with WMB Toolkit V6
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.