Integrating to the max...BizTalk Style

    Problem (identfied with: BizTalk 2010 / ESB Toolkit 2.1 ) The ESB Toolkit is a set of components and artefacts which provide Enterprise service bus functionality on top of BizTalk. One of the capabilities of BizTalk is debatching (Xml, Flat files). During debatching a single message is debatched into several messages (e.g. an OrderBatch containing multiple orders). The default behavior is that each message will be placed onto the messagebox for additional processing. In a business context it is desired that the entire batch is processed before the flat file is removed, thus Recoverable Interchange Processing should be set to FALSE.   In an ESB Toolkit context it is possible to follow the same approach, but not only debatch the message, but also start of a new process using an itinerary. This means that each individual messages leads to a new process.   In this case, the disassembler and the ESB Dispatcher are required to interoperate with eachother. T...

Hereby some BizTalk gotchas, that got me, it’s a small compilation as I’m trying to group related subjects together, in future posts I’ll focus on MSMQ, ESB Toolkit and other stuff. Issue: Outputfile name is %sourcefilename% Is it, that…? Y ou have promoted the FILE.ReceivedFileName and configured the macro %SourceFileName%, however, this is CASE SENSITIVE! Issue: No processing takes place after a BRE call Is it, that…? You might be using a .Net helperclass, you’ve added the ‘StaticSupport’ following ( http://msdn.microsoft.com/en-us/library/dd298814(v=bts.10).aspx ). This won’t work…the StaticSupport should be created under the WOW64Node Issue: Pipeline configuration change does not have any effect Is it, that…? You are using a dynamic send port…if so, stop/start the application-port Issue: Inside my orchestration, a variable assignments (from context properties) leads to an exception (missing property exception) Is it, that…? You are not assigning the variable fro...

  As I mentioned…I have a blog backlog…so much to do, so little time…so you can help me out. I have several pending blog items. Hereby the current list and I invite you to help me out in determining the priority, otherwise…it will be me who chooses what’s next . Sorry for the delay in posting….   Kind regards, Sander

  In case the mapper fails (and only then, these steps will help you out a bit!) when you do Test map, and it seems to be caused by a Custom Functoid that can not be loaded, perform the following steps; You have to call the ‘Debug’ map, this will generate the XSLT and will start the debugging This will give you an error in case there are errors Look in the output window, for the clear and distinct hint (e.g. : NS0 is the namespace causing the problem); Now perform a ‘Validate’ map to get the Extension XSLT; Open the .extxml.xml Look for the specific namespace (NS0): Open the custom functoid and make sure that the classname / SetExternalFunctoin are EXACTLY identical. If this is the case, you can do the following (but you’re problably in the zone….the problem zone) 1) Perform a build on the Functoid library 2) Redeploy the Functoid library 3) Restart visual studio 4) Open the map, Reset the toolbox 5) Verify that the map works LAST RESORT!! 6) Remove t...

  Several weird issues I’ve encountered have made my think about a special blog theme ‘BizTalk Quircks’. The first one is the BizTalk mapper in 2010. As blogged earlier, there are some behavior differences, but to my opinion as well a few bugs. As I’ve not spent a lot of time reproducing the issues but have met colleagues with the same issues, here some issues you might encounter; A link to a functoid that is removed remains active in the functoid parameters This means that it isn't possible to create a new link, the parameter has to be manually removed in the mapper. Creating several links to a functoid (with e.g. 6 params) lets the mapper loose count I had a functoid with 6 parameters, filled them all, but somehow the link of parameter 6 created a void parameter 7, this meant i got a validation. When i removed the parameter in the functoid it was all fine and dandy. Creating a 'new' message (SalesOrder = SalesOrder) using a map doesn't filll all the values ...