| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Identifying deployable .msgflow files |
« View previous topic :: View next topic » |
| Author |
Message
|
| jamie_townsend |
 Posted: Wed Feb 13, 2013 11:30 am Post subject: Identifying deployable .msgflow files |
 |
|
Newbie
Joined: 09 Mar 2011
Posts: 4
|
Hi all,
WMB 7.x, mostly 7.0.0.4 on Windows.
We're in the process of automating the building of our bar files. The process currently looks through the given projects for a given fileset (defaulting to **/*.msgflow) and adds them to the mqsicreatebar command. This default picks up all .msgflow files, whether they're deployable or not. This of course breaks the bar creation when sub-flows are included.
What I'm looking for is a way to identify deployable .msgflow's. I know that the presence of at least one Input Node is the defining trait, but how can I figure that out?
I'd love to hear any suggestions, no matter how technical and involved.
Regards,
Jamie |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Feb 13, 2013 11:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
this is almost always left as a human decision, fed to an automated process through a configuration file of some kind.
Making the decision that a given msgflow is "deployable" or not would require that you read and parse the msgflow file itself. This is not as hard as it might sound, but it requires that you understand the internal meaning of the file, which *is* harder than it sounds and should be left to the Lab.
In v8, when you manually build a bar file, it will show you an mqsicreatebar / mqsipackagebar command to rebuild the bar file, so you can cut/paste that if you wanted - but you're not at v8 yet.
Again, think of this as a project level configuration for what is being built, rather than an automatically discovered piece of information. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Wed Feb 13, 2013 6:23 pm Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| Is that a custom built tool? One way you can do this easily is by following proper naming conventions for all your components, say for Main flows you can have a "_MessageFlow" and for a sub-flow you can have a "_SubFlow" and feed this info in your tool. Similarly for all other components. |
|
| Back to top |
|
|
| jamie_townsend |
| Posted: Mon Feb 18, 2013 10:09 am Post subject: |
|
|
Newbie
Joined: 09 Mar 2011
Posts: 4
|
| Yes, it's a custom build tool which does a few extra things before invoking mqsicreatebar. Naming conventions is a good solution for new projects, but we also have to deal with projects that were developed before the naming conventions were defined. |
|
| 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
|
|
|
|
