The good and bad news about the ESB Guidance 2.0 CTP announcement

Let me start with the good news, the Microsoft announced the long expected version 2.0 of the ESB guidance. The present version is about a year old (November 2007) so it was time the lessons of the 1.0 version would result into a 2.0 version. Also some people doubted that Microsoft would invest into a second version of the guidance because it was quiet for some time. However on CodePlex the team announced a follow up already in July.

How about the bad news? Well, the bad news is that it is only available for Micrsoft BizTalk Server TAP customers, at least for now. This CTP is targeted for BizTalk Server 2009 so I guess that it will take some time before we can play with it since BizTalk Server 2009 is scheduled for first half of next year. Although I expect the first public CTP of BizTalk Server 2009 to be available soon.

So, what is actually new and changed in this version?

New Features and Components:

  • New samples. This version includes the following new samples:
    • SSO Configuration provider for Enterprise Library 4.0
    • Multiple Web Service Execution Sample
    • Exception Handling Service Sample
  • New ESB Web services. This version includes the following new ESB Web services:
    • Generic Itinerary Services ( no itinerary header required)
  • New core features. This version includes the following new core features:
    • Alignment with Microsoft BizTalk Server 2009 ( Beta )
    • ESB Configuration tool
    • Centralized itinerary store
    • Itinerary resolver components
    • Itinerary forwarder pipeline component
    • Itinerary selector pipeline component
    • Itinerary designer
    • Centralized configuration uses Enterprise Library 4.0 Configuration Block
    • Centralized caching uses Enterprise Library 4.0 Caching Block
    • Multiple service invocation using both messaging and orchestrations
    • Itinerary BAM tracking
    • Improved ESB Core engine and itinerary execution

Changes to Existing Features and Components:

  • Modifications. This version includes modifications to the following features:
    • Resolver and Adapter Provider Framework. This version consolidates the Dispatch and Transform classes to support batch routing of messages within the Dispatch pipeline component using document specification type, and support for itineraries.
    • Itinerary caching pipeline component. This version uses Enterprise Library 4.0 configurable cache management.
    • UDDI Publisher Utility This version supports UDDI3 only with publishing endpoints using publisher-defined key.
    • General bug fixes.
  • Retired features. This version retired the following features:
    • None.

You can read more about it on the Architects Rule blog and here. Also Charles Young mentioned it a while ago but didn’t go into feature details.