Friday, 4 October 2013

Managing Snapshot Deactivation in IBM BPM

In IBM BPM ( Fixpack 1 ), the behaviour of the Deactivate Snapshot command / process has changed.

By default, any running instances will be, effectively, locked, so that they can no longer be used, although they won't actually be terminated.

This is the default for, whereas, apparently, in BPM 8.X, the default behaviour is back to the former i.e. active snapshot instances will continue to be usable, although ( of course ) new instances cannot be started.

The behaviour can be reversed, by adding two lines into 100Custom.xml, and restarting the AppTarget cluster: -

<block-deactivated-snapshot-favorite-progression merge="replace">false</block-deactivated-snapshot-favorite-progression>
<block-deactivated-snapshot-task-progression merge="replace">false</block-deactivated-snapshot-task-progression>

Note that it is vital to add merge="replace" or the setting will stay set to true which isn't cool :-)

This Technote ( for WLE ) provides more detail on the change: -

Having changed the default behaviour, I can now continue to progress instances for deactivated snapshots, although ( of course ) I cannot spawn new instances.


No comments: