| Author |
Message
|
| rrydziu |
 Posted: Fri Feb 10, 2012 1:24 am Post subject: mqsicreatebar -version parameter not working for all objects |
 |
|
Newbie
Joined: 21 Dec 2011
Posts: 8
|
Hi,
Some time ago I have faced problem with versioning objects in bar.
mqsicreatebar has a possibility to add -version parameter which
| Quote: |
| Appends the _ (underscore) character and the value of VersionString to the names of the objects added to the BAR file, before the file extension. |
Objects may be flows, java projects (compiled to jars), jars (copied from specified place), and message sets.
For flows, jars and java projects it is working fine, but message set .dictionary and xsdzip files are without version appended.
any idea how to make it work?
I have a problem that I would like to deploy into same ex group 2 bars with same message setobject in two different versions.
second thing is that:
even I have a renamed jar or dictionary - does it mean that there will be no conflict between two different versions? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Feb 10, 2012 5:53 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| rrydziu |
| Posted: Fri Feb 10, 2012 6:27 am Post subject: |
|
|
Newbie
Joined: 21 Dec 2011
Posts: 8
|
at first I thought the same, but it is not a typical property.
In cmf (compiled flow) it is visible as first element of MessageFlow - version.
Example:
| Code: |
| <MessageFlow><ConfigurablePropertyTable><Documentation><longDesc/><version value="$MQSI_VERSION=R2768 MQSI$"/></Documentation> |
So this is version and keyword at the same time.
when reading bar(mqsireadbar) I can see result:
| Code: |
SampleBar_R2768.bar:
SampleFlow_R2768.cmf (2/10/12 3:03 PM):
VERSION = R2768
Messagset.xsdzip (2/10/12 3:03 PM):
Messagset.dictionary (2/10/12 3:03 PM):
Deployment descriptor:
SampleFlow_R2768#additionalInstances
[..] some other properties with suffixed version
SampleFlow#something = Test
[..] other properties without suffixed version
|
there is one place where VERSION is set and there is no way to override it or at least I can't do this with mqsiapplybaroverride. |
|
| Back to top |
|
|
| ganesh |
| Posted: Fri Feb 10, 2012 7:15 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
|
| Back to top |
|
|
| rrydziu |
| Posted: Fri Feb 10, 2012 7:34 am Post subject: |
|
|
Newbie
Joined: 21 Dec 2011
Posts: 8
|
thanks for the link. I have seen this presentation, it is more like labelling flows with keywords.
What I like to obtain is to have possibility to deploy two flows in two different versions to same execution group. Keyword probably won't help. But VERSION may help (see slide 12th, VERSION!=version) - for now only partly: flows and jars have appended VERSION but message sets don't. |
|
| Back to top |
|
|
| ganesh |
| Posted: Fri Feb 10, 2012 9:15 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| There is a version tag inside the message set file, add some token there and then replace it using ant scripts during bar file creation or override. |
|
| Back to top |
|
|
|
|
