Export (0) Print
Expand All

How to Use the Party Migration Tool

Perform the following tasks to migrate party data from BizTalk Server 2006 R2 to BizTalk Server 2009 to a temporary migration database.

Hh183965.note(en-us,BTS.70).gifNote
As a best practice approach, Microsoft recommends that you create a temporary database and not use an existing database to which the Party Migration Tool will copy the migrated EDI application settings.

To use the Party Migration Tool

  1. Insert the CD into the CD drive on a computer that has BizTalk Server Administration console installed as part of BizTalk Server 2006 R2 or BizTalk Server 2009 installation.

  2. On the CD, open the PartyMigrationTool folder at the CD root, right click PartyMigrationTool.exe, and then click Run as Administrator. This starts the Microsoft BizTalk Server Party Migration Tool.

    Hh183965.note(en-us,BTS.70).gifNote
    You must always run the executable with administrative privileges.

  3. From the File menu, click Initialize.

  4. Select the If sender identities and receiver identities of a party are different, create different parties for them check box if you want to create different parties for the sender and receiver identities for a party.

    For example, for a party with EDI configured, assume that Party as Sender is configured to process messages sent from A to B and the Party as Receiver is configured to process messages sent from B to C. In such a case, if you select the check box, after migration, three parties will be created (say P1, P2, and P3) and the respective identities will be added under each party. However, if the check box is cleared, two parties will be created (say P1 and P2) and A,C will be added as identities under one party and B will be added as identity under the other party.

  5. Select the Create default AS2 agreements for all parties check box if you want the migrated party information to have a default AS2 agreement for all parties. This is required because in previous versions of BizTalk Server, you may have a party processing AS2 messages without setting the AS2-specific properties. However, in the new TPM model in BizTalk Server 2010, you must have an AS2 agreement for a party to process AS2 messages. So, if you select the check box, the migrated party data will have a default AS2 agreement for all parties.

  6. In the BizTalk Management Database box, do the following:

    Use this To do this

    Server name

    Enter the name of the computer that hosts the BizTalk Server management database. If the same computer hosts the database on which you are running the tool, you can enter a dot (.)

    Database name

    Select the BizTalk Server management database (BizTalkMgmtDb).

    Test Connection

    Click this button to test the connection to the database.

  7. In the Database to hold Migrated TPM Data box, do the following:

    Use this To do this

    Server name

    Enter the name of the computer that hosts the database to which the migrated TPM data will be copied. If the same computer hosts the database on which you are running the tool, you can enter a dot (.)

    Database name

    Select the database that you created to hold the migrated TPM data.

    Test Connection

    Click this button to test the connection to the database.

  8. Click Initialize. As soon as you initialize the tool, it reads all the party information from the BizTalk Server 2006 R2 or BizTalk Server 2009 environment and presents it in a hierarchical format.

    Hh183965.note(en-us,BTS.70).gifNote
    If the target database you selected stores TPM migration data for other party migrations, the tool prompts you before overwriting the database.

    The tool also presents how the EDI applications would be defined once you migrate all party data and upgrade to BizTalk Server 2010.

    • The Existing parties section lists all the parties, and their settings, as they exist in BizTalk Server 2006 R2 or BizTalk Server 2009. By default all parties are selected. You can click Unselect All to clear the check boxes against all the parties. You can then select specific parties by clicking the check boxes against them or click Select All to select all the parties again.

    • The Parties created section lists all the partners that will be created for the parties selected in the Existing Parties section.

    • The New agreements created section lists all the agreements that will be created between the partners listed in the Parties Created section.

  9. At this stage, you can either accept the suggested migration hierarchy or make changes to customize the migrated party data as described under Modifying the Suggestive Migrated Data. In either case, once you want to exit the tool, you have the following options.

    Use this To do this

    Save to Migration database

    Click Save to Migration database to save the changes you made to the suggested party migration data. You must use this option if you need to make more changes and you want to the tool to remember the changes that you have already done.

    Save to Binding file

    Click Save to Binding file to save the changes to a binding file. You must use this option if you want to import the migrated data into a BizTalk Server 2010 test environment to understand how the EDI party data from BizTalk Server 2006 R2 or BizTalk Server 2009 would be reflected in a BizTalk Server 2010 setup after upgrade.

    Finish

    Click Finish when you accept the party migration hierarchy as displayed or after you have made all the required changes to the party migration hierarchy. When you click Finish, the tool stores all the migration information in the database and creates a flag indicating that the EDI party migration exercise has been completed. The tool also shows a dialog box containing a link to a log file that contains the migration summary report.

    When BizTalk Server 2010 upgrade is run, it looks for this flag and then proceeds with the upgrade. If you have not clicked Finish in the tool, BizTalk Server 2010 upgrade does not proceed.

    Close

    Click Close to close the tool. If you have made changes to the suggested party migration data, you are prompted to save the data before exiting.

    Hh183965.Important(en-us,BTS.70).gifImportant
    To understand how the parties, identities, etc. are migrated from BizTalk Server 2006 R2 or BizTalk Server 2009 to BizTalk Server 2010, see Understanding How the Data is Migrated.

Show:
© 2014 Microsoft