locked
Proper procedure for migrating EDI bindings from BizTalk 2006 to BizTalk 2013 R2 from an XML file RRS feed

  • Question

  • Hi all,

    I would appreciate if anyone can share their experience or a guide to follow any standard procedure for migrating EDI party bindings in .XML file from BizTalk 2006 to BizTalk 2013 R2. Also, how to identify partner profiles if migrating from more than two different regions into one clustered environment.

    With regards,

    Bond NY

    Thursday, February 25, 2016 6:31 PM

Answers

  • Ohh....hold on, you're coming from 2006, not 2006 R2?

    Then, sorry, there's no way to migrate that.  EDI partners in 2006 was based on a completely different stack, replaced with the current (except TMP) EDI stack in 2006 R2.

    This was a big deal way back.  Everyone just ended up doing it manually.

    • Marked as answer by BondNY Thursday, February 25, 2016 8:27 PM
    Thursday, February 25, 2016 8:01 PM
    Moderator
  • If that's the case, as I have mentioned above in this article it says we can by doing an intermediate step https://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

    I tried opening in VS2008 and it opened, but didn't know or find a way to migrate that to recent version. Any help here will be appreciated. 

    That thread talks about migrating BizTalk application.

    "If you are talking about BizTalk Server 2006 (And NOT R2), then you need an intermediate step when converting your source code in Visual Studio.

    BizTalk Server 2006:

    Open your projects in Visual Studio 2008 first, and migrate them. Then open them in Visual Studio 2012 and migrate."


    As stated above you have to set up new Party/Agreement setup manually. There is no other alternative. 



    Rachit Sikroria (Microsoft Azure MVP)


    Thursday, February 25, 2016 8:17 PM
    Moderator

All replies

  • Refer the guide: Considerations for Upgrading to BizTalk Server 2013

    Before you upgrade to BizTalk Server 2013 R2 you have to run the Microsoft BizTalk Server Party Migration Tool (Party Migration Tool) and migrate the party data from the old Trading Partner Management (TPM) model to the new TPM model.

    Trading Partner Management (TPM) has been re-engineered in BizTalk 2010.


    Rachit Sikroria (Microsoft Azure MVP)

    Thursday, February 25, 2016 7:10 PM
    Moderator
  • Hi Rachit,

    As per this link https://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral , I'm sure there is an intermediate step involved to migrate.

    But, in my case I only have .XML file of the bindings. What is the approach for this scenario?


    Thursday, February 25, 2016 7:27 PM
  • As noted above, TPM is completely different in BizTalk Server 2010 compared to previous versions.  You must use the Party Migration Tool to update TPM data.

    The tool itself is written mostly assuming a 1-1 upgrade, there is no provision to merge multiple TPM databases.

    However, so long as the Identifier Pairs are unique, there is nothing stopping you from importing both bindings into the same BizTalk Group.  That then becomes your 'master' TPM system.

    Of course, you should do all of this on a non-PROD system and you may have to do it more than once to get it right.  That's perfectly fine.

    Thursday, February 25, 2016 7:31 PM
    Moderator
  • Hi John,

    Thank you for your reply,

    In our case, we do not have access to Old BT2006 servers. All we have is the XML file with party bindings. Is there a way to migrate without using the above mentioned steps? 

    With regards,

    Bond NY.

    Thursday, February 25, 2016 7:40 PM
  • Ohh....hold on, you're coming from 2006, not 2006 R2?

    Then, sorry, there's no way to migrate that.  EDI partners in 2006 was based on a completely different stack, replaced with the current (except TMP) EDI stack in 2006 R2.

    This was a big deal way back.  Everyone just ended up doing it manually.

    • Marked as answer by BondNY Thursday, February 25, 2016 8:27 PM
    Thursday, February 25, 2016 8:01 PM
    Moderator
  • If that's the case, as I have mentioned above in this article it says we can by doing an intermediate step https://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

    I tried opening in VS2008 and it opened, but didn't know or find a way to migrate that to recent version. Any help here will be appreciated. 

    Thursday, February 25, 2016 8:10 PM
  • If that's the case, as I have mentioned above in this article it says we can by doing an intermediate step https://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral

    I tried opening in VS2008 and it opened, but didn't know or find a way to migrate that to recent version. Any help here will be appreciated. 

    That thread talks about migrating BizTalk application.

    "If you are talking about BizTalk Server 2006 (And NOT R2), then you need an intermediate step when converting your source code in Visual Studio.

    BizTalk Server 2006:

    Open your projects in Visual Studio 2008 first, and migrate them. Then open them in Visual Studio 2012 and migrate."


    As stated above you have to set up new Party/Agreement setup manually. There is no other alternative. 



    Rachit Sikroria (Microsoft Azure MVP)


    Thursday, February 25, 2016 8:17 PM
    Moderator
  • Thank you for the reply...
    Thursday, February 25, 2016 8:27 PM
  • Did you get the idea on how to setup manually? If yes, can you share any document.. I am having the same issue and dont know how to do it manually.

    Thanks

    Thursday, February 25, 2016 8:39 PM