Today I was working on some content for Tech Ed when I found a major error in a sample I posted about 4 months ago. The error caused the CR-LF’s between records to be included in the positional character count during debatching and actually into the messages themselves. This through off the file layout but did not give any errors. In fact, the expected result of three files were received. They just did not have the right data in them. I have seen similar problems in the past were the Flat File ......

Recently I have seen a lot of talk about large message support in BizTalk 2004. The most interesting and depressing was on the BizTalk Core Engine WebLog. It seems that large messages do not work as well in BizTalk 2004 as I would have hoped. I have had success with some types of large messages using the file adapter and mapping. I have gotten it to work with messages up to 500 MB but in a production environment this would not be a viable or supported solution. During some recent testing, I discovered ......

It is a common request. How can I debatch a message into smaller batches rather than single messages inside BizTalk 2004? I have tried many times to get this accomplished natively inside the pipeline. One would think it would be as easy as setting the group property to 10 if you wanted a batch size of 10, but that does not seem to work. The only way I have been able to break up a message into smaller batches has been inside custom code. I wrote a .net component that can be called using an atomic ......

The help guide gives many excellent examples of using WMI to perform a large variety of useful tasks in BizTalk 2004. One of the little known features is the ability to have suspended messages saved to a file at the time of suspense. I would assume this is govern by the same rules of viewing tracked messages in HAT, that is the stream must be seekable for the message to be tracked and in this case saved (see Christof’s Blog Post). What makes this feature so nice is it saves both the message ......