BizTalk MAP

Maps enable you to translate and to transform messages. Translation is the process of converting a message from one format to another format, such as converting a flat file into an XML file. Transformation is the process of taking information from one message and inserting it in another message. 

BizTalk Mapper uses its own graphical system of icons and links to represent the translation and transformation of input instance messages to output instance messages. Mapper uses the same graphical representation of schemas as BizTalk Editor. BizTalk Mapper stores its maps as Extensible Stylesheet Language Transformations (XSLT) stylesheets.

The BizTalk Mapper resides in the Visual Studio shell. Some of the functionality in the BizTalk Mapper relies on the user interface elements of the Visual Studio shell. For example, you use the File, Edit, and View menus just as you would for other development in Visual Studio.

The BizTalk Mapper becomes active when you add a new map to a BizTalk project, when you open an existing map (a .btm file), or when you reactivate a map by clicking its tab in the main Visual Studio editing window.

The following figure shows various parts of BizTalk Mapper within Visual Studio-

Visual Studio Mapper Utility Ribbon: The BizTalk Server Mapper provides a utility ribbon to surface Mapper-related commands. The ribbon provides source schema information, toggle button for relevance view for source and destination schemas, toggle button to show or hide totally out of scope links, toggle switch to turn auto-scrolling on or off, button to pan the Mapper surface, controls to zoom in or zoom out, and the search text box. The following figure shows the utility ribbon you can see at the top of the grid page.

Source schema tree view: This view shares the main Visual Studio editing window with the destination schema tree view and the grid view. As the name suggests, this view displays the schema that describes the instance messages that are the source of mapping. The links that define the mapping lead from the source schema tree view to the grid view, and, ultimately, to the destination schema tree view.

Destination schema tree view: This view shares the main Visual Studio editing window with the source schema tree view and the grid view. As the name suggests, this view displays the schema that describes the instance messages that are the destination of the mapping. The links that define the mapping lead into the destination schema tree view from the grid view, and ultimately from the source schema tree view.

Grid view: This view shares the main Visual Studio editing window with the source schema tree view and the destination schema tree view, with the source schema tree view to the left and the destination schema tree view to the right. As the name suggests, this view plays a critical role in the definition of maps, containing the links and functoids that control how data in a source instance message is transformed into an instance message that conforms to the destination schema. The grid view can have multiple layers, called grid pages, allowing you to organize complex maps into logical subdivisions of mappings. Grid pages generally use more space than can be displayed at one time, and there are several effective ways to scroll within a grid page.

Visual Studio Toolbox window: You use this view to display the functoids available for use in BizTalk maps, and as the source of the drag-and-drop operations to place functoids in a grid page. The functoids shown in the Toolbox are organized according to their categories.

Visual Studio Properties window: You use this view, and its associated dialog boxes, to examine and set the properties of the links and functoids that you create to define your map. When you select a link or functoid in a grid page in the Grid view, select a schema node in the source or destination schema tree views, or select a map in the Solution Explorerwindow; the corresponding properties of that link, functoid, schema node, or map appear in the Properties window using the standard Visual Studio conventions. For example, the properties are grouped into categories, and can be displayed according to these categories or alphabetically.

Visual Studio Task List and Output windows: You use these views to examine the results of validating, compiling, and testing your BizTalk maps in much the same way that these views are used when compiling source code and building other types of projects. In addition to these views, you can interact with several dialog boxes. You usually open these dialog boxes when you are editing a complex property such as the input parameters to a functoid. You often use the Solution Explorer window in conjunction with BizTalk Mapper. For example, to create a new map, right-click the BizTalk project in the Solution Explorer window, click Add, click Add New Item, and then use the Add New Item dialog box to name and create a new map.

See some more biztalk mapping useful link-

1. Inline Schema uses in MAP
2. MAP - Indent : Specifies additional white space
3. Error: The map contains a reference to a schema node that is not valid

!! Keep visiting BizTalkLive !!

<< Previous                                                                                                                                 Next >>