BizTalk Load - Strange Behaviour with File Size

After upgrading to a new instance of BizTalk Server (2006 to 2010), strange behaviour was seen with a customised Voucher load. All of the records were imported into 3e, but certain internal 3e Object Code operations were not being performed to amend the imported data. This only happened when the imported flat file was greater than a particular size (32,218 Bytes in this case).

Following advice from this article, I changed the value of the Large Message Size in the BizTalk Group Settings from 100KB to 315KB.

This solves the problem. It seems message fragmentation caused by an insufficient message size threw errors which eventually led to the Process in 3e not executing methods further downstream.

See this msdn blog post for further information.

BizTalk Server and Transaction Service Config

The configuration settings file used to set up BizTalk server to 3e instance communication can be found here by default: <Program Files of BizTalk Server>\Microsoft BizTalk Server\EAI\EAI.Biztalk.Config (i.e. C:\Program Files (x86)\Microsoft BizTalk Server\EAI\EAI.Biztalk.Config).

A particularly useful value is contained in the <Cobra> node. This holds the transaction service URL that BizTalk uses to integrate with the 3e instance. Connection credentials are also stored here.

...
<Cobra>
 <WebServiceUri location="http://TE_3E_SERVER/TE_3E_INSTANCE/WebUI/TransactionService.asmx" />
 <DefaultUser userName="BizTalkUser" password="*encrypted password*" domain="NetworkDomain" />
</Cobra>
...