How to Develop BizTalk Custom Pipeline Components – Part2

In my current series, I am talking about developing custom pipeline components in detail. In part1, we talked about pipeline component types and about developing general pipeline component with example. I encourage you to refer part1 article to have a logical start in this article series.   In this part, I am talking…


How to Develop BizTalk Custom Pipeline Components – Part1

Receive and send pipelines in BizTalk are used to perform a range of processing and operations on messages. They can –   1.      Encrypt and decrypt messages 2.      Sign and verify digitally signed messages 3.      Validate message against schema 4.      Deal with promoted properties used for content based routing 5.      Disassemble or break single message…


Effect of Engine Control Functions on Business Rule Execution – Part2

In current series, we have already gone through rule execution algorithm and effect of “Assert” and “Update” on rule execution cycle. If you wish to recap, please go through these articles again @   Now, we are going to talk about rest of the engine control functions – Retract, RetractByType and…


Effect of Engine Control Functions on Business Rule Execution – Part1

Policies in BizTalk Rule Engine execute according to Match – Conflict Resolution – Action algorithm. Engine control functions influence rule execution cycle in big way. They cause execution cycle to recur more than once and also control action agenda to be executed.   Following are BRE engine control functions –   Assert Update Retract RetractByType…


Multiple Message Boxes in BizTalk (Scale out message box)

BizTalk runtime can be divided into “Process” and “Data” area in larger terms. Orchestrations, receive handler, send handler etc. run under process area. Process area is popularly called “Host”. Host can be mapped to several BTS machine in BizTalk Server group to achieve higher scalability. Such mapping instance is called “Host Instance”. So one “Host”…


Understanding Rule Execution in BizTalk Rule Engine

BizTalk business rule engine (BRE) is a wonderful tool to extend dynamics and flexibility of business. It allows business rules to be tailored on the fly with no hazards and downtime.   In BRE, you can define “Policy”. Policy contains “Rules” drafted by business people. You can consider “Policy” as a logical grouping of rules….


Understanding Inbound / Outbound Message Security in BizTalk

In the communication and integration world message is core entity. It is principal data carrier. Applications and businesses trade information using messages. BizTalk is content based publish-subscribe engine which facilitates in enterprise application and business-to-business integration. Some of the entities publish messages through BizTalk while other subscribe and consume.   Sometime, message security becomes a…


Long Term Facts / Fact Retriever in BizTalk Rule Engine

BRE Facts   Business is dynamic. Policies, rules, constraints are never stable and they amend/evolve with time. Processes, applications and workflows supporting any business model need to implement these changes with minimal maintenance and adoption hazards.   BizTalk Business Rule Engine (BRE) is a magnificent tool that scales out capabilities of policy/rule based applications and…


BizTalk Custom Receive Pipeline Component to Batch Messages

Introduction:   Pipelines in BizTalk are used to do specific processing on incoming and outgoing messages. Each pipeline has some stages in which stage specific components can be employed to do certain tasks.   “Disassemble” is the second stage of the receive pipeline which is primarily used to disassemble incoming messages, validate schema and promote…


BizUnit Quick Start Sample

For a long time, automatic unit testing of BizTalk interfaces was a night mare and BizTalkers were desperately looking for a sophisticated tool. With BizUnit 2.0, BizTalk interface unit testing has become an easy and efficient job. Purpose of this article is to give a quick start sample which can be used by beginners to…