In a previous post, I started a series on explaining some of the new features of BizTalk 2013 in more detail. We started with a more detailed explanation on why BizTalk 2013 will be using the XslCompiledTransform API. You can find a list of the new features that BizTalk 2013 introduces on our earlier post.
In this next post in the serie, I would like to explain the announced ‘Improvements in dynamic send ports’… What has been changed in this new version of BizTalk?
BizTalk 2010 (& earlier)
Dynamic send ports where introduced already in an earlier version of BizTalk. However, unlike a static send port, you didn’t have the possibility to choose a BizTalk host that the ports send handler would run on. The dynamic send port will use the default send handler that is configured for the adapter that is being used. Meaning we are tied to using the same default Host for each dynamic port that uses the same adapter, which could cause separation of concern issues with bigger systems.
Or in other words… when you wish to run a dynamic send port using a different host, you are obliged to change the default send handler of the specific adapter. But keep in mind this will effect all dynamic send ports that are using this adapter as well.
BizTalk 2013 now has the ability to assign a host handler per adapter. This means you now have the possibility to configure a host to be used per adapter on a dynamic send port… providing more control on how your workload gets executed with dynamic send ports. This change will bring better scales and performance for dynamic send ports.
When adding a dynamic send port, you see there is a whole new Transport section in the General tab of the send port properties. By clicking on the Configure-button of the transport section, you’ll be able to choose which host must be configured as send handler for each available adapter.
Note however that the hosts that can be assigned to an adapter are the configured send handlers of the adapter. So you need to make sure that there is a send handler defined on the adapter configured to use your desired host. The chosen host no longer needs to be the default send handler defined for the adapter.