Dynamic send ports lose
pipelines on redeployment
Considering the following scenario:
- You have a dynamic
send port configured as using customized send pipeline, receive pipeline,
inbound map, outbound map and filters.
- You try to do a redeployment
by using BTSTask AddResource, and it
shows the deployment is successful.
In this case, when you refresh
the send port to check the configurations, you will notice that the send
pipeline and receive pipeline are reverted back to the default values as below
screenshot shows :
Also, when you check the binding
file under C:\Users\<usename>\AppData\Roaming\Microsoft\BizTalk
Server\Deployment\BindingFiles after the redeployment, you notice it contains
all appropriate customized receive pipeline and send pipeline indeed.
This issue occurs because you
choose the default pipeline (Microsoft.BizTalk.DefaultPipelines.PasssThruTransmit
or Microsoft.BizTalk.DefaultPipelines.XMLPipeline ) as the send pipeline & receive
pipeline for dynamic send port in Visual Studio. Please refer to below picture:
Thus even though you choose the
custom send pipeline & receive pipeline in BizTalk server Administration
Console then do a redeployment, the Send Pipeline & Receive Pipeline options
are still the ones you selected when you configured the dynamic send port in
Visual Studio. This is by design.
If you would like to use the
custom send pipeline & receive pipeline for dynamic send port, please
1. Change the Send Pipeline & Receive Pipeline to the
custom pipeline in Visual Studio.
2. Redeploy the BizTalk project.