Basics of BizTalk Runtime Architecture

Posted: June 19, 2009  |  Categories: BizTalk

BizTalk runtime architecture primarily has four major components:

  • Receive Handler;
  • Message Box;
  • Orchestration;
  • Send Handler.
BizTalk Server Runtime Architecture

Receive handler

Receive handler held responsible for receiving messages from the channel contains one or more receive locations.

Receive location is a combination of receive adapter and receive pipeline.

Receive pipeline has four stages:

  • Decode: is used for components that decode or decrypt the message like verifying message signatures to ensure integrity, or decoding the S/MIME messages.
  • Disassemble: This stage is used for components that parse or disassemble the message. The message gets converted entirely into the XML format so that the messaging engine can understand it.
  • Validate: check to see if the message is in the correct format or not.
  • Resolve Party: like the decode stage, deals with message security using encryption and digital signature with the help of certificates. (map the sender certificate or the sender security identifier (SID) to the corresponding configured BizTalk Server part)
Receive Port Architecture

MessageBox

MessageBox is the publishing area. The messages read from the channel are published into the MessageBox.

Orchestrations

Orchestrations execute business logic. They play subscriber as well as publisher role. They acquire subscribed message instance from the MessageBox and carry out business processing.

Send handler

Send handler plays the subscriber role. It fetches a message from the MessageBox and pushes them through a channel. Send handler is a combination of send pipeline and adapter.

Send pipeline contains three stages:

  • Preassemble: pre-processing of the message before it needs to be assembled.
  • Assemble: responsible for assembling or serializing the message and converting it to or from XML, in other words, convert the message to a format that can be understood by the external system.
  • Encode: is used for components that encode or encrypt the message.
Send Port Architecture
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

1 thought on “Basics of BizTalk Runtime Architecture”

Leave a Reply

Your email address will not be published. Required fields are marked *

BizTalk360
BizTalk Server

Over 500+ customers across
30+ countries depend on BizTalk360

Learn More
Serverless360
Azure

Manage and monitor serverless
components effortlessly

Learn More
Atomicscope
Business Users

Monitor your Business Activity in iPaaS
or Hybrid integration solutions

Learn More

Back to Top