Presenting the best practices for BizTalk configuration
As we have seen, BizTalk is a capable, scalable, and a powerful platform for running messaging and middleware solutions. However, more often than not, it is not configured in a way that maximizes its potential. The default configuration for BizTalk creates only one host and one host instance; this means, by default only one .NET thread pool will be used to run all the processing performed by BizTalk, including receiving, sending, orchestration, tracking, and BAM. Under these circumstances, it is very easy for a BizTalk Server to underperform. Typical signs will include low throughput combined with low CPU utilization. Often, the root cause is thread starvation as different parts of BizTalk ...
Get Microsoft BizTalk Server 2010 Patterns now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
