An Introduction to BizTalk 2006 R2 Development, Page 2
Building a Project
BizTalk ships with all sorts of samples. The CBRSample is perfect for exercising BizTalk's Messaging Engine. You can find the sample in the BizTalk SDK folder shown in Figure 2.
Figure 2: CBR Sample Folder
BizTalk works with Visual Studio 2005. The loaded sample appears in Figure 3.
Figure 3: The CBR Sample
As you can see, the sample uses XML schemas. If you are unfamiliar with XML and XML Schemas (XSD), you'll find XML resources at the end of the article.
The sample contains the following components:
- Three Schemas, an input Schema (CBRInputSchema.xsd), and two output Schema's (CBROutputSchema.xsd, CBROutputSchemaCAN.xsd).
- Two maps map the input schema to each of the output schemas. A complete explanation of maps is beyond the scope of this article. To read more about maps, check out Creating Maps Using BizTalk Mapper on MSDN.
- A promoted properties Schema BizTalk uses to extract information from an XML file and place in the BizTalk Context.
- Sample XML files for testing the application.
See the BizTalk 2006 R2 documentation for a complete explanation of the sample code.
A Setup.bat file in the sample directory will automatically compile and deploy the entire solution. I'm going to walk through manually deploying the project.
To run the sample, you first need to compile the project. BizTalk assemblies are loaded in the GAC, so they must be signed. To deploy the project, execute the Deploy command on the project menu (see Figure 4).
Figure 4: Deploying a BizTalk Project
BizTalk applications are really groupings of related components. Deployment properties dictate where a project is deployed (see Figure 5).
Figure 5: Deployment Properties