Overview of the New BizTalk 2006 Sharepoint Adapter

I came across Adrian Hamza’s blog today.  His blog seems to be totally dedicated to the Sharepoint Adapter for Biztalk. 



It looks like it will be a great resource for information on anything related to Sharepoint and Biztalk integration.



The post I like best gives a detailed comparison between the GotDotNet Sharepoint Adapter and the new Biztalk 2006 Sharepoint Adapter. 



I think the best new “feature” of the Sharepoint Adapter is that it will be supported by Microsoft.  I know this has held up a lot of customers from using it in the past.


Performance Testing Tool for Biztalk

Larry Beck from Avanade has released a Biztalk Throughput and Capacity Testing Tool for testing Biztalk Performance. 



This tool will automatically generate files for you to submit them into Biztalk.  In addition, it will track server parameters in a nice graph.  It’s configurable through a UI.



You can get more information on his blog or on the GotDotNet workspace.


 


Who is Larry Beck?  He is a Connected System Evangelist and fellow Texan who works for Avanade.  Avanade is a joint venture between Accenture and Microsoft.  If you went to TechEd, you probably saw there video in the Key Note.



Look for more good things to come from him blog! 


 

Suspended Message Routing and Error Reporting

This sample shows how to use Error Reporting to route suspended message to an Orchestration in Biztalk 2006. It includes two Orchestrations, one intended to fail on the Receive Port and one on the Send Port. Both a manual installation and MSI installation is available.

Get more information from the original blog post on this topic:https://www.biztalkgurus.com/biztalk_server/biztalk_blogs/b/biztalk/archive/2005/08/02/suspended-message-routing-and-reporting-in-biztalk-server-2006.aspx

Suspended Message Routing and Reporting in Biztalk Server 2006

Suspended message routing is arguably the greatest and most anticipated new feature in Biztalk 2006. 


Suspended message routing gives you the ability to subscribe to messages that fail inside the messaging system.  Matt Hall going into detail on how to generate Error Reports for Suspended Message Routing and what properties you have available to subscribe to.  In addition, the documentation that ships with Beta 1 cover this is great detail.


The ability to react to errors in the messaging system goes much deeper then just “No Matching Subscription” errors.  You now have the ability to easily handle all messaging errors that occur inside a pipeline, an adapter, and even maps.  That’s right, no more looking into the great abyss for Send and Receive Port mapping errors.


In a post about a year ago, I point out that Delivery Notification in Biztalk 2004 did not work when the map fails on the Send Port.  Not any more!  Now, Delivery Notification supports Send Port mapping exceptions as well as adapter exceptions.


That brings up another point.  You now have Error Reporting, native support for First-in First-out on EVERY Send Adapter, and the traditional Delivery Notification to accomplish FIFO in Biztalk 2006.  With all these options available it could be very easy to go overboard and needlessly bog down a process with too many bells and whistles.  Off hand, I can not see a need in using both Delivery Notification and FIFO on a Send Adapter together in a single process.


I have put together a small sample that works with Error Reporting and Suspended Message Routing.  It includes two Orchestrations, one intended to fail on the Receive Port and one on the Send Port.  In addition, I have included a map that throws an Exception.  In the suspended message routing Orchestration, I subscribe to the ErrorReport.FailureCode exists property. 


Download: Biztalk 2006 Suspended Message Routing Sample


The download includes a binding file with source code as well as a packaged MSI.  This should only be run on Biztalk 2006.

How To Prepend to the SourceFileName in BizTalk Sample

Biztalk 2004 provides a variety of built in macros for dynamically naming files.  A full list of macros can be found in the help guide or here. 



Recently, I have been looking at SourceFileName.  I have posted a sample in the past that covers how to name output files inside your Orchestration using the %SourceFileName% macro.  In that sample, I completely override the File.ReceivedFileName property with a new value.  The File.ReceivedFileName property is the data source for the %SourceFileName% macro.



What if I wanted to append or prepend data to the original file name?  When using the File Receive Adapter, the File.ReceivedFileName property looks like this: “c:\somepath\FileName.xml”. 



If you prepend or appended text to this, you will get “PrePend_c:\somepath\FileName.xml” or “c:\somepath\FileName.xml_Append”. 



When the %SourceFileName% macro runs, it looks for the last “\” and truncates the beginning part of the filename.  So, in the Prepend case, the prepended text is completely lost.



How can I prepend or append text to the filename?  Easy, just use a simple static helper class to prep the filename.  The method to prepend text would look like this:



public static string PrePendText(string sReceivedFileName, string sPreppendText)


{


 int nLastIndex = sReceivedFileName.LastIndexOf(@”\”);


 return sPreppendText + sReceivedFileName.Substring(nLastIndex+1);


}



I have put together a sample with three methods; one to prepend text, one to append text, and one to append text and change the file extension. 



Download: Prepend and Append Text to Filename Sample



Setup is easy.  Just deploy the Orchestration and do not forget to GAC the Helper class.

Prepend and Append Text to SourceFileName Macro

This sample shows how use the %SourceFileName% macro to append or prepend text to the original file name of the file received by the file adapter. This sample includes a helper class with three methods to help with string manipulation of the file name.

This uses an Orchestration to set the Received File Name Message Context Property that the SourceFileName Macro uses. 

This sample will work for BizTalk 2004 and BizTalk 2006.

Get more information from the original blog post on this topic:https://www.biztalkgurus.com/biztalk_server/biztalk_blogs/b/biztalk/archive/2005/08/01/how-to-prepend-to-the-sourcefilename-in-biztalk-sample.aspx