BizTalk Server: Basics principles of Maps – What are maps and where BizTalk can use them? (Part 2)

BizTalk maps are graphical representations of XSLT (Extensible Stylesheet Language Transformation) documents that allow us to perform, in a simple and visual manner, transformations between XML messages.

We can enumerate the following standards used in the BizTalk Mapper:

• XML (Extensible Markup Language) – designed to transport and store data in messages.
• XML Schema (XSD – XML Schema Definition) – describes the structure of an XML document.
• E XSLT (Extensible Stylesheet Language Transformation) is a style sheet language for XML documents (stands for XSL Transformations), which defines the transformation rules of the messages.

To emphasize that they are all W3C recommendations. W3C (Worldwide Web Consortium) is an international consortium where Member organizations, a full-time staff, and the public work together to develop Web standards.

We can define that there are two types of transformations:

• Syntax Transformations: This type of transformation occurs in the receive or send pipelines and aims to transform a document into another representation, e.g., CSV to XML. Here, the document maintains the same data (semantics) but changes the syntax that is represented. I.e. we translate the document, but typically we don’t modify the structure. Normally, this type of transformation is bidirectional, since we still have the same semantic content, we can apply the same transformation logic and obtain the document in its original format.

• Semantic Transformations: This type of transformation usually occurs only in BizTalk maps. Here, the document maintains the same syntax that is represented (XML) but changes its semantics (data content). This type of transformation is typically one-way, since when we add and aggregate small parts of the information that compose the document into another document, we may miss important details for its reconstruction.

Note: In this article, we will talk only of semantic transformations, i.e., maps in BizTalk.

Where can maps be used?

Maps can be used for processing messages received at a receive port, inside orchestrations or for processing messages sent to a send port, as the following figure suggests:

The biggest difference between using maps in ports or in orchestrations is that when we use maps inside orchestrations, we can have multiple message inputs (transformations of many documents into one final document – transformations N -> 1), and ports only allow a single input message (transformations 1 -> 1).

Related links

• BizTalk Server: Basics principles of Maps – Introduction (Part 1)
• BizTalk Server: Basics principles of Maps – Introduction to map editor (Part 3)
• BizTalk Server: Basics principles of Maps – Basic maps functionalities (Document mapping) (Part 4)
• BizTalk Server: Basics principles of Maps – Organizing Maps (Part 5)
• BizTalk Server: Basics principles of Maps – Testing and Validation of maps (at design time) (Part 6)

For those looking to move beyond the basics of message transformation, I highly recommend checking out my eBook, BizTalk Mapping Patterns & Best Practices, published in partnership with BizTalk360.

This resource is a deep dive into the real-world challenges of data transformation. It covers:

• Mapping Patterns: From simple field-to-field links to complex structural shifts.
• Performance Optimization: How to build maps that don’t slow down your environment.
• XSLT vs. Functoids: Knowing exactly when to use built-in tools and when to write custom code.

Whether you are maintaining a legacy BizTalk 2010 environment or planning a migration, these patterns are the foundation of clean, maintainable integration.

Download the full eBook here: BizTalk Mapping Patterns & Best Practices

Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.