MQSeries.net :: View topic - WMB V6.0 deploying subflows independently

brokendrum

We are trying to migrate from WMQI 2.1 to WMB V6.0. Our current 2.1 code uses subflows as a way of managing changes which can be deployed without impacting other subflows:

MessageFlow1
.....L RulesSubflow1
.....l.......L ReformatSubflow1
.....l.......L ReformatSubflow2
.....l.......L ReformatSubflow3
.....L RulesSubflow2
.............L ReformatSubflow4
.............L ReformatSubflow5

For example we can deploy changes to ReformatSubflow3 without impacting any other component as follows:

mqsiassign brokername -f ReformatSubflow3 -e execGroupName
mqsideploy brokername -e egroup -d

However if we wanted to deploy changes to ReformatSubflow3 in WMB V6.0, MessageFlow1 must be included in the bar file which would also deploy any pending changes to MessageFlow1. Also, whilst other subflows could be removed using the Message Broker Toolkit to avoid their deployment this cannot be done at the command line.

I could replace all the input terminals with MQ input nodes however that will create an additional overhead and the message flow would be split from one to three units of work.

1) Is there any way of deploying only the changes to ReformatSubflow3 without deploying changes to any other components (specifically at the command line)?

2) Is there any way of deploying only the changes to MessageFlow1 without deploying changes to any other components (specifically at the command line)?

Thanks,

Dave