Microsoft BizTalk Server 2004: Creating a Schema Map

Tasks

Detailed steps

1. Set up lab.

1. Click inside the virtual machine window.

2. Press Right-ALT + DEL.

3. Type a password of pass@word1 and press Enter.

4. Click Start | Windows Explorer and navigate to C:\Labs\Setup Scripts\SetupLab3.A.bat.

5. Double-click the file to run it and close Windows Explorer.

This script will erase the existing projects and artifacts in the C:\Labs\Work folder and copy all required artifacts and files for this lab into the C:\Labs\Work folder.

2. Open an existing solution.
   
   This opens a project with predefined schemas (.xsd).

1. Click Start | All Programs | Microsoft Visual Studio .NET 2003 | Microsoft Visual Studio .NET 2003.

2. On the File menu, click Open Solution.

3. In the Open Solution dialog box, navigate to C:\Labs\Work\NWBusinessSolution, select NWBusinessSolution.sln, and then click Open.

A project opens in Solution Explorer.

3. Add the destination schema to the project.
   
   This loads the schema for the purchase order format used by Fabrikam, Inc.

1. In Solution Explorer, right-click the NWMessaging project, and then click Add Reference.

2. In the Add Reference dialog box, click Browse, navigate to C:\Labs\SupportingArtifacts\FKMessaging
   \bin\Development, select FKMessaging.dll, and then click Open.

3. Click OK.

The FKMessaging reference is added to Solution Explorer.

4. Create the BizTalk map.
   
   Selecting the Map template causes BizTalk Mapper to start.

1. In Solution Explorer, right-click the NWMessaging project, point to Add, and then select Add New Item.

2. In the Add New Item dialog box, in the Templates pane, click Map.

3. In the Name box, type NWCustomerOrder_To_FKSupplierPO.btm to name the map.

4. Click Open to start BizTalk Mapper.

BizTalk Mapper opens, and the new map is added to Solution Explorer.

5. Open the source and destination schemas.
   
   This prepares the Mapper’s UI to translate the source schema to the destination schema.

1. In BizTalk Mapper, open the following schemas:

6. Rename the map page.
   
   Renaming the map page makes map management easier. It does not affect the XSLT in any way.

1. Below the Map Zone, right-click the Page 1 tab (at the bottom of the map), and click Rename Page.

2. Rename the page Data Maps and press Enter.

7. Create a link between fields.
   
   Linking nodes in the Mapper creates XSLT that will transform the data in the source document into the structure of the destination document.

1. Using the pairings in the table below, in the Source Schema pane, click each source field and then drag it across the Mapper grid to the associated destination field in the Destination Schema pane.

The lines in BizTalk Mapper show how the fields between schemas have been mapped, as shown here:

Tasks

Detailed steps

1. Add a cumulative functoid to the map.
   
   This functoid calculates the total quantity of all line items in the customer order before updating the total quantity in the purchase order.

1. In the Toolbox, click the Cumulative Functoids palette, click the Cumulative Sum functoid, and then drag it to the Mapper grid.

2. In the Source Schema pane, click the Quantity field, and then drag a link to the Cumulative Sum functoid in the Mapper grid.

3. In the Mapper grid, click the Cumulative Sum functoid, and then drag a link to the TotalQty in the Destination Schema pane.

2. Add a multiplication functoid to the map.
   
   This functoid calculates the total cost of a line item.

1. In the Toolbox, click the Mathematical Functoids palette, click the Multiplication functoid, and then drag it to the Mapper grid.

2. In the Source Schema pane, click the UnitPrice field, and then drag a link to the Multiplication functoid in the Mapper grid.

3. In the Source Schema pane, click the Quantity field, and then drag a link to the Multiplication functoid in the Mapper grid.

3. Add another cumulative functoid to the map.
   
   This functoid calculates the total cost of all line items in the customer order before updating the total cost in the purchase order.

1. In the Toolbox, click the Cumulative Functoids palette, click the Cumulative Sum functoid, and then drag it to the Mapper grid.

Make sure to place this functoid to the right of the multiplication functoid. Functoids must always link from left to right.

2. In the Mapper grid, drag a link from the Multiplication functoid to the Cumulative Sum functoid in the Mapper grid.

3. In the Mapper grid, drag a link from the Cumulative Sum functoid to the TotalCost field in the Destination Schema pane.

4. Add a scripting functoid to a map.
   
   This step changes the value in the Priority field from an integer to a string. This function could be written in C#, Jscript.NET, XSLT, or an external assembly.

1. In the Toolbox, click the Advanced Functoids palette, select the Scripting functoid, and then drag it to the Mapper grid.

2. In the Source Schema pane, click the Priority field, and then drag a link to the Scripting functoid in the Mapper grid.

3. Click the Scripting functoid, and then drag a link to the Priority field in the Destination Schema pane.

4. Select the Scripting functoid, and press F4 (this brings up the Functoid Properties window).

5. Select the Script property, and then click the ellipsis (…) button.

6. In the Configure Functoid Script dialog box, in the Script type drop-down list, select Inline Visual Basic .NET, and then type the following code in the Inline script buffer text box:

   Public Function PriorityConversion(ByVal param1 As String) As String
   Select param1
      Case “1”
         Return “High”
      Case “2”
         Return “Medium”
      Case “3”
         Return “Low”
      Case Else
         Return “Error”
      End Select
   End Function

7. Click OK to save the script and close the Functoid Properties window.

The completed map should look similar to this:

5. Create a new map page.
   
   It is not required to create a new page but it will aid in readability.

1. Below the Map Zone, right-click the Data Maps tab, click Add Page to create a new page (or map zone), and then rename the page as Control.

6. Add a Looping functoid to the map.
   
   This functoid loops through all occurrences of line items in the customer order and creates multiple line items in the purchase order.
   
   If no Looping functoid is present, the Mapper will try to determine how many of the destination nodes to create for each occurrence of the source node. Even if the Mapper chooses the looping that you desire, it is best for documentation purposes to explicitly use the Looping functoid.

1. In the Toolbox, click the Advanced Functoids palette, and then drag the Looping functoid to the Mapper grid on the Control page.

2. In the Source Schema pane, click the SalesOrderLine record, and then drag it to Looping functoid in the Mapper grid.

3. In the Mapper grid, drag a link from the Looping functoid to the Item record in the Destination Schema pane.

The completed map should look like this:

4. On the File menu, click Save All.

Tasks

Detailed steps

1. Validate the map.
   
   This makes sure that the map could produce a valid destination document.
   
   An example of an invalid map would be one in which a required field in the destination document is not filled.

1. In Solution Explorer, right-click NWCustomerOrder_To_FKSupplierPO.btm, and then select Validate Map.

The results of the map validation are displayed in the Output window.

2. Test the map.
   
   Testing a map provides a way to catch exceptions or logical errors by using an actual instance document, without deploying an entire solution.

1. Right-click NWCustomerOrder_To_FKSupplierPO.btm, click Properties, and then configure the following properties:
   
   

   Property	Value
   TestMap Input Instance	C:\Labs\Work\CustomerOrder.xml
   TestMap Input	XML

2. Click OK to save the map.

3. Right-click NWCustomerOrder_To_FKSupplierPO.btm, and then select Test Map.

A link to the XML instance is shown in the Output window. Click the link while pressing Ctrl to open the resulting XML file.

Tasks

Detailed steps

1. Build the project. The assembly is compiled into a DLL file and saved in the …\bin\Development folder within the project folder.

1. On the File menu, click Save All.

2. In Solution Explorer, right-click NWMessaging, and then select Build.

The results of the compiled project are displayed in the Output window.

3. Close Visual Studio.