Introduction to AppFabric Composite Apps

The Windows Azure AppFabric Composite Application service lets you easily build,deploy,run and manage applications that span application tiers and technologies. See how to build an application that composes multiple Azure services such as web roles,storage,Caching,SQL Azure,and ServiceBus,while leveraging familiarMicrosoft .NET developer experiences in Microsoft ASP.NET,Microsoft Silverlight,Windows Communication Foundation (WCF),and Windows Workflow Foundation (WF). Leverage the Composite Application service to easily provision,deploy,monitor,scale and manage this application as a cohesive unit throughout its lifecycle.
Watch the video here.

Hyperthreading – To enable or disable?

If you have been dealing with BizTalk 2009 or prior, you must have observed that it was always advised to turn off hyperthreading to get optimum performance in BizTalk. This is what is stated in the BizTalk Server 2009 Operations Guide:

  • It is critical that hyper-threading be turned off on BizTalk Server computers. This is a BIOS setting, typically found in the Processor settings of the BIOS setup. Hyper-threading makes the server appear to have more processors/processor cores than it actually does; however, hyper-threaded processors typically provide between 20-30% of the performance of a physical processor/processor core. When BizTalk Server counts the number of processors to adjust its self-tuning algorithms, the hyper-threaded processors cause these adjustments to be skewed, which is detrimental to overall performance.
  • Hyper-threading should be turned off on SQL Server computers because applications that can cause high levels of contention (such as BizTalk Server) may cause decreased performance in a hyper-threaded environment on a SQL Server computer.

However, one should make this decision about enabling or disabling hyperthreading based on the hardware. So,  with Intels Nehalem+ hyperthreading, is this advice still valid?

As per some tests carried out by the the CAT team, this is no longer the case….

Read more here!

The latest guide on improving server performance is available here.

BizTalk 2010 CU1 released

The MS team have released the first cummulative update for BizTalk 2010 and it can be found here.

The fixes include:

FIX: The WCF-SQL adapter from BizTalk Adapter Pack 2.0 or from BizTalk Adapter Pack 2010 does not write enough useful error information


FIX: A WCF-based SQL adapter may lock SQL Server resources when the PolledDataAvailableStatement binding property returns a positive result but the actual polling does not return any data


FIX: Statement in the PollStatement property incorrectly runs if a receive location uses WCF-based BizTalk Adapter for SQL Server


FIX: An update is available that adds the ClearRfcContext binding property to the WCF-based SAP adapter from BizTalk Adapter Pack 2.0 or BizTalk Adapter Pack 2010


FIX: Multiple grouped IDOCs are processed incorrectly if the WCF-based SAP adapter in BizTalk Adapter Pack 2.0 or BizTalk Adapter Pack 2010 uses the String setting to connect to an SAP system


Hotfix to add the “ReceivedIdocRelease” binding property for the WCF-SAP adapter to BizTalk Adapter Pack 2.0 and Microsoft BizTalk Adapter Pack 2010