Considerations Before Using the Party Migration Tool
You must consider the following points before you use the Party Migration Tool.
-
You must run the Party Migration Tool from the CD. You should not copy the tool executable to a separate location and then run.
-
You must run the Party Migration Tool from the same computer where you inserted the CD or copied the CD locally. You should not run the tool over the network share of the CD drive.
-
You must run the Party Migration Tool on a computer that has BizTalk Server Administration console installed.
-
You must run this tool only against BizTalk Server 2006 R2 and BizTalk Server 2009 management database. The tool does not support migrating EDI application data from other BizTalk Server versions.
-
If the source database (BizTalkMgmtDb) and the target database (where the tool copies the migrated party data) are on separate computers from the one where you are running the tool, make sure the computers running the databases and the computer where you run the Party Migration Tool have MSDTC configured. For instructions on how to configure MSDTC see How to Enable MSDTC on the BizTalk Server (http://go.microsoft.com/fwlink/?LinkId=190346).
-
Make sure SQL Server is running on the computers hosting the BizTalkMgmtDb and the target database where the migration data will be copied to.
-
Make sure the target database is running on SQL Server 2008 SP1 or higher. Also, the compatibility level of the SQL Server database must be 100. For more information about the compatibility level, see How to: View or Change the Compatibility Level of a Database (http://go.microsoft.com/fwlink/?LinkId=194986).
-
Make sure you run only a single instance of the Party Migration Tool to migrate party data for a BizTalk Server installation. Running multiple instances of the Party Migration Tool (on a single or multiple machines) for migrating party data for a specific BizTalk Server installation is not supported.
-
Make sure that the party definitions in BizTalk Server 2006 R2 or BizTalk Server 2009 are not configured in such a way that two EDI-specific parties have the same send port associated with them.
-
Make sure that no two parties have the same AS2From and AS2To properties set.
-
BizTalk Server 2006 R2 did not require BAM to be configured as part of AS2 configuration. However, for BizTalk Server 2010, you must have BAM configured before configuring AS2. So, while migrating from BizTalk Server 2006 R2 environment (that has AS2 configured) to BizTalk Server 2010, the tool first checks if BAM is configured. If not, the tool prompts you to configure BAM in BizTalk Server 2006 R2 and then run the tool.
Show: