Introduction Used in all BizTalk solutions Components Messages Message Boxes (SQL Server databases) Ports Pipelines Pipeline components Adaptors

Used in all BizTalk solutions

Components

Messages

Message Boxes (SQL Server databases)

Ports

Pipelines

Pipeline components

Adaptors

Messages The lifeblood of BizTalk Can be either XML (Most Common) or Binary Can be tracked using HAT

The lifeblood of BizTalk

Can be either XML (Most Common) or Binary

Can be tracked using HAT

Pipelines Provide the ability to perform processing and validation on incoming or outgoing messages Four out of the box pipelines are: Xml Receive – Contains the XML disassembler PassThru Receive – No processing occurs in this pipeline XmlTransmit – Contains the XML assembler. PassThru transmit – Same as receive but out bound

Provide the ability to perform processing and validation on incoming or outgoing messages

Four out of the box pipelines are:

Xml Receive – Contains the XML disassembler

PassThru Receive – No processing occurs in this pipeline

XmlTransmit – Contains the XML assembler.

PassThru transmit – Same as receive but out bound

Receive Pipeline Stages Decode Disassemble Validate Resolve Party

Decode

Disassemble

Validate

Resolve Party

Send Pipeline Stages Pre-Assemble Assemble Encode

Pre-Assemble

Assemble

Encode

Subscription Core principal of BizTalk Once a message has been processed it needs to be routed An orchestration or send port can “subscribe” to show it is interested in processing Each message has context properties The message type property is assigned by the XML disassembler Subscription is based upon message type and various other context properties You can have your own properties these are known as promoted properties

Core principal of BizTalk

Once a message has been processed it needs to be routed

An orchestration or send port can “subscribe” to show it is interested in processing

Each message has context properties

The message type property is assigned by the XML disassembler

Subscription is based upon message type and various other context properties

You can have your own properties these are known as promoted properties

Message Box After processing by the adaptor and pipeline the BizTalk message agent commits the message to the message box All inbound and outbound messages stored Orchestration execution, dehydration, rehydration and message tracking rely on this

After processing by the adaptor and pipeline the BizTalk message agent commits the message to the message box

All inbound and outbound messages stored

Orchestration execution, dehydration, rehydration and message tracking rely on this

Ports Physical end points for sending and receiving messages The selection of communication type defines how external systems communicate with BizTalk For send ports the type defines how BizTalk communicates with other systems

Physical end points for sending and receiving messages

The selection of communication type defines how external systems communicate with BizTalk

For send ports the type defines how BizTalk communicates with other systems

Receive Ports Used for getting messages into BizTalk Have one or more receive locations This means that the same port can have different communication methods

Used for getting messages into BizTalk

Have one or more receive locations

This means that the same port can have different communication methods

Send Ports Used for sending messages from BizTalk One to one relationship Can use send port groups to send to multiple endpoints

Used for sending messages from BizTalk

One to one relationship

Can use send port groups to send to multiple endpoints