In this video, I’ll show you how to create an BRE policy to resolve itineraries and I’ll show you how to setup your BizTalk receive ports to use this policy. I’ll show you how to implement context and content based itinerary resolution.
These two new features allow us to implement a solution where a client no longer has to have any knowledge of itineraries. Now, they simply have to pass in their message to the ESB where it will dynamically figure out what itinerary is needed and it will load that itinerary from the database. In this video, I’ll show you how to implement this feature. To demo this feature, I use an InfoPath form which sends data to a generic OnRamp which uses the Itinerary Resolver. I’ll walk you through the process of storing your itinerary into the database, creating the new generic OnRamp that will use the itinerary resolution feature and I’ll show you how to configure the Itinerary resolver to retrieve the itinerary from the database.
In this demo, I show you how to do a number of new things. How to create an itinerary that compose three services together into a single composite service. How to setup your BizTalk environment to support this type of itinerary. Including how to create the send ports required for a composite service itinerary. How to retrieve information from a UDDI v3 server from within your itinerary. How to test resolvers inside visual studio using the resolver web service. How to implement dynamic mapping and dynamic routing inside an itinerary.
What I’ll be showing is how this can be implemented using the basic routing capabilities of the ESB 2.0. I’ll take you through the process of setting this up from start to finish. We setup the BizTalk components, define the Itinerary (which defines the process flow within the ESB) and we’ll test the end to end process. If any of those terms were new for you (i.e. itineraries, biztalk, uddi etc), then I would recommend you take a bit of time and review the basic concepts of the ESB guidance.
This video shows how to use a BizTalk ESB off-ramp to send messages to the Windows Azure platform Service Bus, using the WCF-Custom adapter and ESB Toolkit WCF-Custom Adapter Provider. This enables Windows Azure platform Service Bus interactions to occur as part of itinerary processing, participating as a first-class citizen in an ESB flow.
Shows how BizTalk and the ESB Toolkit 2.0 can be used in a process that uses dynamic messaging (message itineraries are dynamically selected based on rules engine evaluation of message content). In addition, it shows how SharePoint can be used to provide human intervention into a process, as well as BizTalk’s BAM capabilities. This is a compelling demo as the scenario is very simple, yet it really brings together and shows off the power of the Microsoft stack.
