Team blog of MCS @ Middle East and Africa

This blog is created by Microsoft MEA HQ near shoring team, and it aims to share knowledge with the IT community.With its infrastructure and development sides,It brings to you the proven best practices and real world experiences from Subject Matter Experts
Follow Us On Twitter! Subscribe To Our Blog! Contact Us

Upgrade to Biztalk 2010

Upgrade to Biztalk 2010

  • Comments 1
  • Likes



This blog to consider some important information when upgrading to BizTalk 2010


Upgrade roadmap

For BizTalk 2006 R2 and 2009 can be upgraded directly to BizTalk 2010:

  • Upgrade from BizTalk 2006 R2 to BizTalk 2010
  • Upgrade from BizTalk 2009 to BizTalk 2010

But unfortunately upgrading directly from BizTalk 2006 to 2010 is not supported, so what you need to do in this case is to perform two stages upgrade:

  • Upgrade from BizTalk 2006 to 2006 R2
  • Then upgrade from BizTalk 2006 R2 to 2010.


Infrastructure Consideration

  • When upgrading to BizTalk 2009
    • Windows server 2003 and windows 2008 are supported.
    • SQL 2005 and SQL 2008 are supported
  • When upgrading to BizTalk 2010

    • Widows server 2008 and windows 2008 R2 are only supported
    • SQL 2008 and SQL 2008 R2 are only supported

    BizTalk 2010 upgrade considerations:

    • You cannot roll back to BizTalk Server 2009/2006 R2.
    • Trading Partners engine is completely different in BizTalk 2010 , as a result you need to run (party migration tool) to migrate parties from the old TPM to the new TPM model.
    • Human Workflow Services (HWS) is deprecated in BizTalk 2010.
    • When upgrading to SQL Server 2008 make sure that you install SQL Server 2005 notification services if you are using BAM alerts. This is required for enabling BAM alerts.
    • You must run a migrate command if you upgraded the SQL server (bm.exe migrate-sql)
    • SSO DB and Master Secret should be backed up before starting the upgrade process.
    • The BizTalk Server 2010 upgrade process requires the existence of the default host.
    • User-defined custom bindings that are built with earlier versions of the .NET Framework 4 will not be available after you upgrade to BizTalk Server 2010. To use the custom bindings, you have to manually add the custom bindings in the .NET Framework 4 machine.config file.
    • Before you upgrade to BizTalk Server 2010, you must back up all custom managed configuration files in BizTalk Server 2009/2006 R2. BizTalk Server 2010 supports migration of changes only in the btsntsvc.exe.config and bm.exe.config files



    i recommend to refer to this valuable documentation  




    Your comment has been posted.   Close
    Thank you, your comment requires moderation so it may take a while to appear.   Close
    Leave a Comment