October 25, 2014
Hot Topics:
RSS RSS feed Download our iPhone app

Collaborating with the BizTalk 2006 R2 SharePoint Adapter

  • October 8, 2007
  • By Jeffrey Juday
  • Send Email »
  • More Articles »

Of the options above, "Yes" and "Optional" require support from the "Templates Document Library" and the "Templates Namespace Column" to associate the file with the appropriate template. Refer to the additional information section for more details.

Further down the properties dialog is the "Windows SharePoint Services Integration" section. The dialog appears below:

In this section, you assign the property values in the Document Library. The "Column 0N" contains the name of the property as it appears in the SharePoint Document Library property label and the "..Value" column contains the value to place in the column.

You may have noticed that the column values and in the filename property contain "%XPATH...". For example, the full filename property value appears below:

%XPATH=//ns0:BizTalkContext[1]/ns0:MessageSource%
   %XPATH=//ns0:FailedMessageDocID%.xml

Macro values such as %XPATH allow you to extract information from the file you are storing or from the BizTalk context. In the XPATH example above, the Adapter is programmed to use the value of the MessageSource element and the FailedMessageDocID element to name the file. Writing XPATH statements is beyond the scope of this article, but you'll find a helpful article here http://msdn.microsoft.com/msdnmag/issues/0700/xml/. When using XPATH, you also need to fill in the Namespace Alias if you're using namespace aliases in the XPath statement. Finally, all macros must be enclosed in the "%" sign.

There are some other useful insights to keep in mind. I wanted to highlight them because they should be foremost in your mind as you apply what you've learned.

It is worth noting that work for the project this article is based on was done using InfoPath 2003. I was, however, using SharePoint 2007 and BizTalk 2006 R2, so behavior may vary with other product versions. Although I could not get Document Library properties created by a published InfoPath Template file to work properly, your properties can be created from within the SharePoint Document library. You should also note that versioning, approvals, and check-in/out are not supported by the Adapter.

I mentioned earlier that you could use the Adapter to update Lists and Wikis. Updating these other repositories is covered in the BizTalk documentation. Also, there is a great four-part Webcast on the SharePoint BizTalk adapter (http://blogs.msdn.com/ahamza/).

Conclusion

SharePoint has become a major collaboration platform. Microsoft has made it part of many of their major products. In BizTalk, the SharePoint Adapter and an accompanying Web Service perform all the SharePoint integration duties. The Adapter mostly works with Document and Form Libraries. It is especially adept with XML and InfoPath.

Download the Code

You can download the source code for this article here.

Acknowledgements

Special thanks to Jeff Hunter and Corné van Dyk, my company's SharePoint experts, for their expertise and assistance with this article.

About the Author

Jeffrey Juday is a software developer with Crowe Chizek in South Bend, Indiana. He has been developing software with Microsoft tools for more than 12 years in a variety of industries. Jeff currently builds solutions using BizTalk 2004, ASP.NET, SharePoint, and SQL Server 2000. You can reach Jeff at jjuday@crowechizek.com.





Page 3 of 3



Comment and Contribute

 


(Maximum characters: 1200). You have characters left.

 

 


Sitemap | Contact Us

Rocket Fuel