Lab : Implementing BizTalk in-process receive adapter

This MOC style lab is the second one of the series of labs that I’ll write about how to develop the BizTalk adapters. Especially, this one will show you how to develop BizTalk In Process File Receive Adapter in C#. The purpose of this lab isn’t to provide every details and best practices of the development of the BizTalk adapter. This adapter sample code doesn’t use any abstraction layer such as Base Adapter. After completing this lab, I think that you can understand the big picture and you can continue to develop more sophisticated your own adapters.

Bloggers Guide to BizTalk Janyary 2005

I’ve just posted the January 2005 edition, sorry it’s so late. I think I’d better start trying to get them back to the start of the month again. I’ve been real busy with buying and selling apartments, packing, tidying, etc. and will be moving early March. (Just hope Bredbandsbolaget can switch my 10M line to the new place by the time I move in.)


 


As for the guide, it’s up to 218 articles now, the target for the year is to break through the 500 barrier. More contributors are always welcome, as are any feedback and comments.


Get it here…

BizTalk Server 2004 – An update

Recently the BizTalk Server exam has been released.  Just do as I did and take it to get yourself certified!  For more information, see Scott’s blog.

Another important milestone in the life of this great product: SP1 has been released TODAY!!  Get it NOW!
I strongly advise everyone to test it in your test environment and bring it in production as soon you can: it’s worth it!  In addition to that, we got now an adapter migration toolkit: something you might find interesting if you’re planning to migrate your integration solutions from BizTalk Server 2002 to 2004.

 

 

Share this post: Email it! | bookmark it! | digg it! | reddit!

Suppress Nodes Inside A Map

This map sample shows how to suppress nodes inside a map by passing false from a logical functoid. The blog post below gives more detail on the sample.

The mapper in BizTalk 2004 makes it easy to suppress nodes inside the mapper. The key is to send the looping node a “false” from a Logical Functoid. I have tried sending a Boolean False value from a Scripting Functoid but that was unsuccessful.

Get more information from the original blog post on this topic: https://www.biztalkgurus.com/biztalk_server/biztalk_blogs/b/biztalk/archive/2005/01/27/how-to-suppress-nodes-in-the-biztalk-mapper.aspx

How to Suppress Nodes In the BizTalk Mapper

Recently on a project I was required to filter out single records from a large batch that were not required to be processed inside the business process.  In this case, the vast majority of the thousands of input records would not be required in the Orchestration.



Rather the load the whole document into the Orchestration or break the document up into single messages, I decided to just suppress the non-required nodes in the mapper.  This would greatly reduce the number of input records into the system.



The mapper in BizTalk 2004 makes it easy to suppress nodes inside the mapper.  The key is to send the looping node a “false” from a Logical Functoid.  I have tried sending a Boolean False value from a Scripting Functoid but that was unsuccessful. 



This would look like this:





In this case, if the Logical Equals is “false” the Info node will not be created.  This can be very handy if you want to suppress records for items that are out of stock or for records that do not need to be processed inside the Orchestration.



Note that in this case the Looping Functoid is not required.  Removing it does not change the results.  The Node is still suppressed if the Logical Equals returns “false”.  I always include the Looping Functoid when looping records.



I have put together a sample that shows a simple suppression and a more complex scenario. 



Download: Suppress Nodes Sample