Default Pipelines
When you create a new application, the default pipelines are created and deployed by default and appear in the Microsoft.BizTalk.DefaultPipelines assembly in the \References folder for every BizTalk project. The default pipelines cannot be modified in Pipeline Designer. These pipelines can be selected when configuring a send port or receive location in BizTalk Explorer. This topic describes the default pipelines and when to use them.
 Note |
|---|
| The XML receive and XML send pipelines do not support XML documents larger than 4 gigabytes. |
The pass-through receive pipeline has no components. It is used for simple pass-through scenarios when no message payload processing is necessary. This pipeline is generally used when the source and the destination of the message are known, and the message requires no validation, encoding, or disassembling. This pipeline is commonly used in conjunction with the pass-through send pipeline.
Because it does not contain a disassembler, the pass-through receive pipeline cannot be used to route messages to orchestrations.
| Note |
|---|
| The pass-through receive pipeline does not support property promotion. |
Do not use the StsFileReceive, StsReceive, or StsSend pipelines. They are included in BizTalk Server 2006 only for backward compatibility with the BizTalk SharePoint Messaging Adapter component in BizTalk Server 2006 Business Activity Services (BAS). In BizTalk Server 2006 this component has been replaced with the BizTalk 2006 native adapter for Windows SharePoint Services, which does not have a dependency on these pipelines or the containing assembly.
StsFileReceive pipeline
The StsFileReceive pipeline consists of the following stages:
-
Decode. Empty
-
Disassemble. Contains the XML Disassembler component
-
Validate. Empty
-
ResolveParty. Empty
StsReceive pipeline
The StsReceive pipeline consists of the following stages:
-
Decode. Empty
-
Disassemble. Contains the XML Disassembler component
-
Validate. Empty
-
ResolveParty. Runs the Party Resolution component, which resolves the source security ID to the party ID. The certificate subject is not used for party resolution.
StsSend pipeline
The StsSend pipeline consists of the following stages:
-
Pre-assemble. Empty
-
Assemble. Contains the XML Assembler component configured to add the Microsoft.BizTalk.KwTpm.StsDefaultPipelines.EnvSchema XML envelope around the message
-
Encode. Empty
