Call REST services from BizTalk Server 2010

March 14, 2011 LeandroDG 7 comments

I was having some trouble consuming REST services from Biztalk Server 2010.

The first and easy thing to try is creating a Send Port with WCF-Custom adapter and configuring webHttpBinding as the binding and webHttpBehavior as the behavior.

But it doesn’t work inmediately, when you send a message with this configuration, you’ll get the following error:

The adapter failed to transmit message going to send port "SampleSendPort" with URL "http://localhost/SampleSite". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.InvalidOperationException: Manual addressing is enabled on this factory, so all messages sent must be pre-addressed."

So, I tried another solution that I read around, use webHttpBehavior but instead of webHttpBinding, use a custom binding just like webHttpBinding but with manual addressing turned off. This looks like this:

The problem is that webHttpBehavior expects ManualAddressing to be turned on, so it throws this error:

The adapter failed to transmit message going to send port "SampleSendPort" with URL "http://localhost/SampleSite". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.InvalidOperationException: In the endpoint at 'http://localhost/SampleSite', in order to use 'System.ServiceModel.Description.WebHttpBehavior', the 'HttpTransportBindingElement' of the binding must have ManualAddressing set to true."

So, I got rid of webHttpBehavior, and the messages were being sent without issues. If the endpoint couldn’t be reached, it would throw an error correctly in Biztalk and the message instance would get suspended. But when the server threw a 500 error (Internal Server Error), the message would dissappear and no error would show up.

Finally I decided to use webHttpBinding, webHttpBehavior but also add a custom behavior that configures the address and the method for the call. I took the code for this from here: http://social.msdn.microsoft.com/Forums/eu/biztalkesb/thread/c19d7486-0705-433f-8e1a-a9088d076ed7. And it ends up looking like this:

WebManualAddressingBehavior.cs:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.ServiceModel.Description;
using System.ServiceModel.Dispatcher;
using System.ServiceModel.Channels;
using System.ServiceModel;
using System.ServiceModel.Configuration;
using System.Configuration;

namespace Logue.Library.WebManualAddressingBehavior
{
    public class WebManualAddressingBehavior : IEndpointBehavior, IClientMessageInspector
    {
        public string Method { get; set; }
        public Uri ManualAddress { get; set; }

        public WebManualAddressingBehavior()
        {
        }

        public WebManualAddressingBehavior(string _method, Uri manualAddress)
        {
            Method = _method;
            ManualAddress = manualAddress;
        }

        public void AddBindingParameters(ServiceEndpoint endpoint, System.ServiceModel.Channels.BindingParameterCollection bindingParameters)
        {
        }

        public void ApplyClientBehavior(ServiceEndpoint endpoint, System.ServiceModel.Dispatcher.ClientRuntime clientRuntime)
        {
            clientRuntime.MessageInspectors.Add(this);
        }

        public void ApplyDispatchBehavior(ServiceEndpoint endpoint, System.ServiceModel.Dispatcher.EndpointDispatcher endpointDispatcher)
        {
        }

        public void Validate(ServiceEndpoint endpoint)
        {
        }

        public void AfterReceiveReply(ref Message reply, object correlationState)
        {
        }

        public object BeforeSendRequest(ref Message request, IClientChannel channel)
        {
            request.Headers.To = ManualAddress;
            HttpRequestMessageProperty property = new HttpRequestMessageProperty();
            property.Method = Method;
            property.SuppressEntityBody = true;
            request.Properties.Add(HttpRequestMessageProperty.Name, property);

            return request;
        }
    }
}

WebManualAddressingBehaviorExtensionElement.cs:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.ServiceModel.Description;
using System.ServiceModel.Dispatcher;
using System.ServiceModel.Channels;
using System.ServiceModel;
using System.ServiceModel.Configuration;
using System.Configuration;

namespace Logue.Library.WebManualAddressingBehavior
{
    public class WebManualAddressingBehaviorExtensionElement : BehaviorExtensionElement
    {
        //Constructor to create instance of endpoint behavior and initialize with two property values.
        protected override object CreateBehavior()
        {
            return new WebManualAddressingBehavior(Method, ManualAddress);
        }

        public override Type BehaviorType
        {
            //Return configuration element type to be used in the behavior.
            get
            {
                return typeof(WebManualAddressingBehavior);
            }
        }

        [ConfigurationProperty("Method", DefaultValue = "GET", IsRequired = true)]
        public string Method
        {
            get
            {
                return (string)base["Method"];
            }
            set { base["Method"] = value; }
        }

        [ConfigurationProperty("ManualAddress", DefaultValue = "", IsRequired = true)]
        public Uri ManualAddress
        {
            get
            {
                return (Uri)base["ManualAddress"];
            }
            set { base["ManualAddress"] = value; }
        }

        //Copies the content of the specified configuration element to this configuration element
        public override void CopyFrom(ServiceModelExtensionElement extFrom)
        {
            base.CopyFrom(extFrom);
            WebManualAddressingBehaviorExtensionElement element = (WebManualAddressingBehaviorExtensionElement)extFrom;
            Method = element.Method;
        }

        //Represents a collection of configuration-element properties
        private ConfigurationPropertyCollection _properties;

        /// Both properties are returned as a collection.
        protected override ConfigurationPropertyCollection Properties
        {
            get
            {
                if (_properties == null)
                {
                    _properties = new ConfigurationPropertyCollection();
                    _properties.Add(new ConfigurationProperty("Method", typeof(string), "", ConfigurationPropertyOptions.IsRequired));
                    _properties.Add(new ConfigurationProperty("ManualAddress", typeof(Uri), "", ConfigurationPropertyOptions.IsRequired));
                }
                return _properties;
            }
        }
    }
}

You need to GAC this behavior assembly and modify both 32-bit and 64-bit machine.configs, in the following paths: “%WINDIR%Microsoft.NETFrameworkv4.0.30319Configmachine.config” and “%WINDIR%Microsoft.NETFramework64v4.0.30319Configmachine.config”.

In the system.serviceModel/extensions/behaviorExtensions section, add the following line:

<add name="webManualAddressingBehavior" type="Logue.Library.WebManualAddressingBehavior.WebManualAddressingBehaviorExtensionElement, Logue.Library.WebManualAddressingBehavior, Version=1.0.0.0, Culture=neutral, PublicKeyToken=be30eb01119b89a8" />

It should look like this:

And then, you should be able to add it to the send port configuration, so you can set the method and the address:

When configured like this, an error on server side will generate an exception on Biztalk send port as expected, like this:

The adapter failed to transmit message going to send port "SampleSendPort" with URL "http://localhost/SampleSite". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.ServiceModel.CommunicationException: Internal Server Error

Downloads:
WebManualAddressingBehavior Source Code (229)
WebManualAddressingBehavior Binaries (163)

VN:F [1.9.11_1134]
Rating: 3.7/5 (3 votes cast)
Categories: Development Tags: , ,

Tellago Studios SO-Aware at Microsoft TechReady!

February 15, 2011 adglopez No comments

Tellago Studios’ Chief Architect Jesus Rodriguez will be presenting a session about SOA Governance on the Microsoft platform using SO-Aware at Microsoft TechReady.

This week Microsoft is hosting the first edition of their annual TechReady conference. Even though TechReady is an internal conference, Microsoft invited us to present a session about how to enable Agile SOA Governance on the Microsoft platform using our recently release product: SO-Aware.

As part of our session, we will take a look at the current challenges that organizations face when enabling SOA governance capabilities on the Microsoft platform and how organizations can benefit from  more agile, lightweight and modern SOA governance models.

The session will provide a practical view to the role of Tellago Studios’ SO-Aware as an essential technology to enable native SOA governance on the Microsoft platform. We will explore in detail important capabilities of SO-Aware such as

  • Centralized service repository
  • Centralized configuration management
  • Service testing
  • Monitoring
  • Transparent integration with technologies such as Visual Studio, BizTalk Server, Windows Server & Azure AppFabric among many others

But the fun doesn’t stop there…..

As part of this session, we will showcase for the first time our upcoming SO-Aware Test Workbench product which enables load and functional web service testing capabilities on the Microsoft technology stack.

SO-Aware Test Workbench provides developers with a visually rich environment to model and control the execution of load and functional tests in a SOA infrastructure. This tool includes the first native WCF load testing engine allowing developers to transparently load test applications built on Microsoft’s service oriented technologies such as WCF, BizTalk Server or the Windows Server or Azure AppFabric.

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)

SO-Aware at TechReady!

I’m happy to announce that Tellago will be presenting a session on Techready on SOA governance using our product SO-Aware!

And for the first time we will be presenting SO-Aware Test Workbench, an environment that allows modelling and controlling execution of load and functional tests in a SOA infrastructure.

More information at: http://www.tellagostudios.com/blog/so-aware-highlighted-microsoft-techready

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
Categories: Development Tags: ,

Use VHD disk from Virtual PC / Hyper-V on VMware

October 18, 2010 LeandroDG No comments

Lately I’ve been working with Virtual PC’s that use VHD’s disks. As I don’t have Hyper-V on my computer, I wasn’t able to load the VHD disk I got that contained a 64-bit OS, because neither Virtual PC 2007 nor Microsoft Virtual PC support 64-bit guest OS’s.

So I needed to use it on VMware, that supports 64-bit guests, to configure some stuff and then return the VHD file to my team. The best way to go around this, as they need to use that modified disk again on the Hyper-V environment, was to create a differential disk from the VHD so I only share with them the resulting diff disc (else I’d have to upload a 40GB disk with all the changes through my slow internet connection).

But the problem is that, there’s no way to transform it to VMDK and back to VHD and keep only the differential disk. So transforming it to VMDK and later moving it back to VHD is not a possibility.

I’ve found that there’s a way to import it inside VMware and share the VHD instead of using a copy, so I thought it may be of help for others.

  • Create Differencing VHD
    • First, to create the differencing VHD disk, open up Windows Virtual PC or Microsoft Virtual PC 2007.
    • Create a new Virtual PC.
    • When creating the virtual hard disk, select Create a virtual hard disk using advanced options, and click Next.

       
    • Select Differencing.

       
    • Type in the name of the Differencing VHD.

       
    • Select the original VHD file (it should be read-only just to be safe you don’t modify it).

       
    • Click on Create. This will create a new Virtual PC based on the VHD disk with a new differencing disk that you’ll now import into VMware.
  • Import Virtual PC into VMware
    • Open VMware.
    • Go to File, select Import or Export.
    • For Source Type, select Other.

       
    • Select the VMC file for the Virtual PC you previously created.

       
    • In Source Data, select Convert all disks and mantain size.. This step is very important, as if you select anything else you won’t be able to use the VHD as source and VMware will force you to convert the disk to VMDK format.

       
    • For Destination Type, select Other Virtual Machine.

       
    • Type in the name of the VM you want to create.

       
    • Now select Share source, this option is only enabled because you previously selected Convert all disks and mantain size.. This allows VMware to use VHD instead of VMDK as the virtual hard drive.

       
    • Carry on with the rest of the wizard and the summary screen should look like this.

       
    • After the process ends, you should end up with a screen similar to this one.

       
VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)

SO-Aware Webinar on August 25, 2010

September 16, 2010 adglopez No comments

Hey everyone,

For those that don’t know what SO-Aware is, simply put, it is a Web Service Metadata Repository which supports WCF, ASMX, SOAP, JAVA, REST and OData services. You can read more about it here: (http://www.tellagostudios.com/products/so-aware%E2%84%A2″).

For all those using SO-Aware as a replacement for UDDI, web service discovery and WSDL organization, we have a free webinar that you can view to see how to use WCF/SOAP/REST services with SO-Aware. Check it out if you have a chance. (http://www.regonline.com/register/checkin.aspx?EventId=882502)

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)