At the beginning of this chapter, we talked about what a specification is.We discussed that in order for two or more organizations to do business together, a similar set of systems is needed to be able to transform information to and from each other (for example, EDI to XML). So, what happens when your business partners do not have similar systems? If this were the case (which it most often is), you would need to create specifications based on those differences that can be mapped and put together to make a seamless and transparent transaction of resources.You would need to implement Microsoft BizTalk Server 2000 and, more importantly, learn how to create those specifications and map them with the tools described in this chapter: the BizTalk Editor and the BizTalk Mapper. While learning these tools, we created new specifications and altered predefined templates. We worked at creating our own purchase orders and exporting data into an XDR schema.We also covered the details of records and fields, and how to work with and alter their properties. We then moved on to the BizTalk Mapper, where we learned how to add two specifications together to create a map.We learned how to use the Mapper tool and how to create basic mappings. We did an overview of creating specifications to be mapped and went through the entire process of creating schema data and mapping it together.We looked at mappings that were not simple in nature and required functions or functoids to be added to the script to provide the results needed. We then looked at the XSL stylesheet and how it is all tied together to achieve the end result. We finished the chapter with an explanation ofWebDAV and how to access it. All in all, you should now have a good understanding of how to use the tools in this chapter to create a business solution with Microsoft BizTalk Server 2000 and the .NET platform.
Was this article helpful?