locked
Migration approach strategy and Effort estimation for migrating BTS 2009 Application to BTS2013 RRS feed

  • Question

  • We got a requirement from customer that to migrate one of the BTS 2009 application into BTS 2013.He asked us to give Migration approach and Effort estimation.

    I am new to estimation of migration projects.please help what migration strategy to follow and how to estimate the effort for migration.

    Let's Assume: The existing BizTalk 2009 -ABC application is having 20 schemas,20 maps,10 orchestration.so to  migrate the application how much efforts is required including SIT,UAT and Go-live 

    Please share  your thoughts and any doc/templates.

    1. What are the activities to be covered in migration(WBS)

    2. How to calculate efforts for old version of biztalk to new version of biztalk application

    3.what are testing strategies to cover in migration project

    • Edited by BizQ Thursday, December 25, 2014 6:17 AM
    Thursday, December 25, 2014 6:15 AM

Answers

  • Hi,

    Migration from BT2009 to BT2013 is quite a hot topic these days on the forum. :) Seen lot of queries regarding this.

    #1 Regarding what approach to take for the migration, I think it is will explained in the installation guide provided by Microsoft @ Upgrade from BizTalk Server 2009 to BizTalk Server 2013. For me its the one stop shop for the information related to migration.

    Visual Studio projects developed for BizTalk Server 2009 can be migrated to the BizTalk Server 2013 R2 environment by using the Visual Studio Conversion Wizard, you cannot use BizTalk 2009 MSI's directly.

     

    #2 Regarding the estimation, there is no set formula or automated tool to calculate the time. It depends majorly on the infrastructure, applications etc. It takes experience, judgement and know-how to be able to estimate how many man-hours (effort) will be required for a given set of BizTalk tasks.

    You need to keep in mind about the following things while estimating the efforts.

    1) Database Migration.

    BizTalk application may rely on databases for configurations and data archiving. Such databases need to be migrated to the new infrastructure. 

    2) BizTalk Application Migration.

    As discussed, Visual Studio 2012 Conversion Wizard can be used to convert the Visual Studio 2005 projects into Visual Studio 2012 project.

    3) Trading Partner Configuration Migration

    Before you start upgrading to BizTalk Server 2013, you must run the Microsoft BizTalk Server Party Migration Tool (Party Migration Tool) to migrate the party-specific data from BizTalk Server 2006 R2 or BizTalk Server 2009 to the new TPM model in BizTalk Server 2013.

    If you have parties with Electronic Data Interchange (EDI) data, you will have to migrate the party data from old Trading Partner Management (TPM) model to new TPM model.

    4) Certificates Migration

    5) BRE Policies and Vocabularies Migration

    Migration of BRE Policies and Vocabularies from BizTalk 2009 to BiTalk 2013 via BRE Policies and Vocabularies Export/Import may work but is not supported by Microsoft. The business rules may have to be build from scratch on the BizTalk 2013 environment.

    6) BAM Activities Migration

    BAM activities will be migrated by re-deploying the BAM Activities definition files using the bm.exe utility.

    Refer this article for the details about each component migration in detail: BIZTALK 2006 R2/2009 TO BIZTALK 2013 MIGRATION APPROACH

     #3 Regarding the testing strategies you can refer this article Testing Strategy.

    Rachit 

    Thursday, December 25, 2014 8:36 AM
    Moderator
  • Is your Biz Talk Environment design  is part of your scope ?  or is it only the code Migration activity which you will be considering .

    If you are working with code Migration only then list of task which you need to perform are as follows

    1) Migrate Existing .net class library to 4.0 .Net framework . 

    2) Migrate BizTalk Projects through Visual studio Migration Wizard ( one Migration is completed you need to change project properties to point to 4.0 framework)

    approach can be sub divided into two :

    • Backup Visual Studio projects.
    •     Convert projects in Visual Studio through Visual Studio Conversion Wizard (For troubleshooting see)
    •     Compile the solutions against .NET Framework.
    •     Build and deploy.

      Or
          Backup Visual Studio projects.
    •     Recreate projects in Visual Studio 2013.
    •     Copy old artifacts from the old projects into the new project.
    •     Compile the solutions against .NET Framework.
    •     Build and deploy.

    3) If you are using BAM then you need to deploy all the activities which are part of earlier version 

    4) Similarly you need to Migrate Rule engine if it is being used .

    5)There are certain consideration which you need to take care of if you are using IBM MQ  as well . With BizTalk Migration you need to migrate some of the source and destination system as well which are not being supported with BizTalk 2013

    6) There are also mapping change in BizTalk 2013 . So you need to test Each map separately to see its working fine or not . It will add to your Work breakdown task.  There are certain restrictionin mapping in bizTalk 2013 which is being listed below .

    • Only public methods may be called from XPath expressions.
    • Overloads are distinguishable from each other based on the number of arguments. If more than one overload has the same number of arguments, an exception will be raised.

    You need to see below blog to understand the change in biztalk 2013

    What the BizTalk Server 2013 Mapper Updates Mean for You

    Andrei Kosmynin has written a good post here BizTalk 009 to BizTalk 2013 Migration  which tells you benefits and the scope of Migration which you need to understand before developing final WBS

    • BAM Activities Migration
    • BRE Policies and Vocabularies Migration
    • Exporting BRE Policies and Vocabularies from BizTalk Server 2009
    • Importing BRE Policies and Vocabularies into BizTalk Server 2013

      Certificate Export/Import
    • Windows Server 2003 to Windows Server 2012
    • Choosing an Export Format
    • Exporting a Server Certificate from Windows Server 2003
    • Importing a Server Certificate to Windows Server 2012

    There are some good post written by Steef jan  and over MSDN which you follow

    BizTalk Application Migration Guide by Steef Jan

    Troubleshooting BizTalk Server Migration in BizTalk 2013

    At last i can say WBS  depends on the team, whether they're confortable with Biztalk or not (and have they done integration projects - really different from doing a web site)..

    I would suggest to take reference from an old post over MSDN

    BizTalk project estimation for man-hours or person-days

    Now coming to your last point about  testing strategy Michael Stephenson has described various approach for this in his blog post  . 

    Michael Stephenson Mapping strategy

    Test Effort Estimation: Learning from an experience

    I would prefer to go ahead with Visual studio testing for MAP and schema but note it will add WBS time as well.

    You can also try manual testing as well to check your application flow.

    Thanks

    Abhishek




    Thursday, December 25, 2014 2:25 PM

All replies

  • Hi,

    Migration from BT2009 to BT2013 is quite a hot topic these days on the forum. :) Seen lot of queries regarding this.

    #1 Regarding what approach to take for the migration, I think it is will explained in the installation guide provided by Microsoft @ Upgrade from BizTalk Server 2009 to BizTalk Server 2013. For me its the one stop shop for the information related to migration.

    Visual Studio projects developed for BizTalk Server 2009 can be migrated to the BizTalk Server 2013 R2 environment by using the Visual Studio Conversion Wizard, you cannot use BizTalk 2009 MSI's directly.

     

    #2 Regarding the estimation, there is no set formula or automated tool to calculate the time. It depends majorly on the infrastructure, applications etc. It takes experience, judgement and know-how to be able to estimate how many man-hours (effort) will be required for a given set of BizTalk tasks.

    You need to keep in mind about the following things while estimating the efforts.

    1) Database Migration.

    BizTalk application may rely on databases for configurations and data archiving. Such databases need to be migrated to the new infrastructure. 

    2) BizTalk Application Migration.

    As discussed, Visual Studio 2012 Conversion Wizard can be used to convert the Visual Studio 2005 projects into Visual Studio 2012 project.

    3) Trading Partner Configuration Migration

    Before you start upgrading to BizTalk Server 2013, you must run the Microsoft BizTalk Server Party Migration Tool (Party Migration Tool) to migrate the party-specific data from BizTalk Server 2006 R2 or BizTalk Server 2009 to the new TPM model in BizTalk Server 2013.

    If you have parties with Electronic Data Interchange (EDI) data, you will have to migrate the party data from old Trading Partner Management (TPM) model to new TPM model.

    4) Certificates Migration

    5) BRE Policies and Vocabularies Migration

    Migration of BRE Policies and Vocabularies from BizTalk 2009 to BiTalk 2013 via BRE Policies and Vocabularies Export/Import may work but is not supported by Microsoft. The business rules may have to be build from scratch on the BizTalk 2013 environment.

    6) BAM Activities Migration

    BAM activities will be migrated by re-deploying the BAM Activities definition files using the bm.exe utility.

    Refer this article for the details about each component migration in detail: BIZTALK 2006 R2/2009 TO BIZTALK 2013 MIGRATION APPROACH

     #3 Regarding the testing strategies you can refer this article Testing Strategy.

    Rachit 

    Thursday, December 25, 2014 8:36 AM
    Moderator
  • Is your Biz Talk Environment design  is part of your scope ?  or is it only the code Migration activity which you will be considering .

    If you are working with code Migration only then list of task which you need to perform are as follows

    1) Migrate Existing .net class library to 4.0 .Net framework . 

    2) Migrate BizTalk Projects through Visual studio Migration Wizard ( one Migration is completed you need to change project properties to point to 4.0 framework)

    approach can be sub divided into two :

    • Backup Visual Studio projects.
    •     Convert projects in Visual Studio through Visual Studio Conversion Wizard (For troubleshooting see)
    •     Compile the solutions against .NET Framework.
    •     Build and deploy.

      Or
          Backup Visual Studio projects.
    •     Recreate projects in Visual Studio 2013.
    •     Copy old artifacts from the old projects into the new project.
    •     Compile the solutions against .NET Framework.
    •     Build and deploy.

    3) If you are using BAM then you need to deploy all the activities which are part of earlier version 

    4) Similarly you need to Migrate Rule engine if it is being used .

    5)There are certain consideration which you need to take care of if you are using IBM MQ  as well . With BizTalk Migration you need to migrate some of the source and destination system as well which are not being supported with BizTalk 2013

    6) There are also mapping change in BizTalk 2013 . So you need to test Each map separately to see its working fine or not . It will add to your Work breakdown task.  There are certain restrictionin mapping in bizTalk 2013 which is being listed below .

    • Only public methods may be called from XPath expressions.
    • Overloads are distinguishable from each other based on the number of arguments. If more than one overload has the same number of arguments, an exception will be raised.

    You need to see below blog to understand the change in biztalk 2013

    What the BizTalk Server 2013 Mapper Updates Mean for You

    Andrei Kosmynin has written a good post here BizTalk 009 to BizTalk 2013 Migration  which tells you benefits and the scope of Migration which you need to understand before developing final WBS

    • BAM Activities Migration
    • BRE Policies and Vocabularies Migration
    • Exporting BRE Policies and Vocabularies from BizTalk Server 2009
    • Importing BRE Policies and Vocabularies into BizTalk Server 2013

      Certificate Export/Import
    • Windows Server 2003 to Windows Server 2012
    • Choosing an Export Format
    • Exporting a Server Certificate from Windows Server 2003
    • Importing a Server Certificate to Windows Server 2012

    There are some good post written by Steef jan  and over MSDN which you follow

    BizTalk Application Migration Guide by Steef Jan

    Troubleshooting BizTalk Server Migration in BizTalk 2013

    At last i can say WBS  depends on the team, whether they're confortable with Biztalk or not (and have they done integration projects - really different from doing a web site)..

    I would suggest to take reference from an old post over MSDN

    BizTalk project estimation for man-hours or person-days

    Now coming to your last point about  testing strategy Michael Stephenson has described various approach for this in his blog post  . 

    Michael Stephenson Mapping strategy

    Test Effort Estimation: Learning from an experience

    I would prefer to go ahead with Visual studio testing for MAP and schema but note it will add WBS time as well.

    You can also try manual testing as well to check your application flow.

    Thanks

    Abhishek




    Thursday, December 25, 2014 2:25 PM