Monday 14 May 2012

SharePoint Installation Process Part 5


Now with all the software’s installed and configured, let us now create and setup Content SSA and Query SSA. Content SSA crawls the content and feed it into FAST Search back-end while Query SSA provides the query results from the content that is crawled by Content SSA.
Create and setup Content SSA
  1. Open SharePoint 2010 Central Administration Home Page, under Application Management and click Manage Service ApplicationsImage 59
  2. In Manage Service Applications page, click New –> Search Service ApplicationsImage 60
  3. In Create New Search Service Application page, fill in the details (here’s what I filled)
    1. Name: FAST Content SSA
    2. FAST Service Application, select FAST Search Connector
    3. Search Service Account, selected the default value
    4. Application Pool for Search Admin Web Service, entered FAST_Content_Admin_App_Pool
      I also decided to let the AppPool run under dotnetscraps\svcaccnt service account.
    5. Content Distributors and Content Collection Name, you can get the value from install_info.txt from D:\FASTSearchon the FAST Search Server (type %fastsearch% to jump to the FAST Search installation folder)e.g.: Content Distributor: WIN-FS.dotnetscraps.com:13391
      Content Collection Name: sp
    6. Click OKImage 61
      Image 62
    7. When finished, you will get a confirmation that a new Content SSA is created and is added in the list of Service Applications –> click OKImage 63
  4. Once you have created Content SSA, you must configure the communication channel to feed content to FAST Search. This communication channel is SSL enabled and is the must.
    1. You will need to copy securefastsearchconnector.ps1 from %fastsearch%\installer\scripts andFASTSearchCert.pfx from %fastsearch%\data\data_security\cert on to the SharePoint Server (WIN-SP)
    2. On the SharePoint Server, Start –> All Programs –> Microsoft SharePoint 2010 Products –> right click onSharePoint 2010 Management Shell and Run as administrator
    3. Navigate to the folder where you copied the above two files
    4. type the command.\SecureFASTSearchConnector.ps1 –certPath “path_of_certificate\certificate_name.pfx” –ssaName “name_of_content_SSA” –username “domain\username”NOTE: if you are not sure about the domain\username, check the account under which SharePoint Server Search 14 (OSearch 14) service is running.
      When prompted for password, enter the password you entered during the FAST Search post-setup configuration i.e. in step 6 in the previous post
      Image 64
  5. Now that we have setup Content SSA, let us verify FAST Search by adding a content source and performing a full crawl.
    1. Open SharePoint 2010 Central Administration Home Page, under Application Management and click Manage Service Applications
    2. click FAST Content SSA (managed search service application you created)
    3. On Search Administration Page, in the Crawling section, click Content SourcesImage 65
    4. click New Content SourceImage 66
    5. Fill in the details as shown belowName: fastdemo Content Source
      Content Source Type: select SharePoint Sites (since we would like to search documents that’s in SharePoint). We can add multiple Content Source and different type of content source as needed.
      Start Addresses: type the URL http://win-sp (is the link for my Team Site)
      Crawl Setting: Everything that’s under that URL (http://win-sp)
      Crawl Schedule: None (we will schedule it later)
      Content Source Priority: Normal
      Start Full Crawl: (unselected) as I will do that manuallyImage 67
      Image 68
    6. Click OK
  6. On the Manage Content Source, click beside fastdemo Content Source (the content source we created) –> click Start Full CrawlImage 69
  7. On the FAST Search, open the Microsoft FAST Search Server 2010 for SharePoint shell and type Get-FASTSearchContentCollection, to show all the content collections i.e. documents crawled and feed.Image 70
So, the documents have been crawled and now we need to add Query capability. Let’s keep it for a bit later.

No comments:

Post a Comment