Example for BizTalk 2013 to use the SB-Messaging and WCF-NetTcpRelay adapter

The BizTalk 2013 provides some new adapters for service bus to be able to use relay service and send/receive message to service bus queue and topics.

Recently Paolo Salvatori has upload an example demonstrate all of those features in here

I have set it up and tried it with one issue when calling netTcpRelay service in the demo client.

The demo client is using an app.config to call the netTcpRelayService. However, I have the error said, "The element 'bindings' has invalid child element 'netTcpRelayBinding'.

This because an extensions section needs to be added for the client to be able to recognize those element.

The client finally worked after the following config added.

<extensions>
    <behaviorExtensions>

<add name="transportClientEndpointBehavior" type="Microsoft.ServiceBus.Configuration.TransportClientEndpointBehaviorElement, Microsoft.ServiceBus, Version=1.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

</behaviorExtensions>

<bindingExtensions>

<add name="netTcpRelayBinding" type="Microsoft.ServiceBus.Configuration.NetTcpRelayBindingCollectionElement, Microsoft.ServiceBus, Version=1.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

</bindingExtensions>

</extensions>

This article here has a complete list for all the extensions that can be added. Just be aware that it is using 1.7.0.0, whereas the latest is 1.8.0.0 now.

Service Bus UnauthorizedAccessException token provider was unable to provide a security token while accessing custom STS

I installed the service bus for windows server on my windows server 2012. Then I setuped the new service bus farm and followed the tutorial on MSDN to test the brokered message queue client.

However, I am getting the error as below.

This error can not provide a security token for the user I setup run as from sb farm, which username@domain.

After some test, I realized the issue is caused by the run as user has to be given a full userdnsdomain name. So when you set up the service bus farm, make sure it is uisng username@domain.com format.

Then it worked as expected.

Difference between Azure Queues and ServiceBus Queues

MSDN just published a good article comparing the Windows Azure queues and ServiceBus queues, from performance, capacity and security perspective.

	Windows Azure Queues	ServiceBus Queues
Performance	10 miliseconds latency, support 2000 message per second	100 miliseconds latency, support 2000 message per second
Capacity	64KB message, 1TB data storage, 7 days TTL	256KB message, 5GB data storage, no limit TTL
Security	Security Token	ACS

My two cents with some finding in BizTalk and ServiceBus

1. BizTalk 2010 R2 is released a CTP, check the details from Mick.
    It is no surprsie for it to be aligned with the latest framework and tools.
    The interesting things for me is the adapters with the REST capability finally, and all the ServiceBus enabled adapters.  So here the support for ServiceBus is very interesting and need more details to see how BizTalk relationship with even the ServiceBus for Windows.

2. Just found this document about implementation with Windows Azure Servicebus, since really there is not many articles about it apart from the msdn.

3. An interesting topic about how to integration Dynamics CRM 2011 with azure service bus on MSDN,
Azure extensions for Microsoft Dynamics CRM

4. The ServiceBus EDI/EAI looks even much more promising especailly with the new mapper. However, I think we still need a BusinessRule engine support for decistion and runtime configuraion.