The primary user interface for BizTalk® Mapper is displayed on a tab within the Microsoft® Visual Studio® .NET editing window. This display is divided into three panes. The left pane displays the source schema as a tree on the left side. The right pane displays the destination schema as a tree. The middle pane displays the grid as multiple pages. To indicate how you want to map data from the source schema to the destination schema, you draw lines between the records and fields you want to map. These lines are called "links", and they are the most basic way to specify the mapping of data. For more information about linking records and fields, see Links in Maps.
If you want to implement more advanced mapping methods, you can use functoids, tools available in BizTalk Mapper tabs within the Visual Studio .NET Toolbox. Functoids enable you to create more complex maps. Examples of more complex map elements include:
- Adding the values in two fields in a source schema and putting the result in a field in the destination schema.
- Calculating the average value of a field in a looping record and putting the result in a field in the destination schema.
- Writing a custom script to manipulate instance data as appropriate for your business needs.
For more information about functoids, see Functoids in Maps.
BizTalk Mapper can support many different mapping scenarios from simple parent-child relationships to detailed, complex looping of records and hierarchies. All data processed by Microsoft® BizTalk® Server 2004 at run time must be in XML. All non-XML data must be translated to an equivalent XML format before mapping. Similarly, when the mapping process is complete, BizTalk Server 2004 uses the output of a mapping operation to create a file format that is recognized by the trading partner or application to which the data is sent.
BizTalk Mapper includes a compiler. This tool-level component generates the Extensible Stylesheet Language Transformations (XSLT) needed to transform or translate input instance messages to output instance messages.
This section provides task-specific information about using BizTalk Mapper to create the mapping between two schemas. It assumes that you already have BizTalk Mapper open, and have chosen your source and destination schemas.
This section contains:
- Managing Maps Within Projects
- Using Links to Specify Record and Field Mappings
- Using Functoids to Create More Complex Mappings
- Mapping without Maps
All rights reserved.