Tuesday, September 25, 2007
BizTalk 2006 and R2 now doesn't require an atomic scope for calling rules
I didn't know this, but in BizTalk 2006 and R2 its no longer required to wrap a "call rules" shape in an atomic scope.
In BizTalk 2004 it was required but this is no longer the case. Be careful though, because the atomic scope served to protect the orchestration's processing from the potential problem of an error occuring and a persistence point being reached which will re-run the message which has been passed thru the rules again.
Take a look at your process and decide whether there is any risk of the message being run a second time, if not, save the performance hit if an atomic scope and just use the call rules independently.
In BizTalk 2004 it was required but this is no longer the case. Be careful though, because the atomic scope served to protect the orchestration's processing from the potential problem of an error occuring and a persistence point being reached which will re-run the message which has been passed thru the rules again.
Take a look at your process and decide whether there is any risk of the message being run a second time, if not, save the performance hit if an atomic scope and just use the call rules independently.
Labels: Business Rules Engine