Close

BLOGS

Setting up FAST Search in SharePoint 2010 Farm

Microsoft FAST Search Server 2010 for SharePoint includes all the search features and integration capabilities of SharePoint Server 2010 and adds deep platform flexibility and scale and enhanced content processing capabilities.

As part of this process, you will also download the installation package, enable Windows PowerShell scripts to run and set up permissions for Microsoft SQL Server.

Download the installation package

Log in to MSDN Subscriber Downloads, expand the Servers menu, and then click FAST Search Server 2010 to download FAST Search Server 2010 for SharePoint. The installation package contains a self-extracting exe file that will open a Start page (splash.hta) and extract the installation files to the following folder:

\Program Files (x86)\MSECache\FastSearchServer2010\

Open the FAST Search Server 2010 for SharePoint Start page When you download the installation package, the FAST Search Server 2010 for SharePoint Start page opens automatically. The Start page provides links to product documentation and to the installation wizards.

However, after any restarts of the server during the installation process, the Start page does not open automatically. Double-click the splash.hta to reopen the FAST Search Server 2010 for SharePoint Start page.


Install prerequisites

The Prerequisite Installer checks your server for required components and updates, and then downloads and installs the required components and updates if they are not already present on the system. Which prerequisites are required depends on your operating system.

  1. On the FAST Search Server 2010 for SharePoint Start page, click Install software prerequisites.
  2. On the Welcome to the FAST Search for SharePoint prerequisite installer page, click Next.
  3. On the License page, verify that you accept the license terms and then click Next.
  4. On the Installation Complete page, click Finish.
  5. Restart the server.

 

Enable Windows PowerShell scripts to run

After the server restart in the previous procedure, change the policy for running Windows PowerShell scripts remotely (execution policy). The post-setup configuration wizard that you will run later must be able to run scripts during configuration.

To enable the scripts to run:

  1. From the Start menu, search for Windows PowerShell.
  2. Right-click the Windows PowerShell icon (do not use the one with x86) and select Run as administrator.
  3. At the command prompt, type the following command to enable scripts to run:

Set-ExecutionPolicy RemoteSigned

  1. Answer Yes if you are asked whether you want to change the policy.

Install FAST Search Server 2010 for SharePoint

This procedure describes how to install FAST Search Server 2010 for SharePoint by running the installation wizard. Before you run the installation wizard, the Prerequisite Installer must be completed. To install FAST Search Server 2010 for SharePoint

  1. Go to \Program Files (x86)\MSECache\FASTSearchServer2010 and double-click the splash.hta to reopen the Start page after the server restart.
  2. On the FAST Search Server 2010 for SharePoint Start page, click Install FAST Search Server 2010 for SharePoint.
  3. On the Welcome page, click Next.
  4. On the License Terms page, accept the license and then click Next.
  5. On the Destination Folder page, select the folder where you want to install FAST Search Server 2010 for SharePoint. Click Next.
  6. On the Ready to install page, click Install.
  7. On the page that says that the wizard is completed, click Finish.

 

Install updates

After you have run the installation wizard, make sure that the product is up to date:

  1. On the FAST Search Server 2010 for SharePoint Start page, click Visit Windows update.
  2. Download and install all relevant updates.
  3. For a multiple server deployment, repeat the procedure for all servers that will run FAST Search Server 2010 for SharePoint.

 

Set up permissions for Microsoft SQL Server

You must install SQL Server 2008 before you install FAST Search Server 2010 for SharePoint. When you run the post-setup configuration wizard to configure the server(s), FAST Search Server 2010 for SharePoint creates a database in SQL Server and needs access to the database server. Therefore, before you run the post-setup configuration wizard, make sure that the FAST Search Server 2010 for SharePoint user (the user who is entered in the wizard) has permissions to create the database.

To set up permissions for SQL Server:

  1. If you have installed SharePoint Server in stand-alone mode, you must install SQL Server Management Studio. For more information, see http://msdn.microsoft.com/library/ms365247.aspx
  2. In the SQL Server Installation Center, click Installation, and then click New SQL Server standalone installation or add features to an existing installation. Installation type is Perform a new installation of SQL Server 2008.
  3. On the server where SQL Server is installed, open SQL Server Management Studio.
  4. In the Object Explorer, move to Security. Right-click Logins and select New Login…
  5. In the Login – New dialog box, on the General page, enter the FAST Search Server 2010 for SharePoint user as the Login name.
  6. In the Select a page pane, select Server Roles
  7. Select the DBCreator role.
  8. Click OK.

After you have run the post-setup configuration wizard, you can remove the DBCreator role. However, make sure that the FAST Search user can still read and write to the database that was created. In SQL Server Configuration Manager, also follow these steps:

  1. Verify that the main SQL Server service and the SQL Server Browser service are running. If the services are not running, start them by using Control Panel. Click Turn Windows features on or off, click Configuration, and then click Services.
  2. In SQL Server Network Configuration, click Protocols for <instance name>, and verify that TCP/IP is enabled.
  3. Follow the steps in: How to: Configure a Server to Listen to a Specific TCP Port.

 

Configure a stand-alone deployment (single server deployment)

A stand-alone deployment is useful when you want a deployment for product evaluation or demonstration, a small-scale deployment with minimal administrative overhead, or a development environment or test environment. A stand-alone deployment is an installation of FAST Search Server 2010 for SharePoint on a single server. All required components are installed on this server.

Configure a stand-alone deployment
  1. From the Start menu, run Microsoft FAST Search Server 2010 for SharePoint Configuration Wizard as a local administrator.
  2. On the Welcome page, click Next.
  3. On the Select the deployment type page, select Single server (stand-alone) and then click Next.
  4. On the Enter the user name and password page, enter the user name and password for the FAST Search Server 2010 for SharePoint user. This user must be a domain user. Refer to Required permissions for more information.
  5. On the Enter a certificate password page, enter a certificate password of your choice. This password will be used to protect the general purpose FAST Search certificate (see also Manage certificates (FAST Search Server 2010 for SharePoint)). You will need this password to install certificates on other servers. Retype the password and then click Next.
  6. On the Server settings page, enter the fully qualified domain name of the server and the base port. A deployment file will be generated automatically with all the settings configured.
  7. On the Database settings page, enter connection information to the SQL database that you installed and created before you installed FAST Search Server 2010 for SharePoint. Enter the Database connection string in the format <ServerName>\<DBInstanceName> (Example: mysqlserver1.contoso.com\myinstance).
  8. To determine the database connection string: On the server where the SQL Server is installed, open SQL Server Configuration Manager from the Start menu. Under SQL Server Services, you see the SQL Server main service. The service name contains the connection string in parentheses.
  9. Enter the Database name and Database port. The database will be created when you complete the configuration wizard. Click Next.
  10. On the Click-through relevancy settings page, add the desired relevancy click-through settings. Click-through relevancy enables automatic relevancy tuning based on how search users click on results. Select the relevant Microsoft SharePoint Server 2010 installation type.
  11. If you have installed SharePoint Server 2010 using the Standalone option, specify the Fully Qualified Domain Name (FQDN) of the SharePoint Server 2010.
  12. If you have installed SharePoint Server 2010 using the Server Farm option, specify the user who is running the Microsoft SharePoint 2010 Timer Service. This user is specified in the SharePoint Server 2010 post-setup configuration.
  13. If you do not want click-through relevancy, or if you do not have the necessary information, select Do not enable click-through relevancy.
  14. Click Next.
  15. On the Configuration settings summary page, review the settings and then click Configure. Wait while the configuration finishes.
  16. On the Post-setup configuration was successful page, click Finish.
  17. Before you restart the server, make sure that administrative permissions are defined. Update the local FASTSearchAdministrators group (which was created by the configuration wizard) to include either the user who will administer the FAST Search Server 2010 for SharePoint farm, or the domain group of your FAST Search Administrators.
  18. Restart the server.
Verify that all modules are running
  1. Log in as a user who is a member of the local FASTSearchAdministrators group.
  2. On the Start menu, click All Programs.
  3. Click Microsoft FAST Search Server 2010 for SharePoint.
  4. Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.
  5. At the Windows PowerShell command prompt, type the following command: nctrl status
  6. Make sure that all modules have the status Running.

 

Configure a multiple server deployment

A multiple server deployment is recommended for most production environments, except small deployments without any fault-tolerance requirements. A multiple server deployment is an installation of FAST Search Server 2010 for SharePoint services on multiple servers. During configuration, one server is defined as the administration server, which is the server where the administrative services are installed and run. The deployment is scaled out by adding one or more non-administration servers. A non-administration server does not have the administrative services set up, but connects to a running administration server in a multiple server deployment. The non-administration server runs services such as query matching, indexing and document/item processing.


Prepare the deployment file

The deployment file, deployment.xml, specifies the distribution of components and services across servers in a FAST Search Server 2010 for SharePoint farm. Each FAST Search Server 2010 for SharePoint farm has one deployment file. Each server in the farm can read the deployment file and determine the services that run locally on that server. Each server also determines the location of other services that it communicates with. The deployment file is a required input parameter when you run the configuration wizard (or configuration script) on the administration server. Non-administration servers will download the deployment file from the administration server, determine which services should run on the local server, and start these services.

An example deployment.xml template is shown later in this document: Deployment.xml template. You can also find example deployment.xml templates directly under <FASTSearchFolder>\etc\, where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch.

For information about how to prepare the deployment file, see deployment.xml reference. The completed deployment file to be used for the installation must be named deployment.xml.

The FAST Search Server 2010 for SharePoint administrator can reconfigure the deployment by adding or removing servers or services in the deployment file. For more information about reconfiguring, see Reconfigure the farm deployment (FAST Search Server 2010 for SharePoint).

Configure the administration server in a multiple server deployment This section describes how to configure a server as the administration server in a multiple server deployment by running the configuration wizard. The administration server must be configured and running before you can add one or more non-administration servers to the deployment. Make sure to follow these steps as a user who is a member of the local Administrators group.

  1. Prepare a deployment file as described in the deployment.xml reference document.
  2. From the Start menu, run the Microsoft FAST Search Server 2010 for SharePoint Configuration Wizard.
  3. On the Welcome page, click Next.
  4. On the Select the deployment type page, select Admin server and then click Next.
  5. On the Enter the user name and password page, enter the user name and password for the FAST Search Server 2010 for SharePoint user. This user must be a domain user.
  6. On the Enter a certificate password page, enter a certificate password of your choice. This password will be used to protect the general purpose FAST Search certificate (see also Manage certificates (FAST Search Server 2010 for SharePoint)). You will need this password to install certificates on other servers. Retype the password and then click Next.
  7. On the Server settings page, enter the fully qualified domain name of the server and the base port. Make sure that the server name is the same as the administration server that is defined in deployment.xml.
  8. In the Deployment file location box, enter the path of the deployment.xml file that you created. If there is an error in your deployment.xml file, you will get a warning. If no warnings or errors appear, your deployment.xml file syntax is correct. Click Next.
  9. On the Database settings page, enter the connection information to the SQL database that you installed and created before you installed FAST Search Server 2010 for SharePoint. Enter the Database connection string in the format <ServerName>\<DBInstanceName> (Example: mysqlserver1.contoso.com\myinstance). Enter the Database name and Database port. The database will be created when you complete this configuration wizard. Click Next.
  10. On the Click-through relevancy settings page, add the desired relevancy click-through settings. Click-through relevancy enables automatic relevancy tuning based on how search users click on results. Select the relevant SharePoint Server 2010 installation type.
  11. If you have installed SharePoint Server 2010 using the Standalone option, specify the Fully Qualified Domain Name (FQDN) of the SharePoint Server 2010.
  12. If you have installed SharePoint Server 2010 using the Server Farm option, specify the user who is running the timer service in SharePoint Server 2010. This user is specified in the SharePoint Server 2010 post-setup configuration.
  13. If you do not want click-through relevancy, or if you do not have the necessary information, select Do not enable click-through relevancy.
  14. Click Next.
  15. On the Configuration settings summary page, review the settings and then click Configure.
  16. Wait while the configuration finishes.
  17. On the Post-setup configuration was successful page, click Finish.
  18. Before you restart the server, make sure that administrative permissions are defined. Update the local FASTSearchAdministrators group (which was created by the configuration wizard) to include either the user who will administer the FAST Search Server 2010 for SharePoint farm, or the domain group of your FAST Search Administrators.
  19. Restart the server.
Verify that all modules are running on the administration server
  1. Log in as a user who is a member of the local FASTSearchAdministrators group.
  2. On the Start menu, click All Programs.
  3. Click Microsoft FAST Search Server 2010 for SharePoint.
  4. Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.
  5. At the Windows PowerShell command prompt, type the following command: nctrl status
  6. Make sure that all modules have the status Running.

Configure the non-administration server(s) in a multiple server deployment
By default, all servers in a multiple server deployment, except the administration server, are non-administration servers. In this section, you will configure each non-administration server that is specified in your deployment file as a non-administration server by running the configuration wizard. As part of this configuration process, the server will connect to the administration server to join the FAST Search Server 2010 for SharePoint farm.

On each non-administration server, do the following:

  1. Log in as a user who is a member of the local Administrators group.
  2. On the Start menu, right-click Microsoft FAST Search Server 2010 for SharePoint Configuration Wizard, and select Run as administrator.
  3. On the Welcome page, click Next.
  4. On the Select the deployment type page, select Non-admin server and then click Next.
  5. On the Enter the user name and password page, enter the user name and password for the FAST Search Server 2010 for SharePoint user. This must be the same user as you specified for the administration server during post-setup configuration.
  6. On the Enter a certificate password page, enter the certificate password. Use the password that was used for the certificate in the administration server post-setup configuration. Click Next.
  7. On the Server settings page, enter the fully qualified domain name of the server. Make sure that the server name is the same as the corresponding server name that is defined in deployment.xml.
  8. Enter the fully qualified domain name and the base port of the administration server and then click Next.
  9. On the Configuration settings summary page, review the settings and then click Configure.
  10. Wait while the configuration finishes.
  11. On the Post-setup configuration was successful page, click Finish.
  12. Before you restart the server, make sure that administrative permissions are defined. Update the local FASTSearchAdministrators group (which was created by the configuration wizard) to include either the user who will administer the FAST Search Server 2010 for SharePoint farm, or the domain group of your FAST Search Administrators.
  13. Restart the server.
  14. Verify that all modules are running on the non-administration server
  15. Log in as a user who is a member of the local FASTSearchAdministrators group.
  16. On the Start menu, click All Programs.
  17. Click Microsoft FAST Search Server 2010 for SharePoint.
  18. Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.
  19. At the Windows PowerShell command prompt, type the following command: nctrl status
  20. Make sure that all modules have the status Running.

 

Create and set up the Content SSA

  1. On SharePoint Server 2010, on the Central Administration Home page, click Application Management and then click Manage Service Applications.
  2. On the Manage Service Applications page, click New and then click Search Service Application.
  3. On the Create New Search Service Application page, in the Name section, provide a unique name for the Service Application. Example: FASTContent
  4. In the FAST Service Application section, select FAST Search Connector.
  5. Set the Search Service Account. Note that the Search Service Account is the same across all Search Services. If you set this account to something other than the default value, it will affect all Search Services.
  6. If you want to change the Search Service Account later, go to the Central Administration Home page. Click Security and then click Configure Service Accounts. Change the user who runs Windows Service - SharePoint Server Search.
  7. By default, the user specified in the Search Service Account is used to access the content sources that will be crawled. If a certain content source should be crawled by a different user, this can be specified with a crawl rule for that content source.
  8. In the Application Pool for Search Admin Web Service section, select either an existing application pool under Use existing application pool, or select Create new application pool and give it a unique name. Example: FAST_Content_App_Pool.
  9. If you create a new application pool, select a security account. This security account is used to run the application pool for the administrative Web service. Through this service, an administrator will communicate all search administration operations such as starting crawls and creating crawl rules.
  10. In the Content Distributors and Content Collection Name sections, enter the connection information to the FAST Search Server 2010 for SharePoint installation. Use the install_info.txt file as a reference for the location of the content distributor.
  11. Click OK. It may take a while to finish.

 

Configure SSL enabled communication

  1. Copy the script securefastsearchconnector.ps1 from the FAST Search Server 2010 for SharePoint administration server to the SharePoint Server 2010 server. The securefastsearchconnector.ps1 script is in the <FASTSearchFolder>, under installer\scripts\.
  2. Copy the certificate file FASTSearchCert.pfx from the FAST Search Server 2010 for SharePoint administration server to the SharePoint Server 2010 server. The certificate file is in the <FASTSearchFolder>, under data\data_security\cert\.
  3. Open a Microsoft SharePoint 2010 Management Shell with the Run as administrator option on the SharePoint Server 2010 server.
  4. Navigate to the directory where you copied the securefastsearchconnector.ps1 script and run it, replacing the necessary parameters with the values for your environment. The domain and user name should reflect the details of the user running the SharePoint Server Search 14 (OSearch14) service.
  5. .\SecureFASTSearchConnector.ps1 –certPath "path of the certificate\certificatename.pfx" –ssaName "name of your content SSA" –username “domain\username”
  6. When prompted to enter the certificate password, enter the certificate password that you supplied when you ran the post-setup configuration of FAST Search Server 2010 for SharePoint.

 

Add a content source

Navigate to the Manage Content Sources page Verify that the user account that is performing this procedure is a service application administrator for the FAST Search Content Search Service Application.In Central Administration, in the Application Management section, click Manage service applications. On the Manage Service Applications page, click your FAST Search Content Search Service Application. On the Search Administration Page, in the Crawling section, click Content Sources.

 

To create a content source

  1. On the Manage Content Sources page, click New Content Source.
  2. On the Add Content Source page, in the Name section, in the Name box, type a name for the new content source.
  3. In the Content Source Type section, select the type of content that you want to crawl. We recommend that you pick a small content source to verify the installation. You can add additional content sources, or edit or delete this content source after you have completed the installation.
  4. In the Start Addresses section, in the Type start addresses below (one per line) box, type the URLs from which the crawl should start.
  5. In the Crawl Settings section, select the crawling behavior that you want.
  6. In the Crawl Schedules section, to specify a schedule for full crawls, select a defined schedule from the Full Crawl list. A full crawl crawls all content that is specified by the content source, regardless of whether the content has changed. To define a full crawl schedule, click Create schedule.
  7. To specify a schedule for incremental crawls, select a defined schedule from the Incremental Crawl list. An incremental crawl crawls content that is specified by the content source that has changed since the last crawl. To define a schedule, click Create schedule.You can change a defined schedule by clicking Edit schedule.
  8. To prioritize this content source, in the Content Source Priority section, on the Priority list, select Normal or High.
  9. To immediately begin a full crawl, in the Start Full Crawl section, select the Start full crawl of this content source check box, and then click OK.
 
Create and set up the FAST Search Query SSA
  1. On SharePoint Server 2010, on the Central Administration Home page, click Application Management and then Manage Service Applications.
  2. On the Manage Service Applications page, click New and then Search Service Application.
  3. On the Create New Search Service Application page, in the Name section, provide a unique name for the Service Application.
  4. Example: FAST Query SSA
  5. Warning: If the SSA creation fails, you must enter a new unique name for this field. Otherwise, it will fail again and you must re-enter all data.
  6. In the FAST Service Application section, select FAST Search Query.
  7. In the Application Pool for Search Admin Web Service section, select either an existing application pool under Use existing application pool, or select Create new application pool and give it a unique name. Example: FAST_Query_Admin_SSA_App_Pool.
  8. If you create a new application pool, select a security account. The security account is used to run the SSA Admin Web service.
  9. Select Configurable, and enter the user account. The default is the managed service account.
  10. In the Application Pool for Search Query and Site Settings Web Service section, select either an existing application pool under Use existing application pool, or select Create new application pool, and give it a unique name. Example: FAST_Query_SSA_App_Pool.
  11. If you create a new application pool, select a security account. The security account is used to run the Web service for Search Query and Site Settings.
  12. Select Configurable, and enter the user account.
  13. In the Query Service Location, Administration Service Location and Resource Store Location sections, enter the connection information to the FAST Search Server 2010 for SharePoint installation. The location (URLs/port numbers) of the services is included in the install_info.txt file.
  14. The examples here assume a base port of 13000 for FAST Search Server 2010 for SharePoint.
  15. Query Service Location: http://fastsearch1.contoso.com:13287 or https://fastsearch1.contoso.com:13286 (If you have enabled HTTPS for queries)
  16. Administration Service Location: http://fastsearch1.contoso.com:13257 or https://fastsearch1.contoso.com:13258 (If you have enabled HTTPS for queries.)
  17. Resource Store Location: http://fastsearch1.contoso.com:13255
  18. Account for Administration Service: domain\user.
  19. Click OK. It may take a while to finish.
  20. When finished, a new SSA is added to the list of Service Applications.
  21. Review the redundancy and availability requirements for the Query SSA. For planning considerations, see Recommendations: Redundancy and availability (FAST Search Server 2010 for SharePoint). For deployment details, see Multiple server deployment of the Query SSA (FAST Search Server 2010 for SharePoint).

 

Verify user access to FAST Search Server 2010 for SharePoint administrative services

  1. On SharePoint Server 2010, on the Central Administration Home page, under Security, select Configure Service Accounts.
  2. Each web application has a separate Web Application Pool. Select the relevant component, typically Web Application Pool - SharePoint - 80.
  3. Make sure that the user account for this component is a member of the FASTSearchAdministrators group on the FAST Search Server 2010 for SharePoint administration server.

 

Connect the FAST Search Query SSA to your web application(s)

  1. On SharePoint Server 2010, on the Central Administration Home page, select Application Management.
  2. Under Service Applications, click Configure service application associations.
  3. Click the Application Proxy Group that you want to change, typically default.
  4. Make sure that the Query SSA (for example FAST Query SSA) is the default and only selected Search Service Application Proxy, and then click OK.
  5. Verify that the correct Query SSA is associated with the web application.

 

Configure claims authentication

This section describes how to transfer a Microsoft SharePoint Server 2010 STS certificate (MOSS_STS) from SharePoint Server 2010 to all FAST Search Server 2010 for SharePoint query servers to provide security trimmed queries. Security trimming, or item level security, limits user access to items in search results that the user who submitted the query is authorized to see.

  1. On SharePoint Server 2010, export the SharePoint STS certificate:
  2. On the Start menu, click All Programs.
  3. Click Microsoft SharePoint 2010 Products.
  4. Right-click SharePoint 2010 Management Shell, and select Run as administrator.
  5. At the Windows PowerShell command prompt, type the following command(s):
  6. Copy MOSS_STS.cer to a location that is available to the FAST Search Server 2010 for SharePoint query servers.
  7. On each FAST Search Server 2010 for SharePoint query server, import the SharePoint STS certificate:
  8. On the Start menu, click All Programs.
  9. Click Microsoft FAST Search Server 2010 for SharePoint.
  10. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.

At the Windows PowerShell command prompt, browse to <FASTSearchFolder>\installer\scripts\, where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch. Type the following command:

 

Enable HTTPS (optional)

If you want to help secure query traffic by using HTTPS, you must perform some additional optional steps. With FAST Search Server 2010 for SharePoint, you can choose between HTTP and HTTPS for query traffic. HTTP is used as a default.

HTTP: All query traffic from the SharePoint Server 2010 search application to FAST Search Server 2010 for SharePoint will be sent via HTTP requests. The information is not encrypted. However, this communication channel is faster than HTTPS. Use HTTP if your documents do not contain sensitive information, or if you want maximum query performance. This is the default method.

HTTPS: All query traffic from the SharePoint Server 2010 search application to FAST Search Server 2010 for SharePoint will be sent via secured requests. The information is encrypted so that no one can access sensitive information that is contained in the query traffic. Use HTTPS if your documents contain sensitive information.

  1. On each query server in FAST Search Server 2010 for SharePoint, follow these steps:
  2. Import the server-specific SSL certificate into the certificate store. The certificate must be saved under Certificates(Local Computer)\Personal.
  3. Grant the FASTSearchAdministrators group full access to the certificate, by using winhttpcertcfg or the Microsoft Management Console (MMC) Certificates snap-in.
  4. To grant access by using the MMC snap-in:
  5. Click Start, type mmc in the Search programs and files box, and then press ENTER.
  6. Right-click the certificate, click All tasks, and then click Manage Private Keys.
  7. Click Add, add the FastSearchAdministrators group and select Full control.
  8. Configure the query server to use the certificate on base port + 286.
  9. On the Start menu, click All Programs.
  10. Click Microsoft FAST Search Server 2010 for SharePoint.
  11. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.
  12. At the Windows PowerShell command prompt, type the following command(s):
  13. On the SharePoint Server 2010 server, follow these steps:
  14. Enable a trust relationship in SharePoint Server 2010 for the SSL certificate(s) that you created for each query server. Do this by importing the public certificate of the signing authority of the SSL Certificate(s) into SharePoint Server 2010:
  15. On the Start menu, click All Programs.
  16. Click Microsoft SharePoint 2010 Products.
  17. Right-click SharePoint 2010 Management Shell, and select Run as administrator.
  18. At the Windows PowerShell command prompt, type the following command(s):
  19. Change the Query Service Location configuration setting for the Query Search Service Application (SSA) to use the HTTPS endpoint. See Create and set up the Query Search Service Application (FAST Search Server 2010 for SharePoint) for detailed information.

Create a FAST Search Center site (FAST Search Server 2010 for SharePoint)

Open the SharePoint Server 2010 Web application where you want to create a new site. Enable features unless this has already been done:

  1. Click Site Actions, then click Site Settings, and then click Site collection features.
  2. Make sure that the following are enabled:
  3. SharePoint Server Publishing Infrastructure
  4. SharePoint Server Enterprise Site Collection features
  5. Create a new site:
  6. Click Site Actions and then click New Site.
  7. Select the FAST Search Center template.
  8. Click Create. A FAST Search Center is created at the specified URL.

 

Verify that all services are running

On each server in the FAST Search Server 2010 for SharePoint farm:

  1. On the Start menu, click All Programs.
  2. Click Microsoft FAST Search Server 2010 for SharePoint.
  3. Click Microsoft FAST Search Server 2010 for SharePoint shell.
  4. At the Windows PowerShell command prompt, type the following command: nctrl status
  5. Verify that all services have the status running.

 

Feed and query test documents

Test integration between FAST Search Server 2010 for SharePoint and SharePoint Server After you completed the steps in Create and set up the Content SSA, a Content SSA with a content source should have been created and some items should have been crawled.

Verify that documents have been fed to FAST Search Server 2010 for SharePoint:
  1. On the Start menu, click All Programs.
  2. Click Microsoft FAST Search Server 2010 for SharePoint.
  3. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.
  4. At the Windows PowerShell command prompt, type the following command: Get-FASTSearchContentCollection -Name "sp"
  5. Verify that one or more documents are displayed in the search result from the FAST Search Center site:

Open the FAST Search Center site that you created, and do a search for the documents that you fed to FAST Search Server 2010 for SharePoint. Verify that one or more of the documents that you fed to FAST Search Server 2010 for SharePoint are returned in the search results.

Test feeding and searching on FAST Search Server 2010 for SharePoint

Follow these steps on a FAST Search Server 2010 for SharePoint server that has the query processing component (query role in the deployment.xml file). By default, single server deployments have this component. Refer to deployment.xml reference for more information.

  1. On the Start menu, click All Programs.
  2. Click Microsoft FAST Search Server 2010 for SharePoint.
  3. Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.
  4. At the Windows PowerShell command prompt, type the following command to feed a single document: Docpush -c sp <filename>
  5. Where <filename> is the full path to a test document that can be indexed by FAST Search Server 2010 for SharePoint. Use any text document, Office document or HTML document. Verify that the document or documents were indexed correctly, by running the following command: Get-FASTSearchContentCollection -name "sp"
  6. Open a browser on the FAST Search Server 2010 for SharePoint server that has the query processing component and go to the page: http://localhost:<baseport + 280>.

The baseport is the base TCP/IP port for the FAST Search Server 2010 for SharePoint farm. In a default deployment, the base port is 13000. Replace <baseport + 280> with the actual port number.

  1. In the FQL Query field, type a word that you know exists in the document(s) that you previously fed. Click Search.
  2. Verify that the XML test result page returns an item (document) that contains the content of your test document.
  3. To remove all the documents that you added, run the following command: Clear-FASTSearchContentCollection -name "sp"

 

Check the Event Log

On the FAST Search Server 2010 for SharePoint administration server, open the Event Log. Browse to Applications and Services Logs and FAST Search Farm. Verify that no error messages are displayed.

Print
Posted: Mar 8, 2018,
Categories: SharePoint & EPM,
Comments: 0,
Author: Urish Arora
Tags: search
Rate this article:
5.0

Urish AroraUrish Arora

Other posts by Urish Arora

, Contact author

Please login or register to post comments.

Name:
Email:
Subject:
Message:
x

SEARCH

Categories

Subscribe to our blog

«May 2019»
MonTueWedThuFriSatSun
293012345
6789101112
13141516171819
20212223242526
272829303112
3456789

  • Featured Posts
  • Recent Posts
  • Recent Comments
Dynamics365Authority is a community platform for Professionals and Students to contribute or share their knowledge and skills on Microsoft Dynamics 365 Technologies. Our primary goal is to invite professionals on Dynamics 365 technology across the world to contribute & share their knowledge and skills through their blogs so that we can help other developers.
Stay updated with Dynamics 365 technology. Improve skills and knowledge from our blogs, articles and code snippets. Learn it. Follow professionals and learn from them.
Unified Service Desk Book(Online Edition) 

FOLLOW US

Stay connected with us on our social media channels for latest articles, blogs posts etc.  We will keep updating regularly on our social media platform and web platform.

FACEBOOK

Follow us on Facebook

 

TWITTER

View all our tweets

 

DYNAMICS365AUTH

Join us now

 

BLOGS

View our blogs

 

 

Latest Blog

Posted: Apr 30, 2019

Find which privileges are applied to which roles in Dynamics 365 with privileges discovery

This blog is about Find which privileges are applied to which roles in Dynamics 365 with privileges discovery

Read more
Posted: Apr 30, 2019

Dynamics 365 Field Security

This blog is about Field Security in Dynamics 365

Read more
Posted: Apr 30, 2019

Access Team Templates in Dynamics 365

This blog is about Access Team Templates in Dynamics 365

Read more
RSS

ADDITIONAL RESOURCES

Dynamics 365 Authority.com - Search the library for "Dynamics 365"

  What's New in Dynamics 365

  Dynamics 365 Documentation

  

  Sign-up for 30 days trial

 

 

Recent comments

Ashish:

Nice blog. Very helpful to get all references to white papers at one place.

Previous Next

About Us

Here comes the Dynamics 365 Authority - Great technical blog posts are hidden gems. They are hard to find simply because not enough of us write them in the first place. Yet technical blogging is one of the best things we can do not only for ourselves, but also as members of the wider community of developers.

Dynamics 365 Authority leverages this platform to help developers and users to move from traditional paper-based process to modern digital business process. Dynamics365Authority.com helps your business grow, evolve and transform.

Dynamics365Authority.com is your Digital Transformation Partner

Recent Posts

Find which privileges are applied to which roles in Dynamics 365 with privileges discovery

This blog is about Find which privileges are applied to which roles in Dynamics 365 with privileges discovery

  • 3
  • Article rating: No rating

Dynamics 365 Field Security

This blog is about Field Security in Dynamics 365

  • 3
  • Article rating: No rating
RSS

Get in touch

Follow Us

 

Tag cloud: Dynamics365Authority.com with Urish Arora; Dynamics365Authority.com; Sales; Leading community site on MS Dynamics 365; Dynamics 365 Authority; Service;Top CRM Blogs; Urish Arora - Australia's leading expert on Digital Transformation;  Digital Transformation; Field Service;Top Articles on MS Dynamics CRM Relationship Insights; Office 365 Security Compliance; Project Service; Microsoft Dynamics 365 for Sales; Relevance Search; Goal Metrics; Activities and Case; Sales Literature;Knowledge Management;

Terms Of UsePrivacy StatementCopyright 2019 by Dynamics365Authority
Back To Top