Message De-Batching

Overview

Message de-batching is very common in integration scenarios. When a batch message is received into BizTalk environment de-batching can happen in receive pipeline or in orchestration.

The feature provides following capabilities.

1. Ability to log the batch message into main activity.
2. Ability to archive the batch message
3. Ability to link all the de-batched messages to their parent batch.
4. Ability to allow de-batched messages to progress with their individual journey.

De-Batching in Receive pipeline

1. De-batching happens in the disassemble stage of a receive pipeline. When a batch message received, the stage before disassembly must have batch id tracked and configured in atomic scope.

   

2. In above screen shot the stage “ReceiveBatch” should be configured to track BatchId. This ensures that batched is present in BizTalk context in later stages.

   

3. This means that the batch itself is considered as a separate transaction. In this case the Batch is the transaction name. And this stage needs to be started and updated as well.

   

4. The stage immediately after the disassembly must be marked for de-batching. This can be done in stage configuration.

   

   

5. There will be one entry in the tracking UI per transaction and they are identified with an icon as shown below.

6. You will have option to view all the transactions which came in one batch. The ui also provides and option to download the batch message.

   

7. View transactions from batch is going to display all the transactions belonging to a single batch.

   

De-Batching in Orchestrations

1. De-Batching in orchestration happens in a loop within an orchestration. When de-batching happens in orchestration, the Batch-Id must already be available in the context of the message. This means stages before the orchestration must already have tracked batch id.

   

2. Starting an activity should happen in construct shape or outside in an expression shape. The enriched message needs to be the de-batched message.

   

Debatching in Azure Scenarios

To leverage Atomic Scope's debatching functionality in Azure LogicApps , we ship a header called AS-BatchId and you need to pass any value which you need as a BatchId in this field.

1. Similar to BizTalk orchestration , De-Batching happens in a loop in Azure LogicApps as well. The above BatchId should be the same for the whole activity.

3. The stage immediately after the disassembly must be marked for de-batching. This can be done in stage configuration.

4. View transactions from batch is going to display all the transactions belonging to a single batch.