In this port , I’m going to talk about the FAST Search components and how they are interacting with each other , I recommend to read this article before start deploying FAST search as it should give a good guidance and understanding for your deployment plan:
Is the default indexing connector and retrieves content from various content sources such as SharePoint content repositories, Web servers, Exchange folders, line of business data and file servers.
its worth to mention that this is a SharePoint service applications that will run within SharePoint farm
handle query results from users.
Note: for large FAST deployments I recommend to dedicate a special SharePoint application server to host the Content SSA and Query SSA service applications
The rest of the below components are FAST components:
Content distributor communicates with the indexing connectors and organizes the feeding of documents from indexing connectors to the indexing service. You can set up a primary and a backup content distributor for fault-tolerance.
The item processing component receives items to be indexed from indexing connectors. and process the items according to the given configuration. It then sends the processed items to the indexing service ,item processing responsible for:
It analyzes search clickthroughs logs and hyperlink structures. Both contribute to better ranked search results as the following:
Below is a Real deployment scenario using same server role for indexing and Query matching in 3 servers topology will look like below where:
Primary and backup indexer You can configure a backup indexer node for fault tolerance.
One row in the configuration file is used to determine Search rows and indexer rows like in below example is a pure index server. <row id="0" index="primary" search="false" />
Search Cluster Example:
In below example you can see 4 servers , you can see one Indexing node-X in row 1 with a corresponding Query Matching node-x in row 2 , with fault tolerance applied , the below is called Search cluster, where each index row should contain a complete set of indexing (full index = index-X + index-Y) , mapped to a corresponding querying matching component in the same column. (Index-X in row1 is mapped to Query Matching-X in row 2)
The SharePoint Server 2010 Central Administration and site collection user interfaces provide the administrative interfaces for managing the FAST Search Server 2010 for SharePoint deployment and features.
The administration component contains functionality to control the search experience, such as determining how to perform property extraction, ascertaining which synonyms to use, and determining which items to use as best bets.
Consist of the below :
Ensures that only items that a user is entitled to read appear in the query results.
The FSA manager communicates with Claims services, Active Directory services or other LDAP based directory services to manage the authorization process.
FAST Search Web Crawler
The FAST Search Web crawler is an optional indexing connector that can be used for complex Web crawl scenarios involving a mix of Internet and Intranet sites.
The FAST Search Web crawler reads Web pages and follows links on the pages to process a complete Web of items. It then passes the retrieved items to the item processing service.
Does it make sense to split the admin node on its own? where is the fault tolerance if the Admin server goes down ?