A Technology Influencer's musings

A blog exploring the various learning's I have in my day to day role at Microsoft. Currently I'm a technology strategist in the Enterprise Products team and most of my blogs focus on what I think it takes to do that job well.

ESB Toolkit How To Video #7: A SharePoint Adapter Provider

ESB Toolkit How To Video #7: A SharePoint Adapter Provider

  • Comments 2

Welcome to #7 in my series of ESB Toolkit How To Videos. If you have not seen the previous videos, I encourage you to do so. The previous ones can be found here

1) Basic Itinerary Routing and UDDI Integration

2) Composite Itinerary and Dynamic Mapping

3) Itinerary Resolution in the Bus

4) Dynamic Itinerary Resolution in the Bus

5) Including Custom Orchestrations in the Itinerary Designer

6) Performance Metrics using Built in BAM

One very common thing that people will want the ESB to do is to route message to SharePoint where they can potentially kick off human based workflow. However, the base ESB Toolkit does not have an adapter provider for Windows SharePoint Services. BizTalk does have an "Adapter" for WSS, however the ESB toolkit does not have an "Adapter provider" for WSS. The Adapter Providers in the ESBT bridge between the new ESBT code and the traditional BizTalk components.

Now fortunately, the ESBT can be extended very quickly and we can add in our own adapter providers without the need for very much code at all. This past week, I was working with the guys over at QuickLearn to build out a WSS adapter provider that they planned to use in an upcoming BizTalk/ESBT demo.  In this video, I'll show you how we created the adapter provider (using only a few lines of code) and how we registered it so that the design time tools and the runtime engine could use it. Now, while creating the adapter doesn't require much effort, I will admit that I had a hell of a time trying to get it registered properly and all of the associated configuration files aligned correctly.  The ESBT relies heavily on reflection to load components at runtime, so if you don't name your component properly or register it correctly in the config files, then the ESBT engine won't be able to load the provider properly and you'll have a fun time trying to debug just exactly what you did wrong.

In order to make it easier for you, I've included my code and configuration files for download so that you don't have to rebuild everything that I show in the video.

I need to credit Nick Hauenstein over at QuickLearn (http://www.quicklearn.com/) for doing most of the initial leg work on building this out.

You can access the video here

You can download the project here

Cheers and keep on BizTalking

Peter

Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post
  • nice! thanks for another excellent video and nice addition of the source code too.

    building adapter providers is easy; but like you say the registration can be a bit of a headache.

  • Hi, your post is very interesting. I begin with the BizTalk server and I would use SharePoint with the ESB technology.

    I followed your video and take your project to test it on my BizTalk server but I always have a problem in ESB with the endPoint configuration.

    The error I always become when I want to configure the endpoint is the following: The adapter nammed Windows SharePoint Services does not have a valid manifest file or the file '' was not found.

    Is there a further step that I have to do to make it work ?

    Thank your in advance for your help.

    Lauriane

Page 1 of 1 (2 items)