Ce contenu n’est pas disponible dans votre langue. Voici la version anglaise.

Migrating EDI Artifacts to BizTalk Server 2006 R2

The EDI Migration Manager is a set of tools that enable you to migrate EDI messaging items from the EDI/HIPAA adapter model in BizTalk Server 2006 to BizTalk Server 2006 R2.

EDI messaging items you can migrate with EDI Migration Manager include XSD schemas, receive ports/adapters, and send ports/adapters.

Artifact migration from versions earlier than BizTalk Server 2006 is not supported. To migrate items from earlier BizTalk Server versions, first migrate them into BizTalk 2006, then use the EDI Migration Manager to migrate them to BizTalk Server 2006 R2.

The command-line tools and wizard that comprise the EDI Migration Manager are described in the following table. These files can be found in the following folder: %BizTalkInstallPath%\SDK\Utilities\MicrosoftEDI.

Tool Purpose


Migrates specified EDI/HIPAA schemas.


Migrates EDI/HIPAA send and receive ports.


Migrates EDI/HIPAA schemas and send/receive ports.

The command-line tools are provided so that you can migrate schemas and ports programmatically or with scripts.

  • Maps

  • Orchestrations

  • An HTTP or other non-EDI port, even if it uses EDI pipelines

  • EDI Adapter properties (that is, none of the Adapter Properties, Connection Properties, or Connector Properties found in the EDI Transport Properties dialog box)

  • The following EDI Subsytem parameters:

    • Numbers

    • Time-out

    • Tuning

    • Trace

    • Audit Trail

    • Client/Server

  • FTP firewall settings (these are optional in the BizTalk FTP Adapter and not available in the BizTalk 2004 Covast EDI FTP Connector).

EDI Annotations

The following BizTalk Server 2006 EDI annotations are not used by BizTalk Server 2006 R2, therefore they are not modified or altered by the Migration Manager:

  • Standards version

  • Count Ignore

  • EDI Datatype

    Any element using the EDI Datatype annotation is migrated to use the corresponding BizTalk Server 2006 R2 data type. The old annotation is included.

  • Justification

  • Format

  • Custom maxLength

Migration of each individual artifact (that is, each schema, send port, or receive port) is transactional. If any migration step fails for an artifact, changes are rolled back for that artifact and it is not migrated. Migration Manager continues to migrate any remaining artifacts.

If you cancel the migration process, Migration Manager finishes migrating the current artifact then stops. You can start the migration process again to migrate any remaining artifacts.

Running the migration process on migrated artifacts will not affect them. You cannot rollback migrated artifacts.

Ajouts de la communauté