For the people who do not have an IT background, understanding about BizTalk Server may be difficult as they are not familiar with the terms such as XML, SOA, Orchestrations, SOAP, etc. Let us learn about this server in simple language. In the messaging subsystem of the BizTalk Server Architecture, XML messages are received and sent. The files enter through Receive Ports and are delivered to the "Message Box" by means of a "Receive Pipeline". They are then taken up by "BizTalk Orchestrations" where the message processing takes place. They are then sent out by means of a Receive Pipeline through a "Send Port" to the target. The Receive Ports are the channels through which the messages come into the BizTalk. These channels may be HTTP, SQL, SOAP, EDI, file, etc. These channels do not have any effect on the way they are processed at the later stage. Because of this reason, you are able to modify the channel type and the source of the data even after the deployment of your application, without modifying your application implementation. Now the server can manage varied forms of transportation through the adaptors like SAP or DB2 adaptor.

Receive Pipeline comprises of several frameworks for instance, "Party Resolution", "Disassembling" and "Decoding". There is an option of "Pass Through" pipeline in this solution that is necessary for the smooth transport to the Message Box. Several custom pipeline components can be used according to special tasks of the mechanisms. The message Box is the core of the BizTalk server as would be agreed by any BizTalk consultant. Through this, the Server takes care of the dependability for your messages with regard to the assured timely delivery. In case the node in the Server fails, the message will be taken up by another node. The file from the message folder location is not deleted while using file or any mode of transport, unless it is kept on entirely in SQL. The BizTalk Publish-Subscribe system makes out which Orchestrations subscribe to that specific message, depending on the promoted data, and in view of that, routes it. The Orchestrations are basically the processed that are described in the Business Process Execution Language (BPEL). Using the Transformation Maps, the format of the message can also be altered at this step. 

Business Rules Engine is drawn on by BizTalk Development for issuing the existing strategies which are a set of Rules from the Orchestration that are ever-changing. The function of the "Send Pipelines" is a complete opposite of the "Receive Pipelines" and includes "Signing", "Encoding" and "Assembling" of the message. Last to learn about is the Send Ports that manage the transport similar to the receive ports but in the opposite direction, that is, from the Message Box to the target.