Flow of messages in Biztalk Server engine - Biztalk

What is the basic flow of messages in Biztalk Server engine?

1. Receive Port : Listens for messages.
2. Adapters information interchange with external systems.
3. Pipeline, dis-assembler and sub-components : Normalizing the schemas (wire message in its native format) of the internal messages using XML as the common language.
4. MessageBox : Internal XML messages are published here and then are further consumed by Subscribers.
5. Subscribers (Send Port and Orchestration components) : Subscribe to internal messages per metadata or message context properties.
6. When the subscribed orchestration finishes processing the internal messages are re-published in the MessageBox to be consumed by other subscribers.
7. Send Port : Consumes the internal XML messages, converts them to a wire messages through the associated pipeline and subcomponent Assembler.
8. Finally the adapter is used to convey the wire message to the target system.

What is the basic flow of messages in BizTalk Server engine?

After receiving the messages by a BizTalk adapter, the message runs through pre-processing within the BizTalk pipelines, before data transformation via BizTalk maps. These are ultimately published to a central database called the MessageBox. The parties with corresponding subscription for those messages can consume it. The MessageBox database makes up for providing durability, scalability, and reliability.
Components of Biztalk Server architecture - Biztalk
Components of Biztalk Server architecture - Receive Port: listens for messages. Adapters: information interchange with external systems
Business Activity Services (BAS) - Biztalk
Business Activity Services (BAS) - Trading Partner Management : Information workers Manage trading partner relationships within organizations.
Static, dynamic and direct binding - Biztalk
Static, dynamic and direct binding- Static Binding: A static port is already configured at the time of deployment to use a transport so as to deliver messages to a specific external end point.
Post your comment