Saturday, October 31, 2009

BizTalk Performance

Here are some cool videos, docs and ppts about BizTalk Performance Testing Guidance:


BizTalk 2009 – End to end performance testing (1/2)

BizTalk 2009 – End to end performance testing (2/2)


Microsoft BizTalk Server Performance Optimization Guide

BizTalk Server Database Optimization


Microsoft BizTalk Server End-to-End Performance Testing Guidance

BizTalk Server 2009 VPC

We can download a BizTalk Server 2009 VPC Image from:

In this download, we get also a Hands-on Labs to test and practice BizTalk Server 2009.

Problem Enlisting SendPort 0xC00CE557

When we get "Could not enlist Send Port 'Port Name'. Exception from HRESULT: 0xC00CE557" error when we import a binding:

We have to check that Filter properties inside the binding file are correct.

HTTP Receive Location Errors

Here is a link with the errors and the solutions that a Http Receive Location we can get when we try to access it:

Also, we can get an Http 500 error, if we are using a incorrect version of the BtsHttpReceive.dll in our 32bit or 64bit environment.

Using Context Properties Inside a Map (ContextAccesorFunctoid)

In codeplex we can download a very cool functoid, that allows us to use properties from the message context inside a map.

We can get the functoid in this link:

And here are some links that show us how to use it:

Received a "System.NotImplementedException" in custom pipeline component

When testing our custom pipeline component, we could receive a System.NotImplementedException.

If we are using the Http adapter with our pipeline and we use the Data property from the Message.BodyPart, the error is because the Http adapter implements de Setter but not the Getter for this property.

In this case, we have to use the GetOriginalDataStream method, instead of Getter of Data property:

Stream myBodyStream = Message.BodyPart.Data (Incorrect)
Stream myBodyStream = Message.BodyPart.GetOriginalDataStream() (Correct)

Script to Update Receive/Send Pipelines

We can modify the receive and the send pipelines from an SQL script.

First of all, we need to know the pipeline Id value, from the BizTalkMgmtDb database:

select Id from dbo.bts_pipeline where [Name] = '<Pipeline Name>'

Then we can modify the pipeline from wichever send port or receive location:

update dbo.adm_ReceiveLocation set SendPipelineId = <Pipeline Id> where [Name] = '<Receive Location Name>'

update dbo.bts_sendport set nReceivePipelineId = <Pipeline Id> where [nvcName] = '<Send Port Name>'

The Messaging Engine failed to register an adapter

When we get this error:

"The Messaging Engine failed to register an adapter . Details: "Registering multiple adapter types within the same process is not a supported scenario. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process".

Probably we have at least two receive locations from different adapters in the same IIS AppPool.

We have to separate the receive locations from different adapters in different IIS application pools.

More information at:

Any Element Validation Error

Sometimes we need to add to our schemas an Any Element node, because we don't know the content of this node.

If we don't want any validation over this node, we must change the value of the Process Contents property and set to Skip.

Here are the values allowed for this property:

Mock Http Reflector

Only for test purposes, if we want to test our orchestration with an HTTP send port, we can use this code:

We can return the response that we want and test our orchestration.

Wednesday, June 03, 2009

Low Latency BizTalk

Here are some link to achieve low latency in BizTalk Solutions:

SOAP Adapter Configuration and Tuning Parameters:

Configuration Parameters that Affect Adapter Performance

Optimizing BizTalk Server Performance

FIX: Slow performance on startup when you process a high volume of messages through the SOAP adapter in BizTalk Server

BizTalk 2006 SOAP Adapter (Web Service call) in Messaging Only Scenario

Adding Custom SOAP Headers

1) Add a Property Schema to the solution:
2) The Target namespace of our property schema, should be
3) Add an element to this property schema, for example MyCustomSoapHeader. Set the Property Schema Base to MessageContextPropertyBase.
4) In orchestration, inside the Construct Message shape of the message that we send to web service, add a Message Assignement.
5) Inside Message Assignement, assign our custom soap header to the message context property: