Tasks | Detailed steps |
Set up lab.
| Click inside the virtual machine window. Press Right-ALT + DEL. Type a password of pass@word1 and press Enter. Click Start | Windows Explorer and navigate to C:\Labs\Setup Scripts\SetupLab3.A.bat. 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. |
Open an existing solution.
This opens a project with predefined schemas (.xsd).
| Click Start | All Programs | Microsoft Visual Studio .NET 2003 | Microsoft Visual Studio .NET 2003. On the File menu, click Open Solution. 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. |
Add the destination schema to the project.
This loads the schema for the purchase order format used by Fabrikam, Inc.
| In Solution Explorer, right-click the NWMessaging project, and then click Add Reference. In the Add Reference dialog box, click Browse, navigate to C:\Labs\SupportingArtifacts\FKMessaging
\bin\Development, select FKMessaging.dll, and then click Open. Click OK.
The FKMessaging reference is added to Solution Explorer. |
Create the BizTalk map.
Selecting the Map template causes BizTalk Mapper to start.
| In Solution Explorer, right-click the NWMessaging project, point to Add, and then select Add New Item. In the Add New Item dialog box, in the Templates pane, click Map. In the Name box, type NWCustomerOrder_To_FKSupplierPO.btm to name the map. Click Open to start BizTalk Mapper.
BizTalk Mapper opens, and the new map is added to Solution Explorer. |
Open the source and destination schemas.
This prepares the Mapper’s UI to translate the source schema to the destination schema.
| In BizTalk Mapper, open the following schemas:
Source schema | Destination schema | Schemas
NWMessaging.CustomerOrder | References
FKMessaging
Schemas
FKMessaging.SupplierPO |
|
Rename the map page.
Renaming the map page makes map management easier. It does not affect the XSLT in any way.
| Below the Map Zone, right-click the Page 1 tab (at the bottom of the map), and click Rename Page. Rename the page Data Maps and press Enter.
|
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.
| 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.
Source Field | Destination Field | CustomerPONumber | PONumber | UnitPrice | Cost (under items) | Quantity (under lines) | Qty | ItemID | ProdID | Status | Status |
The lines in BizTalk Mapper show how the fields between schemas have been mapped, as shown here: 
|
