Searching Business Data With Moss 2007 Enterprise Search 2


Published on

Slides from my talk on Searching Business Data with Enterprise Search. Given at Tulsa School of Dev 2008 and Tulsa TechFest 2007.

Published in: Technology, Design
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Maybe mention BDC List Web Part, etc.
  • Security issues can be troubleshot via Event Log and SharePoint logs.
  • UniqueId can be faked with proper queries.
  • Give basic tips for setting up a search and recommend starting with a minimal set of records.
  • Demo the use of BDC Tools, the MetaData Model and the Import Process
  • Demo setting up a content source and start a crawl.
  • Map a Property for the column Size and recrawl.
  • Demo the use of BDC Tools, the MetaData Model and the Import Process
  • Searching Business Data With Moss 2007 Enterprise Search 2

    1. 1. Searching Business Data with MOSS 2007 Enterprise Search<br />Presenter: Corey Roth<br />Enterprise Consultant<br />Stonebridge<br />Blog:<br />
    2. 2. Corey Roth<br />Consultant for Stonebridge<br />Worked in Consumer Electronics, Travel, Advertising, and Energy industries<br />Currently doing MOSS development specializing in Enterprise Search<br />OSU Graduate<br />Microsoft Award for Customer Excellence (ACE) Winner<br />E-mail:<br />Blog: (mirrored on<br />
    3. 3. Why Enterprise Search?<br />Allows indexing and searching of business data from multiple systems with little or no code.<br />Through Business Data Catalog (BDC) can index non-SharePoint applications<br />BDC can index data in SQL Server, Web Services, and other database providers<br />Can also be used to index Active Directory (People Search)<br />Designed to search text – Other data types can work but there are limitations<br />
    4. 4. Business Data Catalog<br />Abstraction Layer between MOSS and Business Applications<br />Provides support for displaying and searching data from databases and web services<br />Designed for Readonly access<br />Inserts/Updates/Deletes are possible but there are limitations<br />Not a replacement for a DAL<br />
    5. 5. Security<br />Security is required for the following accounts<br />Domain Accounts are recommended<br />Content Access – Defined in Search Settings; Needs read access to database table; Needs BDC Execute permission<br />Shared Service Provider Account – Used for profile pages; Needs BDC Execute/Select in Clients permission<br />Administrators – Specify an account with full control or you will run into issues<br />End Users – Need BDC Execute/Select in Clients permission<br />
    6. 6. Steps<br />Create MetaData Model for Business Application<br />Import MetaData<br />Create Content Source<br />Crawl Business Data<br />Create Managed Properties and map them to Crawled Properties<br />Crawl Business Data (Again)<br />Create Search Scope<br />
    7. 7. Step 1 - BDC Metadata Model<br />XML file which maps entities from databases or web services to the BDC<br />Defines default actions when a search result is clicked<br />Requires a unique id in the data source*<br />Three types of methods<br />Finder -Returns all records from a table or view<br />SpecificFinder - Returns details for a specific record<br />IDEnumerator- Used by Enterprise Search to determine rows to index<br />
    8. 8. BDC Metadata Model<br />Version Number – Increment every time you import during development<br />LobSystemInstance element<br />AuthenticationMode – RevertToSelf<br />AccessControlList element – Specifies Security (can also do through SSP)<br />Action element – Sets a default action (sets a URL to go for that item)<br />
    9. 9. BDC Tools<br />Tools can be useful for generating XML MetaData schema<br />Office SharePoint Server SDK<br />BDC Meta Man<br />MOSS BDC Design Studio<br />Many Others Available Now<br />
    10. 10. Start Small<br />Crawls over entire tables can take a long time<br />Avoid crawling full tables when testing<br />Modify Schema file to crawl partial tables<br />i.e.: SELECT TOP 50…<br />
    11. 11. Demo<br />
    12. 12. Step 3 - Content Sources<br />Content Sources can map to one or more BDC Application Definition<br />Used to start and stop content crawls<br />Typically map one application definition to one content source<br />
    13. 13. Step 4 - Crawling<br />Uses IDEnumerator method to get list of rows to import.<br />Calls SpecificFinder method for each Id returned by IDEnumerator<br />Stores columns from table or web service as crawled properties<br />
    14. 14. Demo<br />
    15. 15. Step 5 - Managed Properties<br />Out of the box, a search will do a full-text search on all text properties<br />Can be used to create advanced search pages<br />After first crawl, columns are available as crawled properties<br />Map crawled properties to managed properties for more specific searches<br />Non-text types are not indexed by default<br />
    16. 16. Demo<br />
    17. 17. Step 7 - Scopes<br />Scopes are used to specify different types of content to search (i.e.: Products, People, Sales, etc.)<br />Scopes can be defined by Content Source or Managed Property<br />Typically map to a Content Source to make it easier to test application definitions<br />Can be displayed in drop down lists in conjunction with the SearchBox web part<br />
    18. 18. Search Center<br />Out of the box site and web parts for searching and displaying results<br />Can be created using the Site Settings menu on the root web site by enabled certain features<br />Supports keyword search only (no wildcard)<br />For wildcard search consider a Search Center Replacement such as Ontolica or write your own search page<br />
    19. 19. Keyword Syntax<br />Used to search by Managed Properties<br />Can specify Scopes (Scope:”MyScope”)<br />Can be passed via URL to CoreResultsWebPart (k Query String parameter)<br />AND implied between each keyword (i.e.: Color:”Red” Size:”M” is the same Color=“Red” AND Size=“M”)<br />OR implied when multiple keywords of the same managed property used (i.e.: Color:”Red” Color:”Blue” translates to Color=“Red” OR Color=“Blue”)<br />
    20. 20. Search CenterFeatures Required<br />Site Collection Features<br />Office SharePoint Server Enterprise Site Collection features – BDC Web Parts<br />Office SharePoint Server Search Web Parts – Enterprise Search Web Parts<br />Office SharePoint Server Publishing Infrastructure – Not necessarily required unless you want to activate the feature below<br />Site Features<br />Office SharePoint Server Publishing – Adds Create Site menu item and publishing features (not required but convenient)<br />
    21. 21. Search CenterWeb Parts<br />SearchBox<br />CoreResultsWebPart<br />BestBets<br />Paging<br />AdvancedSearch<br />
    22. 22. Search CenterCustomization<br />CoreResultsWebPart displays search results<br />Columns property – XML specifying Managed Properties<br />XSL – Transform the HTML output of the search results<br />Column names are specified in lower case in XSL (i.e.: Color will be color)<br />
    23. 23. Deployment and Migration<br />MOSS has no built in way to move Enterprise Search settings!<br />SharePoint Shared Services Provider Creation (SSSPPC) can help (see blog for more info)<br />
    24. 24. References<br />Dot Net Mafia Blog<br /><br />Office SharePoint Server SDK<br /><br />Faceted Search Web Parts<br /><br />SharePoint Shared Services Provider Creation<br /><br />BDC Meta Man<br /><br />Ontolica<br /><br />
    25. 25. Questions?<br />
    26. 26. Thanks<br />Corey Roth<br /><br /><br />