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, which will provide an extension of BizTalk out-of-the-box pipeline capabilities.
What’s to expect in this version?
Content-Based Routing Pipeline Components
CBR IDoc Operation Promotion Encode component (CBRIdocOperationPromotionEncode)
- Content-Based Routing Component to promote IDOC Operation property.
- This component requires one configuration that is the MessageType string to be ignored. Then it will take the last string (word) from the MessageType Message Context Property and promote it to the Operation Message Context Property.
- This component is to be used on the Encode stage of BizTalk Server Send Pipelines and to be used exclusively on Send Ports.
CBR Operation Promotion Encode component (CBROperationPromotionEncode)
- Content-Based Routing Component to promote Operation property.
- This component doesn’t require any configuration. Then it will take the value (word) which lies ahead of the cardinal (#) from the MessageType message context property and promote it to the Operation Message Context Property.
- This component is to be used on the Encode stage of BizTalk Server Send Pipelines and to be used exclusively on Send Ports.
The project is available on BizTalk Server Open Source Community repository on GitHub (https://github.com/BizTalkCommunity) and everyone can contribute with new pipeline components that can extend or improve the 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.
Deploying Pipeline Components
All the .NET pipeline component assemblies (native and custom) must be located in the \Pipeline Components folder to be executed by the server. If the pipeline with a custom component will be deployed across several servers, the component’s binaries must be present in the specified folder on every 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
Where to download?
You can download BizTalk Pipeline Components Extensions Utility Pack from GitHub here: