High Adventure with BDC and Enterprise Search

The other day I was looking for a refresher on the BDC and Enterprise Search as integration with SAP is now on the horizon. Microsoft has an awesome set of tutorials but they’re sadly out of date due to dependence on the Adventure Works 2000 database. Below I outline how to get everything up and going with the Adventure Works 2005 & 2008 database. It’s a great tutorial and provides an excellent framework for prototyping and demonstrations to customers. Highlights mainly include:

1. Creating and importing BDC ADF
2. Setting permissions on the BDC Application & Entities
3. Crawling your BDC Application in Enterprise Search
4. Surfacing search results via mapped managed properties
5. Configuring end user Search Center experience
6. Bonus: Configuring People Search and MySites


Pre-Req Installations

1. Download and install respective Adventure Works Database from CodePlex.

2. Download and install “SharePoint Server 2007 SDK: Software Development Kit

  • Go to: C:\Program Files (x86)\2007 Office System Developer Resources\Tools\BDC Definition Editor
  • Read the readme and run the setup.exe to install the BDC ADF editor
  • WARNING – Installs SQL Server 2005 Express – UG!


Complete Walkthroughs

1. Adventure Works Sample
– Use the ADF I’ve defined for both 2005 and 2008 as I’ve corrected all of the BDC queries and entity names
– As you create or utilize the ADF I’ve created, be sure to test them in the BDC editor tool
– If you use the ADF I created, change SQL Server name on adfs before importing.

2. Walkthrough: Configuring Search for the AdventureWorks Business Data Application Sample
– PERMISSIONS!!: When crawling, permission has to be given to the crawl account in three different places:

  • the BDC itself
  • the Application Definition you are crawling
  • the individual entities inside the Application Definition.

– Use “Copy all permissions to descendants” to avoid repitious permission enablement
– MYSITES location: If you get the “Error in PortalCrawl Web Service” when crawling the user profiles –

  • Ensure your mysite site collection is NOT located at the root of the SSP web app. It should be in it’s own dedicated web app.
  • Did you know: Each MySite is it’s own site collection?
  • 10 Best Practices for MySites
  • Architecting MySites

3. Walkthrough: Add a Tab and Custom Search Page with Enterprise Search Web Parts to the Search Center
– If you get “Property doesn’t exist or is used in a manner inconsistent with schema settings.”, do the following:

  • Ensure the “Selected Columns” xml matches the column names.
  • Recall that we mapped only three Managed Properties: ProductName, ProductNumber & ProductID

Therefore you can only utilize these three in your selected columns.

4. Hook in Wildcard People Search


~ by spninjablog on November 16, 2009.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: