Azure Thoughts, EAI Challenges

On of the demo’s during Developing Hybrid Solutions with Microsoft BizTalk Server 2013 and Windows Azure presentation talk was about connecting to Windows Azure Storage and pushing a document to a blob container. Based on that demo I created a TechNet Wiki article. What was missing in the demo was functionality to strip path from ReceivedFilename context property. I created a pipeline for it to do so and build the complete messaging solution . Here is the abstract of the TechNet Wiki article: BizTalk Server 2013 supports connectivity with Windows Azure through its new adapters WCF-BasicHttpRelay, WCF-NetTcpRelay, WCF-WebHttp and SB-Messaging. The relay adapters enables connectivity with relay service in Windows Azure Service Bus. SB-Messaging adapters provides means to connect to queue and subscriptions (topic). Finally the WCF-WebHttp for instance supports connectivity to REST endpoints. Windows Azure Storage and other services in Windows Azure and the cloud support a REST Int...

In a previous post I described my experience with installing and configuring BizTalk Server 2006 R2 Beta2. This time I wanted to try out one of the features of R2, WCF Adapter. I found an example of Stephen W. Thomas together with a video demoing WCF Adapter on BizTalk Server 2006 R2 Beta 1. Demo still applies for beta 2 with some differences in screens (wizard) when publishing the WCF Service. Below the first screen when one is using the wizard. I forgot to check enable metadata endpoint, there for in the config file of the service the following line was commented out: endpoint name="HttpMexEndpoint" address="mex" binding="mexHttpBinding" bindingConfiguration="" contract="IMetadataExchange " . So do not forget to check it. The rest of screens are the same as in the video. I also did not VS extensions for VisualStudio 2005 installed containing the WCF SDK. Generating the proxy was not possible without svcutil. As soon as I had it ins...