I finally started and published the first version of the sibling BizTalk project Mapper Extensions UtilityPack for BizTalk Server 2016: BizTalk Pipeline Components Extensions Utility Pack.
What is BizTalk Pipeline Components Extensions Utility Pack?
BizTalk Pipeline Components Extensions Utility Pack is a set of custom pipeline components (libraries) with several custom components that can be used in received and sent pipelines, extending BizTalk Server’s out-of-the-box pipeline capabilities.
📝 One-Minute Brief
An introduction to the BizTalk Pipeline Components Extensions Utility Pack, an open‑source GitHub project that adds reusable custom pipeline components to extend BizTalk Server 2016 receive and send pipeline capabilities.
What’s to expect in this version?
Content-Based Routing Pipeline Components
CBR IDoc Operation Promotion Encode component (CBRIdocOperationPromotionEncode)
This Content‑Based Routing (CBR) pipeline component promotes the IDoc Operation property from the message context.
First, the component requires one configuration value: the MessageType string to ignore. Then, it extracts the last segment of the MessageType context property and promotes it to the Operation message context property.
As a result, BizTalk can route messages dynamically based on the IDoc operation without additional orchestration logic.
Use this component only in the Encode stage of BizTalk Server Send Pipelines. Moreover, apply it exclusively on Send Ports, where outbound routing decisions occur.
CBR Operation Promotion Encode component (CBROperationPromotionEncode)
This Content‑Based Routing (CBR) pipeline component promotes the Operation property directly from the message context.
Unlike the IDoc variant, this component requires no configuration. Instead, it reads the MessageType context property and extracts the value after the cardinal character (#). Then, it promotes that value to the Operation message context property.
Consequently, BizTalk can perform routing based on message type conventions with minimal configuration.
Just like the previous component, use this one in the Encode stage of BizTalk Server Send Pipelines. Additionally, apply it only on Send Ports to ensure correct routing behavior.
Deploying Pipeline Components
All .NET pipeline component assemblies (native and custom) must be located in the Pipeline Components folder for the server to execute them. If the pipeline with a custom component is deployed across several servers, the component’s binaries must be present in the specified folder on each server.
You do not need to add a custom pipeline component to be used by the BizTalk Runtime to the Global Assembly Cache (GAC).
To know more about Deploying Pipeline Components, please see: Deploying Pipeline Components
Download
The project is available on the BizTalk Server Open Source Community repository on GitHub (https://github.com/BizTalkCommunity), and everyone can contribute new pipeline components to extend or improve existing BizTalk Server capabilities.
At the moment, it is only available for BizTalk Server 2016, but it will soon be compiled and available for previous versions of the product.
Special thanks to my team coworker at DevScope, Pedro Almeida, for helping me on this project.
You can download BizTalk Pipeline Components Extensions Utility Pack from GitHub:
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.
