Hello,
I am facing an issue when deploying a particular BizTalk project using BTDF, where the party settings get overwritten when they shouldn't be.
I've confirmed that the PortBindingsMaster.xml for this project does not have any party settings, like so:
The BTDF logs show the following trace entries for the orchestration assembly that is causing this issue:
This is different from the trace entries for other orchestration assemblies which shows that there is no binding information to restore in the post-update event:
As a test, I even removed all artefacts in the orchestration project in question and the issue still occurs - so it appears this has nothing to do with the contents of the orchestration project.
What configuration controls the post-update event?
It appears some misconfiguration is causing this. Any pointers would be greatly appreciated!
Thanks and Regards,
Rohan.
I am facing an issue when deploying a particular BizTalk project using BTDF, where the party settings get overwritten when they shouldn't be.
I've confirmed that the PortBindingsMaster.xml for this project does not have any party settings, like so:
<PartyCollection />
In fact the issue occurs even when the BTDF proj file has the binding related flags switched off:<IncludeMessageBindings>false</IncludeMessageBindings>
<UsingMasterBindings>false</UsingMasterBindings>
<PortBindingsMaster>PortBindingsMaster.xml</PortBindingsMaster>
To isolate the issue, I switched off all components (IncludeSchemas, IncludeComponents, IncludeTransforms, etc.) and was able to repro the issue when IncludeOrchestrations was enabled:<IncludeOrchestrations>true</IncludeOrchestrations>
Further, the issue occurs with only one of the Orchestration projects added under ItemGroup\Orchestrations node.The BTDF logs show the following trace entries for the orchestration assembly that is causing this issue:
Information: Installed the "Communication.Orch.CommunicationDocument.dll" assembly into the Global Assembly Cache. (force=True)
Information: Deploy operation succeeded.
Information: Updating binding information.
ConnectionString="Data Source=.;Initial Catalog=BizTalkMgmtDb;Integrated Security=True;Enlist=True;Application Name=Microsoft.BizTalk.ApplicationDeployment.Engine"
Information: Updating send ports, send port groups, and receive ports...
Information: Updating parties and enlistments...
Information: Updating orchestration bindings...
Information: Successfully updated binding information.
__ Information: Beginning post-update operations for assembly "Communication.Orch.CommunicationDocument, Version=1.0.0.0, Culture=neutral, PublicKeyToken=...". Information: Updating binding information.
ConnectionString="Data Source=.;Initial Catalog=BizTalkMgmtDb;Integrated Security=True;Enlist=True;Application Name=Microsoft.BizTalk.ApplicationDeployment.Engine"
Information: Updating send ports, send port groups, and receive ports...
Information: Updating parties and enlistments...
Information: Updated "Party: AC"
__ Information: Updated "Party: AD" Information: Updated "Party: CD"
Information: Updated "Party: CU"
Information: Updated "Party: DF"
Information: Updated "Party: DO"
Information: Updated "Parties and Partnerships"
Information: Updating orchestration bindings...
...This is different from the trace entries for other orchestration assemblies which shows that there is no binding information to restore in the post-update event:
ConnectionString="Data Source=.;Initial Catalog=BizTalkMgmtDb;Integrated Security=True;Enlist=True;Application Name=Microsoft.BizTalk.ApplicationDeployment.Engine"
Information: Updating send ports, send port groups, and receive ports...
Information: Updating parties and enlistments...
Information: Updating orchestration bindings...
Information: Successfully updated binding information.
__ Information: Beginning post-update operations for assembly "Communication.Orch.MemberCommunication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=...". Information: No binding information to restore.
Information: Ending post-update operations for assembly "Communication.Orch.MemberCommunication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=...".
__As a test, I even removed all artefacts in the orchestration project in question and the issue still occurs - so it appears this has nothing to do with the contents of the orchestration project.
What configuration controls the post-update event?
It appears some misconfiguration is causing this. Any pointers would be greatly appreciated!
Thanks and Regards,
Rohan.