November, 2004

In the past, I have tended to focus on sequential convoys. Now, I decided to take a look at Concurrent Convoys. First off, I was sure in older versions of the documentation they were called Parallel Convoys? Maybe I’m mistaken or maybe the name changed over the past few months…. In any case, I will get with the times and call them Concurrent Convoys. No matter what you call them, the power and usefulness of this type of convoy is the same. Why use Concurrent Convoys? Concurrent convoys...

In many cases it can be useful to know the exact name of your output file that will be sent from your Orchestration using the File Adapter. This can be difficult if you are using the %MessageId%.xml macro to write the file since this it set after the message is sent from the Orchestration. Delivery Notification can help you determine if your message was sent successfully but it can not give you the file name. BizTalk 2004 has two ways to dynamically name your files from inside the Orchestration....

What? How? When? Why? Useless? You have no clue what I am talking about? What are BTXTimerMessages? They are messages BizTalk uses internally to control timers. This includes the delay shape and scope shapes with timeouts. How will you see BTXTimerMessage? You will see these messages in HAT. They will be associated with running Orchestations. If they show up, they will be in the Delivered, Not Consumed (zombie) message status. When will you see BTXTimerMessages? I see these messages when I am working...