BALTIMORE SharePoint Users Group Agenda 6:00pm – 6:45pm Networking Time

1. BALTIMORE SharePoint • Users Group • Agenda • 6:00pm – 6:45pm             Networking Time • 6:45pm – 7:00pm             Group Overview/ Announcements • 7:00pm – 8:30pm             Eric Harlan – Federated Search • 8:30pm – 8:45pm             Closing Remarks • Drinks? • We cant make it happen with out our sponsors: • UMBC Training Center

2. News • Ski Day – Baltimore (Next Wednesday! Feb 25th) • SharePoint Ski Day – Seattle (Next Saturday! Feb 28th) • SharePoint Saturday – Baltimore (July/August) • SharePoint Saturday – NYC (Saturday Feb 21st) • SharePoint Saturday – DC (May 2nd)

3. Infrastructure Update • Infrastructure Update for WSS 3.0 (KB951695) • Applies to ALL Windows SharePoint Services 3.0 (MOSS, MSS, MSSX, project server etc) • Infrastructure Update for Microsoft Office Servers (KB951297) • Applies to: MOSS 07, MOPS 07, MSS 08, MSSX 08 • Infrastructure Update for Microsoft Office Project 2007 (KB951547) • Applies to: Project Professional 07 • Easier upgrades in the future for MOSS overall (office 14)

4. Infrastructure Update Known Issues • Microsoft GroupBoard 2007 • More info on technet but basically uninstall groupboard, install the update, reinstall GroupBoard • Error: Could not find stored procedure ‘dbo.proc_GetDataBaseInformation’ • Just ignore it • Content Deployment Jobs disappear • It’s a user interface issue, your jobs are still there, simply click on one of the columns to sort the list and they will reappear. Just need to do this once. • Blog ‘Email a Post’ • Wont open a new email, there is a KB article on how to fix this. • Single Server Farm, automatic updates will be applied, multi-server farm automatic updates will not be applied.

5. Federated Search • Federated search allows users to query multiple environmental, internal or external sources and display the results back on a single search results page via web parts with out having to index that source. • There is no “API” the api, is XML

6. Where can we use Federated Search?

7. Where can we use Federated Search? • Searching different Farms in the same company in different geographies.

8. Where can we use Federated Search? • Searching different Farms in the same company in different geographies. • Tech searches on topics on other sites

9. Where can we use Federated Search? • Searching different Farms in the same company in different geographies. • Tech searches on topics on other sites • RSS feeds specific to a topic from news sites

10. Where can we use Federated Search? • Searching different Farms in the same company in different geographies. • Tech searches on topics on other sites • RSS feeds specific to a topic from news sites • Searching internal systems that are OpenSearch Compliant but cant be indexed (or shouldn’t be) • Etc…

11. Will’s and Will Not’s • Federation in Search Server will • -Send a query to other search engines or applications • -Format and render the results • -Work out of the box or with minimal effort with many existing search engines and applications • Federation in Search Server will not • -Interweave result sets from other sources into a single result set (web parts) • -Relevance rank results from other search engines or applications

12. Bull in the China Shop

13. Bull in the China Shop • Advantages • Disadvantages • ·          Security-trimming is preserved for the local farm and for remote farms if Kerberos authentication is used.

14. Make the Connection

15. Make the Connection • Required Functionality for a Federated Connector • Based on the requirements for an OpenSearch location, as described earlier, the federated connector must be able to do the following: • Provide a Web page or Web service for the search server’s query request, sent as a parameterized URL. • Retrieve the search query from the request’s URL parameters. • Submit the query to the repository’s search engine in the appropriate format. • Convert the repository’s search results into a structured XML format. • Return the search results XML in the response to the search server. • Out of the box Connectors can be found (News, Media, Blogs, Info) http://www.microsoft.com/enterprisesearch/connectors/federated.aspx

16. Find the Fresh Powder

17. Find the Fresh Powder • Federated Locations • A federated location defines the federated search connection to the external content repository, and is composed of the following: • Location type • Query and More Results link templates • Triggers • Display information • Restrictions • Authentication and credentials information • Location Type • Search Server 2008 supports the following types of federated locations: • -Local Search Index   SharePoint sites local to the search server. • -OpenSearch 1.0/1.1   The RSS feed for any remote search server's results page, or any searchable feed that supports the OpenSearch standard, and returns search results in structured XML format (for example, RSS or Atom results).

18. Hit the Double Blacks

19. Hit the Double Blacks • Federated Results Caching • Results for a query are cached for 60 seconds • Synchronous/Asynchronous Rendering • Top Federated Result Web Part is always sync • Federated Results Web Part can be either • Slow locations should always be async and in a Federated Results Web Part (Timeout is 90s) • Extending the Federation Web Parts • Both can be inherited • Paging Federated Results • Support for “&StartAt=” in Query Template URL

20. Demo • Federated Search

21. Demo Steps: • Show Old search Settings (show that its the same old thing for comfort) • Show Search Administration (unified dashboard) • Note Active Crawls (which crawls are active) • Recently Completed Crawls (duration, errors etc) • Go to Federated Locations • Show two methods (new locations, import) • Go to "Online Gallery" on federated locations page • Download Wikipedia FLD (right click download) • Go to Import location and browse to the wikipedia.fld file • Click Done • Go to search center page • Run a query to get to results page • Edit the page (site actions, edit page) • Add a web part (top federated search results) • Edit the web part and select the "Wikipedia" from the drop down) • Apply and publish • Mention top result from Wikipedia now present • CUSTOM LOCATION (mention it needs open search source I.e. XML, RSS, etc • Go to federated Locations • Click new location • Add Title, Name, Description etc • Leave Author and version blank • Select "Prefix" with the term “Microsoft" • Choose OpenSearch 1.0/1.1 for the location type • Go to Technet do a search, get RSS feed for that result, copy URL • Enter in the RSS url take out the variable passed and replace it with {searchTerms} • Do the same for the "More Link" but link it to the full results set page • Leave rest blank but talk to security and searching against secure areas. • Go back to search results page, edit top federated results web part add Google as first and Wikipedia as second, change results shown to 3

22. THANK YOU! • BALTIMORE SharePoint • Users Group • Next meeting: March 19th • www.baltimoresug.org • Drinks anyone?