How Does the Party Migration Tool Work

The Party Migration Tool is run against a BizTalk Server 2006 R2 or BizTalk Server 2009 management database (BizTalkMgmtDb), which contains all the information about parties and the corresponding settings in the specific BizTalk Server version. The tool presents a hierarchical structure of the party definitions as it exists in BizTalk Server 2006 R2 or BizTalk Server 2009 (pre-migration) and a suggestive hierarchical structure of how the new entities (partner, identities, agreements) will be created in BizTalk Server 2010 (post-migration). The tool also enables you to make changes to the suggested hierarchical structure by renaming the partners, moving identities between partners, deleting send port association, etc. Because your BizTalk Server setup may contain a large number of parties, updating all the parties, and related data, can take considerable time and would probably have to be done in batches. To facilitate that, you can use the Save option in the tool to save the changes that you have made. You can then use the tool at a later time and make changes to the remaining parties.

After making all the required changes, you can click Finish to store the settings to a target database. When you run the BizTalk Server 2010 upgrade, it reads the settings stored in the target database and creates the parties, profiles, agreements, etc. in BizTalk Server 2010.

If the BizTalk Server 2006 R2 or BizTalk Server 2009 that you are upgrading includes party definitions, and you start the upgrade process without running the Party Migration Tool, you would get an alert informing you to run the tool first.

To understand a typical workflow on how to use the Party Migration Tool, consider the following entities:

  • BizTalkMgmtDb – Name of BizTalk Server 2006 R2 or BizTalk Server 2009 database that contains live EDI/AS2 party data from a BizTalk Server deployment.

  • MigrationDB – Name of a temporary target database that contains all the migration information.

The following sequence of events must take place to migrate EDI/AS2 party data from BizTalk Server 2006 R2 or BizTalk Server 2009 to BizTalk Server 2010.

  1. The user running the Party Migration Tool ensures that a temporary database, e.g. MigrationDB, is created in SQL Server. This database must be created in SQL Server 2008 SP1 or higher.

  2. Before upgrading to BizTalk Server 2010 a BizTalk Server administrator runs the Party Migration tool against the BizTalkMgmtDb, if the BizTalk Server 2006 R2 or BizTalk Server 2009 setup contains any EDI/AS2 party data that must be migrated.

  3. The Party Migration Tool goes through the EDI data in the BizTalkMgmtDb and provides suggested migration of the EDI/AS2 artifacts.

  4. The BizTalk Server administrator uses the Party Migration Tool interface to make changes, if required, to the migration suggested by the Party Migration Tool. If the number of parties to be migrated is quite high, the administrator can save the current changes and rerun the tool later.

  5. After making all the required changes, the BizTalk Server administrator clicks Finish on the Party Migration Tool. The Party Migration Tool creates tables in the temporary database to store information about the EDI/AS2 party migration. The upgrade operation cannot progress if the BizTalk Server administrator exits the Party Migration Tool without clicking Finish.

    The tables can also be copied to a BizTalkMgmtDb tables in a test environment.

  6. After exiting the Party Migration Tool by clicking Finish, the BizTalk Server administrator starts the upgrade process. During the upgrade process, the EDI/AS2 related migration data is copied from the temporary database (MigrationDB) to the BizTalk Server 2010 management database, thereby creating all the required entities to comply with the new TPM model.