Migration from 2010 to 2013R2 RRS feed

  • Question

  • Could you pls Share the documentation for migration of 2010 to 2013R2.



    • Edited by CHINNACND Saturday, August 13, 2016 7:11 AM
    Thursday, August 11, 2016 7:15 AM


All replies

  • Hi

    We are going to take a Biztalk project and i am the person to handle the project and taking KT from customer.Help me how to plan and What type of Questions shall i ask

    Mandar Dharmadhikari

    What question you first need to ask the client is what is the business requirement and what are the plans to leverage the features of BizTalk in this path?? That is the ice breaker generally, then you can point out some niceties of the BizTalk server 2013 R2 and how you can implement them, for example:

    1)How it is good to move from MOM to BAM what kind of BAM tracking they want.

    2)You can ask about the kind of architecture they plan to build..meaning how many BizTalk app servers how many SQL boxes etc. Also suggest them trying out the architecture using a load testing tool like Bizalk bench mark Wizard which will let them know if the infrastructure will be able to handle the intended load.

    3) How many environment they plan to have viz.. UAT, Preprod, Prod etc

    4) What exactly client means by using out of the Box BizTalk Tracking?? If they imply of using BAM it is fine. If they plan on using message tracking through individual artifacts in application, you can suggest how enabling tracking on the BizTalk artifact causes performance issues.

    5) You can ask about the processes those will be followed for deployment, Unit Testing, Support and Operations etc and suggest use of tools like BTDF and BizUnit, BHM, MBV and if the client agrees for it BizTalk 360..

    Also go through some of the below pasted links they talk about the BizTalk Migration

    Please go through these and you will be able to come  up with more scenarios than I can point out.

    Well these are couple of pointers that I can think of...well you need to grasp the mood of meeting and pose your questions accordingly. :)


    Thursday, August 11, 2016 7:17 AM
  • Hi 

    That's a pretty big list. I would first request you to get as much information on the current project as possible so that we can offer more precise advice.

    1. If you are installing/configuring BizTalk 2013 R2 on new servers/VM, you can simply open the BizTalk 2010 projects in Visual Studio 2013 and build them in Visual Studio 2013. You will get the binaries that you can then deploy in your BizTalk 2013 R2 environment. The key here is testing all of the applications after you build the projects in VS 2013 and deploy them in BizTalk 2013 R2 test/dev environement . Build a test plan/strategy during your KT sessions.

    You can refer this thread for few other things to take note of - like migrating SQL Server, planning for downtime, etc.

    2. Is the goal here to monitor the environment? Currently MOM/SCOM is being used for monitoring the environment? And the plan is to use BAM? Your point 8 suggests that SCOM will again be used? Get more clarity on this, if SCOM is deployed then, avoid using BAM.

    3. You can refer below articles for testing. You can use something like BizUnit to help you.

    4. What is the current strategy for message tracking?

    5. You have to configure the "DTA Purge and Archive" Job for this -

    Also ensure that the other BizTalk SQL Agent Jobs are configured/running fine-

    6. More clarity needed - maybe one thing you can ask during your KT

    7. Is this to be developed from scratch or modified. Again more clarity needed.

    8. Related to point 2 above? If SCOM is in use currently and the same needs to be re-used, it should be fairly simple-

    Thanks Arindam

    • Edited by Arindam Paul RoyEditor Thursday, August 11, 2016 8:50 AM
    • Proposed as answer by - Anand - Thursday, August 11, 2016 2:10 PM
    • Marked as answer by Angie Xu Thursday, August 18, 2016 8:17 AM
    Thursday, August 11, 2016 7:52 AM
  • hi,

    Migration is a lengthy process but to kickoff the project you may start with below mentioned few points:

    1) Know the business requirement: By knowing the business requirement you can decide the capacity of Biztalk  environment , for an example how many servers required , clustering is needed or not etc.

    2) Hardware configuration detail and validation: Prepare the hardware configuration detail which will suits the  business need and also important to perform hardware validation 

    2) Discuss about the Migration approach like Big bang or Gradually one by one each application or customer

    3) List down the softwares which are required to be installed on new platform.

    4) Firewall and connectivity : List down the ports need to be opened for biztalk and SQL connectivity . For that better create a sheet and share the same with your network team.

    5) Plan your application migration , SQL migration and certificate migraiton

    6) Proper testing of migrated application : It is very very imported to do the proper regression testing to avoid any surprises.

    7) Setup monitoring system :  Configure your monitoring system to start monitoring your new platform

    8) Document update : You also need to update all documents like support doc, design document , networking doc etc based on the new platform.

    9) Go live support 

    I hope these few basic points which will help you to plan your migration project.


    Thursday, August 11, 2016 9:45 AM
  • Some of inputs in Italics:

    Existing BizTalk Server 2010 upgrade to the current version BizTalk 2013 R2: this alone is simple and involves recompiling your code in VS 2012 or VS 2013 and deploying in BizTalk 2013 R2.

    4.Rework the message tracking strategy to use Out Of the Box BizTalk message tracking as much as possible- Use itinerary, eliminate orchestrations as and when possible, more stress on messaging based solution. Itinerary provides you an option of accomplishing transformation(with multiple maps) and routing without over loading the msgBox .

    6.Eliminate the need to maintain custom template files for XML to XML interactions, thus simplifying adding new proc codes . - Entity framework, you can define domain level schema and any change to service contract shall be driven from there.

    8.SCOM BizTalk management pack will be re-deployed. - This is purely monitoring, you have an alternate option of usinf few other tools as well, for example, Splunk, BizTalk 360 or your custom exception logging service.

    5.Data purging - Automation related to purging of T -2 data and BizTalk logs. - Believe using a non Biztalk/.net component would be easier to purge the data.

    Regards Pushpendra K Singh

    Thursday, August 11, 2016 2:06 PM
  • So, this is way too much to cover in a single thread.

    What do you mean "What type of Questions shall i ask"?  Are you new to BizTalk?

    Please open each issue as a new Thread after you've done some research.  We can't really give you any advice since there isn't much detail.

    Thursday, August 11, 2016 4:47 PM