Apr 182012

So Joe and I were talking and I was showing what I was doing, here and he said I should be blogging about this since it doesn’t appear to be documented anywhere.

The resolver I made is a separate one so it can work on getting the endpoint configuration. Here are the steps I used to configure the endpoint in the Itinerary Designer.

  • Created the service schemas using the Visual Studio WCF Wizard
  • Created the map that creates the request message
  • Opened the binding file that is created as part of the project
  • Set the Resolver to Static and set the adapter to the appropriate binding (WCF-BasicHttp in my example)

Enter the following values:


On the Endpoint Configuration:


So now you have everything set in the Endpoint configuration.

Now to move all of the settings to the BRE:


So how do you get the Endpoint Configuration into the Set End Point Configuration to section? Simply highlight the value in the Endpoint Configuration and copy (control-c) and go the BRE and paste

Publish and Deploy

Set the Resolver to BRE

Choose the Policy from the drop-down



The second tip is how to refer to XPath directly in the BRE from the BRE resolver

When you refer to a schema, remedy make sure you click on the root node and change the Document Type to Microsoft.Practices.ESB.ResolveProviderMessage and now you can drag the attributes/elements into your rules with confidence that the rule will fire. (Make sure you type the Document Type correctly Microsoft.EDB.ResolveProviderMessage will cause the rule not to fire Smile with tongue out)


Voilà deux