Tuesday, February 8, 2011

BizTalk Server 2010: The new Settings Dashboard

I was amazed when I looked at the new setting dashboard available in BizTalk server 2010 everyone who have tried to change the BizTalk settings would be happy. Now you get all the settings you need to tweak at one place instead of modifying registry entries, config files or making changes to the SQL table. I will walk through dash board and will mention the settings for which no UI was available before.
Group: Before no UI was available for group- level tracking you have to do it by making changes to the SQL table.
Host: The most interesting part here is that now Polling Intervals for Messaging and Orchestrations can be changed for each host before it was not possible to do. You normally need to change it for low-latency scenarios.
Now you need not to go to open registry editor to change values of the settings required for Resource Based Throttling.
Here added the UI for throttling override for publishing and delivery in BizTalk 2006 R2 you need to change the registry keys.
Now you can control the dehydration behavior of Orchestration from this UI.
Host Instances:Now you can change the number of worker and IO threads for each host instance from this dashboard.
And can also define Memory throttling for Orchestration for each Host Instance.

Cheers,
Rohit Sharma

2 comments:

Anonymous said...

Hi rohit thanks for such information.
I have one basic question, When to use enlist and what is the purpose of enlist?

Rohit Sharma said...

The BizTalk works using pub-sub pattern as shown in part 3. When you enlist some artifacts(send post, orchestration or parties in role link) the subscription get created. For detail on how to create subscription refers to part 6. When you enlist e.g. a send port then a subscription with the properties you defined in the filter (when creating send port) get created. You can think of a subscription as some entries in BizTalk database and whenever any message get received BizTalk engine checks the context properties of the message against these subscriptions to find out who(send ports, orchestrations etc.) is interested in receiving a copy of this message.

Post a Comment