Author |
Message
|
GeneRK4 |
Posted: Wed Feb 04, 2015 1:51 am Post subject: mqsipackagebar command - query |
|
|
Master
Joined: 08 Jul 2013 Posts: 220
|
As mqsipackagebar does not need toolkit for its execution,I hope for
mqsipackagebar -w <root_location> -a <barfilename> -k <applicationname>
<root_location> need not be workspace path.
I tried this with svn path and with paths other than workspace path .But it throws the below error
"BIP1840S: No valid resources found to add to the BAR file. Check that rootLocation is correct and specify at least one resource by using one or more of the -k,
-y, -n, or -o options."
Please let me know what is the use of mqsipackagebar which does not need toolkit but still needs workspace path for refering root location. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Feb 04, 2015 5:23 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
So you can have a "workspace" location on a system that does not support the toolkit... What's wrong with that? All it means is that the path to the resources to be added to the bar file needs to be relative to a specific directory (the workspace) and constant when relative to that directory....
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Feb 04, 2015 5:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
Vitor |
Posted: Wed Feb 04, 2015 5:41 am Post subject: Re: mqsipackagebar command - query |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
GeneRK4 wrote: |
Please let me know what is the use of mqsipackagebar which does not need toolkit but still needs workspace path for refering root location. |
It's for use on a Jenkins / Maven / other CI system which builds the resources but doesn't otherwise need the toolkit facilities. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
vishnurajnr |
Posted: Wed Feb 04, 2015 8:01 am Post subject: |
|
|
 Centurion
Joined: 08 Aug 2011 Posts: 134 Location: Trivandrum
|
Hi,
mqjeff wrote: |
I'm reasonably sure that mqsipackage bar still needs things that look like an eclipse workspace, with a root folder and subfolders that are eclipse projects. |
mqsipackagebar command does not need the toolkit/Eclipse workspace (its not mandatory, it will work fine from the eclipse workspace as well)
<root_location> -- Indicates the location where the source code artifacts are present (message flow project/Application/Libraries etc.).
You can configure a CI system, where it automatically checkout source code from SVN or other SCM to a directory and then using mqsipackagebar to build the BAR files (here the <root_location> should be the one you have configured as checkout directory).
So the <root_location> is the directory where you have checked out the source code - and not necessary to be an eclipse workspace.
Quote: |
Note: The 'mqsicreatebar' needs the eclipse/toolkit workspace folder structure to build. |
|
|
Back to top |
|
 |
mqjeff |
Posted: Wed Feb 04, 2015 8:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
vishnurajnr wrote: |
<root_location> -- Indicates the location where the source code artifacts are present (message flow project/Application/Libraries etc.). |
This is exactly what I said. The folder structure under <root_location> must look like an eclipse workspace, where each subfolder is a project - a message flow project, an Application, Etc.
I didn't say it had to be an eclipse workspace. Just look like one.
You can't just have a single folder with .msgflow, .xsd, .subflow files, etc. all higgeldy-piggeldy |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Feb 04, 2015 9:29 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
mqjeff wrote: |
You can't just have a single folder with .msgflow, .xsd, .subflow files, etc. all higgeldy-piggeldy |
As per Merriam Webster it is spelled higgledy, piggledy...
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
GeneRK4 |
Posted: Mon Feb 09, 2015 3:11 am Post subject: |
|
|
Master
Joined: 08 Jul 2013 Posts: 220
|
Thanks Vishnu and all..
We tried with mqsipackage bar with compiled flows(since it contained messageset;This step is what we missed earlier).Its working now with some local directory(not the Workspace path).
But,we tried to connect with svn path directly from mqsipackage bar.its not working
mqsipackagebar -a myflow.bar -w file:///D:\\SVNRepository/PCINew/Branch -k PCI01_GIFTCARD_V1_0
Same error as Root folder not available.
I think this provision is not there in mqsipackage bar command.So,as Vishnu specified ,we might have to checkout from SVN to some directory and then try using mqsipackagebar. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Feb 09, 2015 5:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
mqsipackagebar certainly doesn't know anything about any source control system.
Neither does mqsicreatebar - except in as much as the eclipse workspace it's using does.
So, yes, you can not get either mqsicreatebar or mqsipackagebar to automatically retrieve files from a source code repository. |
|
Back to top |
|
 |
GeneRK4 |
Posted: Mon Feb 09, 2015 10:14 pm Post subject: |
|
|
Master
Joined: 08 Jul 2013 Posts: 220
|
Thanks mqjeff...That helps  |
|
Back to top |
|
 |
|