HI,

Is there a way of forcing SB-Messaging adapter to use http insteed of tcp?

I am behind a firewall where I can't open the tcp ports.

I did a C# app where I by adding "ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Http;" solved the problem.

Can the same be done in BTS SB-Messaging adapter in?

/// Johan

According to the documentation the SB-Messaging Adapter permits HTTP & TCP/IP relay. So I'm assuming that the service on Azure is listening on TCP/IP in which case that is what you should be connecting to. If you can get the service to listen for HTTP then you;d be able to use that for the SB-Messaging configuration.

Regards.

Refer - http://msdn.microsoft.com/en-us/library/windowsazure/ff182819.aspx - Developing Applications that use Service Bus.

Refer - http://soa-thoughts.blogspot.in/2013/02/biztalk-server-2013-new-adapters-series.html - Azure Thoughts and EAI challanges.

• Edited by ShankycheilMicrosoft community contributor Monday, July 15, 2013 1:47 PM references
• Marked as answer by Chen Yu - MSFTModerator Tuesday, July 23, 2013 5:29 AM

I noticed that even with the WCF-BasicHttpRelay adapter in BizTalk 2013 the adapter requires an outbound connection to port 9351.

The ConnectivityMode.Http setting can be used to direct all traffic over ports 80 and 443. This is especially useful in customer environments where proxies typically allow traffic to ports 80 and 443 only.

With "netstat -a" I compared the connections between by BizTalk adapter and my custom service. The BizTalk adapter uses an outbound connection to port 9351 and the custom service does not.

There seems to be no way to change the behaviour of the BizTalk adapter as this adapter does not allow for extensions either.

There seems to be no way to change the behaviour of the BizTalk adapter as this adapter does not allow for extensions either.

Correct, the SB-Messaging adapter from BizTalk 2013 works only over TCP port 9351-9354 and not over HTTP.