It’s becoming more and more eminent to understand under which CLR version (1.0, 1.1 or 2.0) the BizTalk runtime, In-Process host is running. I’ve explained in my previous post the various factors that influence loading appropriate CLR versions and also how you can make use of the config file to force a specific version of … Continue reading Detect CLR version under which your BizTalk service is running.
Under which version of .NET Framework my code is going to run? I came across this interesting question in BizTalk newsgroup, “I am just wondering though how my local computer knows which CLR to load for the BizTalk Server 2004 Orchestrations when there is no entry in the BTSNTSvc.exe.config file to specifically point to the … Continue reading BizTalk 2004 and .NET 2.0
“BizTalk Server 2004: Receieve Pipeline woes v2” by Charles Young, I guess description for “Seekable streams and MAPS” is incorrect.
Charles Young has written this article “Receive Pipeline Woes V2” few months back. It’s one of the very good articles out there, which explains some of the insights of BizTalk Server internals. But under the heading “Seekable Streams” it appears that the description is not correct. Recently, I came across a strange problem with custom pipeline component … Continue reading “BizTalk Server 2004: Receieve Pipeline woes v2” by Charles Young, I guess description for “Seekable streams and MAPS” is incorrect.
Pipelines are implemented in a BizTalk 2004/2006 project for a variety of reasons, including encryption/decryption, splitting single XML documents into multiple documents, and converting flat files into XML documents etc. For doing above mentioned tasks we’ll be using Pipeline components (which gets deployed in different stages of a pipeline). For more information about Pipeline and … Continue reading Biztalk Custom Pipeline Component Development Tip
When you write custom disassembler code for pipeline components, you must make sure that you do not close the incoming data stream in the custom disassembler code. The incoming stream from the input message is a shared resource. The incoming stream is also used by the message body tracking component in the BizTalk Server message … Continue reading Handling incoming data streams in pipeline components in BizTalk Server 2004/2006
A byte order mark is appended to a message when the assembler component or the disassembler component is used to process a message in BizTalk Server. If you use a PassThruReceive pipeline or a PassThruTransmit pipeline, a byte order mark is not appended to a message. In UTF-16 encoding, a byte order mark is the … Continue reading Delete Byte Order Mark from outgoing messages in Biztalk 2004/2006
Understanding BizTalk Server 2004 BizTalk Server 2004 Performance Characteristics Developing Integration Solutions with BizTalk Server 2004
The BizTalk Server 2004 Health Monitor tool is a Microsoft WindowsÂ® service that is designed to monitor application hosts for active messages based on conditions that are set in the configuration file. The user can specify how long (in hours) messages can be active and how many messages can be active before the tool reports … Continue reading Biztalk Health Monitoring Tool