TechReady: BizTalk Server 2009 R2 renamed to BizTalk Server 2010

This is something I'm glad about - the R2 numbering system just confuses people.

Following is list of key capabilities that have been added to BizTalk Server 2010.

  1. Enhanced trading partner management that will enable our customers to manage complex B2B relationships with ease

  2. Increase productivity through enhanced BizTalk Mapper. These enhancements are critical in increasing productivity in both EAI and B2B solutions; and a favorite feature of our customers.

  3. Enable secure data transfer across business partners with FTPS adapter

  4. Updated adapters for SAP 7, Oracle eBusiness Suite 12.1, SharePoint 2010 and SQL Server 2008 R2

  5. Improved and simplified management with updated System Center management pack

  6. Simplified management through single dashboard which enables IT Pros to backup and restore BizTalk configuration

  7. Enhanced performance tuning capabilities at Host and Host Instance level

  8. Continued innovation in RFID Space with out of box event filtering and delivery of RFID events

One interesting result of the renaming is that the lifecycle clock resets. For BizTalk 2009 R2, the 5 and 10 year support bands would have started with the release of BizTalk Server 2009 "R1" so you would effectively lose a year. For BizTalk 2010, the support bands start from its release ... some time in 2010.

Comments (4)
  1. Scott White says:

    No suffix and round numbers are fine but consistency is better, still no XPath or XSLT 2.0 == no big deal of a release IMHO

  2. MSDN Archive says:

    Hi Scott,

    BizTalk doesn’t have XSLT 2.0 support because the .Net framework itself only supports XSLT 1.0. We will need to wait on future plans (if any) to add XSLT 2.0 support in the .Net framework. I’ll ask around and see what I can find.


    John Breakwell (MSFT)

  3. MSDN Archive says:

    No news as yet.

    I did find that the XML team here at Microsoft were talking about XSLT 2.0 over three years ago:

    They recommended using the Open Source SAXON XSLT processor from Saxonica.


    John Breakwell (MSFT)

  4. Kent-FPNA says:

    I have seen several posts from Microsoft about not supporting XSLT 2.0.  It seems that XML group prefers XQuery over XSLT 2.0.  This is fine, but WHY would Microsoft build an integration system such as Biztalk which handles 100% XML messages to support to use XSLT versus XQuery in the mapper?  The resulting XML Schemas for SAP IDOCS are horrible and without the tools in XSLT 2.0 it is nearly impossible to build maps that either using the native mapper or custom XSLT 1.0 code.  I am finding that I need to build transformations through external Assemblies that have access to XML parsers that support XSLT 2.0.  Why not implement the ability to choose different XML parsers, so I can choose a different engine to execute the XSLT under the hood of the mapper, since Microsoft is conflicted about implementing XSLT 2.0?

Comments are closed.

Skip to main content