BizTalk Messaging Architecture
4 likes1,489 views
The document outlines the architecture of BizTalk's messaging system, highlighting its publish and subscribe model, content-based routing, and the roles of send and receive ports. It explains the function of the BizTalk message box as a central component for managing message storage and processing within the server. Additionally, it describes how transformations can be applied to messages during the sending and receiving processes.
BizTalk Messaging Architecture
- 2. CONTENTS BizTalk’s Publish and Subscribe Architecture Content based routing Send and Receive Ports BizTalk Message Box Applying Transformations to Messages 5/25/2016 2
- 3. BIZTALK’S PUBLISH AND SUBSCRIBE ARCHITECTURE • The Publisher uses a topic-based approach to publish messages to topic A and to topic B. • The subscribers subscribe to these topics; one subscriber subscribes to topic A, one subscriber subscribes to topic B, and one subscriber subscribes to both topic A and to topic B. 5/25/2016 3
- 4. BIZTALK’S PUBLISH AND SUBSCRIBE ARCHITECTURE • BizTalk Server receives messages through input ports and stores them in the Message Box database. • Orchestration ports and send ports consume messages from this database based on their subscriptions. 5/25/2016 4
- 5. BIZTALK’S PUBLISH AND SUBSCRIBE ARCHITECTURE • A receive port is a collection of one or more receive locations that define specific entry points into BizTalk Server. A receive location is the configuration of a single endpoint (URL) to receive messages. • A send port is the combination of a send pipeline and a send adapter. A send port group is a collection of send ports and works much like an e-mail distribution list. • Orchestrations can subscribe to (receive) and publish (send) messages through the MessageBox. • The heart of the publish/subscribe engine in BizTalk Server is the MessageBox database. The MessageBox is made up of two components: one or more Microsoft SQL Server databases and the Message Agent. • A host is a logical representation of a Microsoft Windows process that executes BizTalk Server artifacts such as send ports and orchestrations. 5/25/2016 5 Lifecycle Of a Message
- 6. BIZTALK’S PUBLISH AND SUBSCRIBE ARCHITECTURE 5/25/2016 6
- 7. CONTENT BASED ROUTING • Filters enable you to dynamically determine which send port will be used to process a message or which Orchestration will process a message. • You can also apply filters to Receive shapes on BizTalk orchestrations. This can enable two orchestrations to process the same type of messages but process them differently based on data held within the message. 5/25/2016 7
- 8. SEND AND RECEIVE PORTS • Ports are physical communication endpoints used by BizTalk to send or receive messages. • Receive ports can be configured with one or more receive locations, each of which maps to an endpoint (URL) for a specific adapter. • Send ports, unlike receive ports, are a one-to-one mapping in that you define one send port and map it directly to one BizTalk adapter. 5/25/2016 8
- 9. BIZTALK MESSAGE BOX • The BizTalk MessageBox is implemented as a SQL Server database and is shared between all BizTalk servers in a BizTalk group. • All inbound and outbound messages, along with orchestration execution, dehydration, rehydration, and message tracking, rely on the BizTalk MessageBox. • Messages are published to the BizTalk MessageBox; if there is more than one subscriber to a given message, both subscribers will receive a copy of the message. • The Message Agent then calls the bts_FindSubscriptions stored procedure held in the BizTalk MessageBox to establish which subscriptions, if any, match this message. This stored procedure queries the Subscription and Predicate SQL tables and joins them with the properties inserted for the batch of messages in the previous step to identify potential subscribers. • The Message Agent then calls the bts_InsertMessage stored procedure to insert the BizTalk message into the Spool SQL table, along with basic metadata about the message, such as the number of parts. • As part of this stored procedure, the int_EvaluateSubscriptions stored procedure, which, among other validation steps, inserts a reference to the message into the relevant Host Queue SQL table, follows the naming convention <HostName>Q. 5/25/2016 9
- 11. APPLYING TRANSFORMATIONS TO MESSAGES • Each receive or send port can apply a BizTalk map transformation (which is essentially an XSL to a message). • In the case of receive ports, the transformation occurs after the BizTalk adapter has received the message and after the pipeline has been executed. • In the case of the send port, the transformation is performed before the send pipeline has been executed. 5/25/2016 11
- 12. 5/25/2016 12
- 13. 5/25/2016 13