Framework.BizTalk.Components 2.0.5

Parts Merger Pipeline Component

Overview

PartsMergerComponent is a custom BizTalk pipeline component designed to operate after the Disassemble stage of a receive pipeline. It transforms a multi-part message into a single-part message, applies optional transformations, and promotes properties for downstream processing.

Features

• Converts multi-part messages to single-part messages.
• Applies transformation based on a specified map.
• Promotes properties for routing and processing.
• Supports envelope schema matching and body unwrapping.
• Configurable error handling behavior.

Configuration

The component is configured via the following properties:

Usage

1. Add the PartsMergerComponent after the Disassemble stage of your custom receive pipeline.
2. Configure the properties via the pipeline designer or programmatically.
3. Deploy the pipeline and assign it to your receive location.

Importing XSLT Templates from Embedded DLL Resources

This feature allows XSLT templates to be imported directly from DLLs where the templates are embedded as resources. It streamlines deployment and improves maintainability by bundling transformation logic with related assemblies.

Requirements

• Assembly must be deployed to the Global Assembly Cache (GAC)
• XSLT file must be embedded as a resource in the assembly

Example

<xsl:import href="resource://gac/Framework.BizTalk.Maps.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=eae13714e186477a/segments.xslt"/>

Error Handling

If an unexpected content type is encountered, the component throws an exception:

InvalidDataException("PartMerger: Unexpected content type. Ensure that previous stage is producing text/xml.");

Parts Splitter Pipeline Component

Overview

PartsSplitterComponent is a custom BizTalk pipeline component designed for use in the Pre-Assemble stage of a send pipeline. It works in conjunction with the PartsMergerComponent (used in receive pipelines) to support a round-trip message transformation scenario. The splitter reverses the merging process by extracting individual message parts from a unified structure.

Key Features

• Splits a single-part message into multiple parts based on inferred schema.
• Automatically detects the schema from the message type (no manual configuration required).
• Supports HL7 and other structured formats.
• Designed to work seamlessly with PartsMergerComponent.

Configuration

The component can be configured with the following properties:

Usage

1. Add the PartsSplitterComponent to the Pre-Assemble stage of a custom send pipeline.
2. Configure the component properties via the pipeline designer.
3. Deploy the pipeline and assign it to the appropriate send port.

HL7 Rule-Based Modifier Pipeline Component

Overview

The HL7 Rule-Based Modifier is a custom BizTalk pipeline component designed to modify HL7 messages before they reach the disassembler stage. It uses a configurable set of transformation rules defined in XML to identify and replace specific fields in HL7 segments, including support for repeating segments.

This component is ideal for scenarios where HL7 messages need to be normalized, corrected, or enriched based on dynamic business rules.

Features

• Modify HL7 fields using configurable XML rules
• Supports repeating segments via optional seq attribute
• Uses a lightweight custom HL7 parser (no external dependencies)
• Regex-based matching for flexible transformations
• Designed for use in the Decode stage of a BizTalk receive pipeline

Rule Configuration

Rules are defined in XML format and passed to the component via the RulesXml property.

Example Rule XML

<rules>
  <rule segment="MSH" field="3" match=".*" replace="NewApp" />
  <rule segment="PID" seq="1" field="5" match=".*" replace="Doe^Jonathan" />
  <rule segment="PID" field="3" match=".*" replace="999999" />
</rules>

HL7 Rule XML Attribute Reference

Notes:

• Field indexing starts at 1 because the segment name is at index 0.
• The match pattern uses standard .NET regular expressions.
• If multiple rules match the same segment and field, they are applied in the order they appear in the XML.

XSLT Extensions (for AssemblyQualifiedMapName)

Example

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:helper="urn:biztalk:helper-functions"
    exclude-result-prefixes="helper">

  <xsl:output method="xml" indent="yes"/>

  <xsl:template match="/root">
    <output>
      
      <upperText>
        <xsl:value-of select="helper:ToUpper(name)"/>
      </upperText>

      
      <currentDate>
        <xsl:value-of select="helper:GetCurrentDateTime('yyyy-MM-dd')"/>
      </currentDate>

      
      <counter>
        <xsl:value-of select="helper:Increment('myCounter')"/>
      </counter>
    </output>
  </xsl:template>

</xsl:stylesheet>