Biz Talk Integration with CRM : How to Videos by peter kelcey

Post by Peter Kelsey, MSDN

I recently participated with our MCS Canada team on a large BizTalk 2009 and CRM 4.0 integration project. I gained a ton of experience about CRM integration from that project and I thought I’d speak about it at our semi-annual TechReady internal conference. Not long before TechReady though, we release CRM 2011 and I realized that speaking about BizTalk 2009 and CRM 4.0 was about as relevant as speaking about Windows 98 and Trumpet Winsock implementations (I was reading a Slashdot article this week about the Trumpet Winsock creator… so that’s where the reference came from…). I hastily decided to refocus the presentation on CRM 2011 and BizTalk 2010. That meant that I had to quickly figure out exactly what the integration story was between these two products. After a bunch of trial and error and some helpful conversations with folks from the CRM 2011 team, I figure out the options. It turns out that you have TWO options for integrating BizTalk 2010 and CRM 2011.  Yes indeed, you have two different methods to choose from when integrating these two products! I ended up having a fairly relevant and well received presentation to deliver. From that internal session, I’ve repurposed my content into a publicly ready format and created a shorter walk through video that explains the two options that you have. Instead of trying to write a lengthy blog post about how to do that, I’ve just filmed a walkthrough of the process.  (I found that these video walkthroughs were highly successful when I did them for the BizTalk ESB, so I thought I’d do them again here for CRM) Also, I’ve included the source code project that I use in the video so that you can get a jumpstart on your process.

All in all, I found the process to be a very simple one once I figure out a few basic concepts. Hopefully, this blog post will help you figure out those concepts more quickly than I did. Once you’ve got a grip on those, then I believe you’ll find this integration process to be a very easy one.  As with most of these blog videos that I do, I created this after midnight when the house was quite  so if you find some issues or bloopers, let me know and I’ll correct them.

Below is an overview of the components, tools and services at play in to the process. In the video, I’ll walk you through this diagram in more depth before showing you the actual project I built.  In this diagram, you can see that there is data flowing from BizTalk out to the CRM 2011 cloud service as well as data flowing from CRM 2011 Online back through the firewall to BizTalk on-premise. In this first video, I focus on the BizTalk to CRM 2011 Online option. In a day or two, I’ll post a second video that shows the CRM 2011 Online event notification being sent back to an BizTalk on-premise installation. (it’s a cool one…)

This is quite a long video (>45 minutes) so I had to split it into a multipart zip file in order to get it to fit into my SkyDrive folder.

You can get:

1. Part one at http://cid-04bc12b1f7b2979a.office.live.com/self.aspx/BlogVideos/CRMBTS%5E_Video%5E_Multi.zip
2. Part two at http://cid-04bc12b1f7b2979a.office.live.com/self.aspx/BlogVideos/CRMBTS%5E_Video%5E_Multi.z01
3. The source project and test file here http://cid-04bc12b1f7b2979a.office.live.com/self.aspx/BlogVideos/BizTalkToCRMOnline.zip

You’ll need to download both parts of the zip file and then use WinZip to extract them.

Read more ...

Installing and Configuring Sharepoint Adapter for BizTalk

You do need to install SharePoint Foundation or SharePoint Services 3.0 SP2. See this post and Sandro's post for starters. According todocumentation (BizTalk installation manual):

"You do not need to install WSS if you do not also plan to install the WSS adapter. However, if you are installing WSS, you must do it before continuing with the rest of the BizTalk Server prerequisites."

BizTalk Server 2010 supports these two versions of WSS:

• SharePoint Foundation 2010
• Windows SharePoint Services 3.0 with SP2

Installing and configuring Windows SharePoint Services consists of the following procedures:

• Install Windows SharePoint Services
• Configure Windows SharePoint Services
• Extend the Default Web Site as a virtual server

Installation

BIZTALK 2010  INSTALLATION  AND CONFIGURATION  - SHAREPOINT SERVICES/ADAPTERS

Windows SharePoint Services is a collection of services for Windows Server which enable you to share information, collaborate with other users on documents, and create lists and Web part pages. For information and procedures on installing Windows SharePoint Services, see Appendix A.

Note

You do not need to install WSS if you do not also plan to install the WSS adapter. However, if you are installing WSS, you must do it before continuing with the rest of the BizTalk Server prerequisites.

BizTalk Server 2010 supports these two versions of WSS:

• SharePoint Foundation 2010
• Windows SharePoint Services 3.0 with SP2

Installing and configuring Windows SharePoint Services consists of the following procedures:

• Install Windows SharePoint Services
• Configure Windows SharePoint Services
• Extend the Default Web Site as a virtual server

I chose to install WSS 3.0 with SP2 for no particular reason.

Install Windows SharePoint Services 3.0 with SP2

In the following procedure you install Windows SharePoint Services 3.0.

1. Windows SharePoint Services 3.0 requires Microsoft .NET Framework 3.0, which must be installed before beginning installation of Windows SharePoint Services 3.0. The .NET Framework is available for download at http://go.microsoft.com/fwlink/?linkid=75053.
2. Browse to http://www.microsoft.com/downloads/en/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en. Download the installation package to a location on your hard disk.
3. Locate the package you just downloaded (SharePoint.exe), and then double-click the package to start the setup.
4. On the End User License Agreement screen, select I accept the terms in the License Agreement. On this screen and several others that follow, the setup wizard will automatically move to the next screen when you have made your selection.
   
5. Under Type of installation, choose the Advanced button.
   
6. On the Server Type tab, select Web Front End, then click Install Now.
   
7. Ensure the configuration checkbox is clicked and click the “Close” button.
   

Configure Windows SharePoint Services

1. On the Welcome screen, click “Next”
   
2. In the Warning screen, Click “Yes”
   
3. On the Server Farm screen, select the option “No, I want to create a new server farm” and click “Next”
   
4. On the Configuration Database screen, provide a Database server name and credentials and click “Next”.
   
5. On the Configure SharePoint Central Administration WEB Application screen, use the Default values and click “Next”.
   
6. On the Completing the SharePoint Products and Tecnologies Configuration Wizard screen, leave the default values and click “Next”
   
   
7. On the Configuration Successfull screen, click “Finish”.
   

Extend the Default Web Site as a virtual server

1. Open SharePoint Central Administration, and click “Application Management”
   
2. On the Application Management Tab, click on “Create or extend Web application”
   
3. At this point, normally I extend an existing Web application, this time I chose to follow Kent Wearesuggestion and create a new one using the port 90, so click on “Create a new Web application”
   
4. I have decided to create my Web Application in a new IIS Web site called “SharePoint – 90”. I have done this so that I don’t overwrite or break anything that may be living in my Default Web Site. I also have modified the port to be “90” which means any requests to my WSS Site will need to have “:90” in the url. If you do this then when you post or retrieve documents to/from SharePoint from BizTalk that you will need to include this port number in your Receive Location/Send Port configuration.
1. On IIS Web Site options, select “Create a new IIS web Site”, set a description and change Port to 90
2. On Security Configuration options, set Authentication provider as NTLM
   
3. On Load Balanced URL options, check if the URL as “:90”
4. On Application Pool options, create a new application pool “Sharepoint – 90”
   
5. On Database Name and Authentication options, appended “99” onto the Database Name that will be used for storing Content and chose “Windows authentication” option
6. Click “Ok”
5. You have now created the “shell” for this Web Application, but you still don’t have any content in this Web Application. Click on the “Create Site Collection” link. Remember to issue an “iisreset /noforce” command to complete the Web Application creation process.
1. Open cmd and execute “iisreset/noforce”
2. Click “Create Site Collection”
   
6. On Title and Description option, give your Site a Title, Description(if so desired), on the Web Site Address option create a URL, and in the Template Selection option select “Team Site” (Team Sites are generally a place where team members can collaborate by publishing documents, but other features exist such as Team Calendars, surveys, links etc).
   
7. On Primary and Secondary Site Collection Administrator option set an user. And click “Ok” to finish.
   
8. Team site has now been created.
   

source : sandro perira , MSDN

Read more ...