| Author |
Message
|
| j1 |
 Posted: Thu Feb 02, 2012 2:18 pm Post subject: Overriding message flow name property |
 |
|
Centurion
Joined: 23 Jun 2003
Posts: 139
|
Im using mqsiapplybaroverride to have different versions of the same flow reading from different sets of input,output and audit queus. Id like to not have to use different execution groups just to differentiate the different versions of the flow from an adminsitrative point of view. Can I also override the name so that it shows up under different names, when deployed to the same broker execution group?
Cheers |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Feb 03, 2012 5:36 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
You need to use package names. The WM663 class advocates never ever use default package names.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Last edited by lancelotlinc on Fri Feb 03, 2012 6:16 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 03, 2012 6:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Lancelotlinc - so you're saying that he should manually make multiple copies of the same message flow and put each copy in a different package, thus actually having lots of different copies of what is really the same message flow under change control?
I'd just go with the -version flag on mqsicreatebar myself. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Feb 03, 2012 6:13 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
I suppose I need to explain further. You can have a common subflow that performs the functionality that you want. Then a very minimal main flow, with unique package name for each instance of the I/O desired. The bar overrides can reference each package independently, thereby avoiding the need to make separate execution groups.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 03, 2012 6:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| Then a very minimal main flow, with unique package name |
That must be manually copied or instantiated from a pattern, and still exists as an independent resource in change control.
 |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Feb 03, 2012 6:37 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Yes, it is a compromise. It is not optimal. If WMB supported dynamic namespace bindings, it would be more optimal.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 03, 2012 6:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| Yes, it is a compromise. It is not optimal. If WMB supported dynamic namespace bindings, it would be more optimal. |
And yet the -version flag on mqsicreatebar works around the need to compromise in this area. It allows one to compromise against having a one-to-one relationship between deployed artifacts and change control artifacts, whilst still maintaining a direct auditable path between change control artifacts and deployed artifacts. |
|
| Back to top |
|
|
|
|
