Issue with Updating Receive Shape Filters in BizTalk 2006 R2
If you’ve worked with Receive Shape filters in BizTalk Server 2006 R2, you may have found that updating existing filters is sometimes problematic, in that the change isn’t always applied after deploying it.
I set out to find out when this issue occurs, and what the resolve is. I added a condition to an existing Receive Shape filter, and deployed to see if the change was applied (new filter conditions are highlighted in red):
After deploying, I ran a query in the Administration Console Group Hub to check the subscription…
I ran the query, and in the results I clicked on the orchestration (for which I modified the Receive Shape Filter) to see the subscription details (new conditions highlighted in red):
In this case, after adding new conditions to the filter, there were no issues in the changes being applied after deploying. So far, no problem.
Next I tried removing the condition I had previously applied in the Receive Shape filter, and re-deployed. This time, after checking the subscription filter in the Group Hub, I found that the change was NOT applied. Restarting the Host Instances and refreshing the application in the Administration Console had no effect.
I was curious as to whether this was just an issue with the Subscription Details screen not reflecting the change in the Group Hub. I tried processing a message, and sure enough, BizTalk was not applying the latest Receive Shape filter.
The solution is actually very simple: Ensure that the BizTalk Server Administration Console is closed when you deploy changes for Receive Shape filters. The Admin Console caches various items, which apparently causes this issue (exactly what it caches is not something I can answer). And it’s worth mentioning that I already have BizTalk Server 2006 R2 Cumulative Update 3 installed.
And so if you’re adding new conditions to a Receive Shape filter, you shouldn’t need to worry. But if you’re deploying changes where the Receive Shape filter conditions were modified or removed,then make sure to close the Admin Console before deploying.