Planning for Migration
When planning your migration of a BizTalk Server 2002 solution to BizTalk Server 2004 solution, you must assess the technical architecture requirements, and plan the migration from a feature perspective. This section provides a detailed outlook of the planning considerations and recommendations from both perspectives.
The answers to the following questions help you plan your migration from BizTalk Server 2002 in your BizTalk Server 2004 environment.
|What is a promoted property?||Property promotion enables you to flag schema nodes at design time for promotion to the MessageBox at run time. In addition to any custom metadata you explicitly define by promoting properties, BizTalk Server 2004 has several pre-existing properties that it tracks by default. These pre-existing properties are not defined by instance schemas. For more information about promoting properties, see Promoting Properties.|
|What is a binding file?||Binding files are shortcuts so that you can bind once using the BizTalk Explorer, export that binding, and then import it when you need to assign the binding subsequent times. For example, if you install and deploy your development environment and save a binding file, when it is time to go into production, you can script the Deployment Wizard and specify the binding file to use to create the bindings for the ports. For messaging migration, the Migration Wizard only generates one binding file for the send or receive locations in a solution. For more information about binding files, see Importing Assembly Bindings Using the BizTalk Deployment Wizard and Exporting Assembly Bindings Using the BizTalk Deployment Wizard.|
|Can I have multiple schemas with the same root node?||No. The messaging engine relies on the root node to resolve an XML instance to a schema at run time. (This is possible in BizTalk Server 2002.) For more information about schemas, see About Schemas.|
|Can I add an orchestration within my migration project?||Yes, it is possible, but not recommended because you have to manually create a send/receive port to/from an orchestration, thereby complicating the migration of your messaging solution. For more information about adding orchestrations, see Creating and Modifying Orchestrations.|
|Is it possible to create an orchestration that receives a non-XML message (a binary large object (BLOB) for instance) through a pipeline with a custom disassembler and promote properties in the blob?||You can pass type-less messages through orchestrations by declaring them as an XmlDocument. If you want to retrieve their data, you need to pass them to a .NET object as XLANGPart/XLANGMessage and call part.RetrieveAs(typeof(Stream) ); by using part.LoadFrom( myStream ), you can also construct non-XML messages in an orchestration. For more information about adding orchestrations, see Creating and Modifying Orchestrations.|
|How do I create a dynamic send port?||You can create a dynamic send port either using BizTalk Explorer or within an orchestration:
BizTalk Explorer - Create the port using BizTalk Explorer, and then assign values to the transport properties in BizTalk Editor using the global property schema. You can then select the appropriate schema from references. By default, BizTalk Server 2004 references Microsoft.BizTalk.GlobalPropertySchema. Values to the transport properties come from your document. You need to promote elements from your schema using the global property schema.
Orchestration - You can create dynamic ports in an orchestration, and, after you deploy it, the port is accessible from BizTalk Explorer. In the orchestration, you need to assign the address (transport) using an Expression shape.
For more information about dynamic send ports in BizTalk Explorer, see Adding a Dynamic Send Port Using BizTalk Explorer.
|Will the Migration Wizard migrate custom script functoids?||No. Any maps that are migrated that contain custom script functoids need to be opened and functoids re-coded. For more information about dynamic send ports in BizTalk Explorer, see Migrating Functoids.|
|Will the Migration Wizard migrate my queue receive functions?||Yes. BizTalk Server supports all type of receive functions including BizTalk Server message queuing (MSMQ) file receive. BizTalk Server supports the conventional HTTP receive function, but not the HTTP file receive function because it has no meaningful use in the product. For more information about receive functions, see Configuring Receive Location Properties in the BizTalk Administration Console.|
|Will the Migration Wizard migrate my pre-processor?||No. You must update your project by manually migrating any components such as pre-processors not migrated by the Migration Wizard. For more information about component migration, see Updating a Message Migration Project.|
|Will the Migration Wizard migrate my channel routing and filter configurations?||No, with one exception. BizTalk Server 2004 automatically migrates routing and filtering configurations for channels that use dynamic routing or filtering. Custom routing done in a channel requires that you promote the properties and create the filters. For more information about migrating channels, see About the Migration Wizard.|
|Will the Migration Wizard migrate orchestrations?||No. The Migration Wizard only migrates the following items. For more information about the Migration Wizard, see About the Migration Wizard.|
|BizTalk Server 2002 Messaging Item||BizTalk Server 2004 Migration Path|
|receive functions||receive locations|
|ports and channels||ports and pipelines|
|port groups (distribution lists)||send port groups|
This section contains:http://go.microsoft.com/fwlink/?linkid=20616.Copyright © 2004 Microsoft Corporation.
All rights reserved.