| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problems building a BAR with mqsicreatebar |
« View previous topic :: View next topic » |
| Author |
Message
|
| ccrandall |
 Posted: Tue Nov 16, 2010 1:25 pm Post subject: Problems building a BAR with mqsicreatebar |
 |
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
I have workspace that I have linked to a PVCS SCM repository. I can build a BAR and deploy it just fine within the toolkit. I also have an Ant build that had been working until today. When it goes to compile the BAR using mqsicreatebar, I get a handful of these errors:
[exec] Nov 16, 2010 2:51:08 PM com.ibm.etools.mft.rdb.validation.RDBBaseXmiBuilder buildStart
[exec] SEVERE: Database definition migration cannot be run in headless mode. Please launch the workbench and clean build all projects to perform the migration first.
I did do another clean build and checked in some files that had been checked out to see if that might refresh something. However, having checked out files shouldn't matter as we are pulling our workfiles from PVCS and placing them in a temp location.
I'm using Message Broker 7.0 on Windows XP.
Does anyone know what the above error is caused by?
Thanks!
Curt |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Nov 16, 2010 1:42 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It seems you have a project that is created using an earlier version of Broker, that contains a Database Definition. When it is opened in the current version of Broker, it has to be migrated. This migration process can't be done without some Toolkit components that require GUI componentry and can't be run without a display.
Open the projects in Toolkit, run a full clean build, save everything in PVCS again. |
|
| Back to top |
|
|
| ccrandall |
| Posted: Tue Nov 16, 2010 2:01 pm Post subject: |
|
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
Thanks Jeff.
This is odd as I just ran the mqsicreatebar command directly against my toolkit workspace and it worked. I suspect, then, that something is inside PVCS that shouldn't be there... or is getting included due to a mislabel??
Since there's a ton of files in my project, and it has yet to be released to anyone, it might be easiest to start my PVCS repository from scratch. |
|
| Back to top |
|
|
| Amitha |
| Posted: Tue Nov 16, 2010 2:25 pm Post subject: |
|
|
Voyager
Joined: 20 Nov 2009
Posts: 80
Location: Newyork
|
Can you post the mqsicreatebar you are using?
Did you try mqsicreatebar with -cleanBuild option? |
|
| Back to top |
|
|
| ccrandall |
| Posted: Wed Nov 17, 2010 12:19 pm Post subject: |
|
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
Nope, I haven't tried -cleanBuild, but I can certainly look into that.
The mqsicreatebar command I'm using is pretty basic:
"c:\Program Files\IBM\WMBT700\mqsicreatebar" -data "C:\ECC\Enterprise Components\Message Broker v7.0 Switch 3.x\workspace" -b c:\temp\bar\configure\switch.bar -p ClydeJARs MF_ECC_ApplicationPatternTemplates MF_ECC_BrokerRoutingFramework MF_ECC_CaptureErrorFramework_V2 MF_ECC_MessageSwitchExtension MF_ECC_MsgLoggingFramework PeopleWhoMakeMoreMoney001MessageSet -o MF_ECC_ApplicationPatternTemplates/nmicc/MessageSwitch_req.msgflow MF_ECC_ApplicationPatternTemplates/nmicc/MessageSwitch_rep.msgflow MF_ECC_ApplicationPatternTemplates/nmicc/MessageSwitch_multipacket_rep.msgflow MF_ECC_ApplicationPatternTemplates/nmicc/MessageSwitch_soap_req.msgflow PeopleWhoMakeMoreMoney001MessageSet/PeopleWhoMakeMoreMoney001/messageSet.mset
What's odd here is that, as stated above, I can run this mqsicreatebar command against my MB Toolkit workspace and everything is fine. However, when I run mqsicreatebar manually or as part of the Ant script against the code in our PVCS repository, I get the SEVERE messages. When I use Beyond Compare to compare the code in the workspace to the code in the temp directory (where the code in PVCS is checked out to) the only difference is in the .metadata folder.
We do not check in our .metadata and our senior MB architect didn't think it should have anything to do with this issue, but I can't help but think it does since that's the only difference. So, I'm about to run some more tests replacing the .metadata created during the mqsicreatebar command execution with what's in the workspace.
One other thing I didn't think of is that I'm using MB Toolkit 7.0.0.0. We've found several issues with that version of the toolkit and mqsicreatebar. So, I'm setting up a MB 7.0.0.1 environment and with other build errors this seemed to fix things.
I'll follow up with the results of this for completeness. |
|
| Back to top |
|
|
| ccrandall |
| Posted: Thu Nov 18, 2010 3:16 pm Post subject: |
|
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
I tried several things to see if I could avoid the database definition migrations. Here's what I tried:
1.) Use -cleanBuild option.
This gave an error that the workbench had not been created.
2.) Replace the .metadata folder in the PVCS checkout directory, that's created during the build, with the .metadata in my toolkit workspace.
No change.
3.) After build, try to open the files checked out of PVCS and the created .metadata in MB Toolkit.
I could open it just fine. Did a clean build in the IDE. Then when I manually ran mqsicreatebar it still threw the SEVERE messages about database definition migration.
4.) Copied my toolkit workspace to the temp directory. Ran mqsicreatebuild.
Well, instead of getting 10 SEVERE messages I just got one. Funny, though, that the exact same code I copied doesn't have the issue in the toolkit workspace directory.
5.) Well, gave up and went to MB Toolkit 7.0.0.1.
My database definition migration messages disappeared. However, now it complains that the .project files are read-only (duh! that's the default when checked out of SCM). Doesn't seem to hurt anything, but I've used this same build process in MB 6.0, 6.1, and 7.0.0.0 and never got these errors.
We did have a TON of build errors with MB Toolkit 7.0.0.0 using the mqsicreatebar.exe and most went away in 7.0.0.1. Hopefully in the next fixpack this read-only issue goes away. For the curious, the error I get is:
org.eclipse.core.internal.resources.ResourceException: File /MF_ECC_MessageSwitchExtension/.project is read-only.
Like I said, though, it doesn't prevent what looks like a good BAR file from being created. I'll have to deploy and see what happens. |
|
| 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
|
|
|
|
