Zombie messages are messages that were routed to a running orchestration from the messageBox and were currently “in flight” when the orchestration instance ended. In other words, we have …
In this article, we will see how to use variables in BizTalk bindings during automatic deployments using Azure DevOps. We will also see how to have different configurations depending on the …
One issue I often encounter within BizTalk projects is aggregating and assembling flat files. While mechanisms do exist to carry out both operations, the most important thing is still to know when …
The source schema comes from an SQL database. It comprises a single repeatable Order record, containing all the fields.
The destination schema comprises a number of records which are embedded.
Our …
This article will demonstrate how to deploy a BizTalk application on a BizTalk ‘On Premise’ server following generation of artifacts in Azure DevOps.
The BizTalk Server Application project …
To undertake the operations described in this article, an Azure DevOps account with creation rights over pipelines is necessary.
The aim of this article is to show how it is possible, from a …
Recently, wanting to apply conditions to a dual input map where both source messages have repeating nodes, I realized that this was no easy matter.
Message B (resulting from an SQL query) is …
In this article, we suggest using a send pipeline in an orchestration so as to aggregate messages. The advantages of this method are:
proper control over the structure of aggregated messages;
full …
We have seen, as part of a client project, the requirement to manage acknowledgments (ACK) and negative acknowledgments (NACK) when sending messages. This means we need to respond differently in the …
To communicate with APIs, the message format generally used by Microsoft BizTalk Server is XML or Json. There are indeed some native pipeline components which allows us, while both sending and …
When you want to debatch an XML file under BizTalk, there are two ways to do this either with a pipeline or with XPath.
Here it is going to be about the second way, and we will start with the unitary …
Why would we need to debatch an XML message in an orchestration with a pipeline instead of using straight the receive pipeline on the port ?
It turns out that is interesting for the following …
