Collaborating with the BizTalk 2006 R2 SharePoint Adapter
As you can see, the Web Service portion of the SharePoint adapter works through a separate IIS site. Extending a Web Application is an alternate way to support multiple types of access to a SharePoint Web Application. The Extend Web Application is on the Application Management menu. Here are the Extend Web Application options.
I recommend using different port than the default Web Application. I would advise using a consistent port number if you have multiple SharePoint installations.
Once the SharePoint Web Application is extended, you can configure the Web Service portion of the BizTalk Adapter. After launching the BizTalk Configuration application, select the "Custom" configuration option. The Dialog below will appear.
Select the SharePoint Services Adapter Web Site you used when you Extended the Web Application.
Once you've configured the Adapter, you need to add the Account the Web Service uses to the "SharePoint Enabled Hosts" group (if you took the default Windows Group name). Instead of using a domain account, I like to use two local accounts: one local to the BizTalk server and one local to the SharePoint server. As long as the accounts have the same name and password, they'll work a lot like a Domain Account, but with a smaller security footprint.
At this point, you're ready to use the BizTalk SharePoint Adapter. The next section will explain how you program it.
Programming the Adapter
The Send port options are a superset of the Receive Location programming options, so I'll focus on Send port programming.
The Send port properties dialog appears below.
Most of these options are straightforward or well documented. "Microsoft Office Integration" and "Namespace Aliases" require further explanation.
As stated earlier, the SharePoint Adapter writes files primarily to SharePoint Document Libraries. Document Libraries may contain files of different formats, the same format but different templates, or the same format and same templates. So, the SharePoint adapter must accommodate the varying number of requirements. When to use each requirement is outlined in the following list.
- Use "No" if the Document Library contains no template or a mix of file types.
- Use "Optional" if you want the adapter to associate the file to a template if the appropriate template exists and write the file without error if an appropriate template does not exist.
- Use "Orchestration" if you're utilizing a Dynamic Port. You can find more information on dynamic ports in the BizTalk documentation. Further detail on this option is beyond the scope of this article.
- Use "Yes" if the template exists in another Document library.
- Use "Yes (InfoPath..." if you're integrating with a Form Library.
Page 2 of 3