Logo 
Search:

Sharepoint 2010 Articles

Submit Article
Home » Articles » Sharepoint 2010 » Sharepoint SearchRSS Feeds

Search Architecture in SharePoint 2013

Posted By: Destin Joy     Category: Sharepoint 2010     Views: 34773

n this article we can learn how we can configure SharePoint 2013 Search. In SharePoint 2013 the two Search Engines "SharePoint Search" and "FAST Search Server for SharePoint" was combined in one Search Engine. Much of the search enhancement is due to Analytics moving into search. This will make Analytics Processing Component in SharePoint Server 2013 runs different analytics jobs to analyze content in the search index and user actions that were performed on a site to identify items that users perceive as more relevant than others

 

 

Search components

Query processing Content processing Index Crawl Search administration Analytics Index partitions · You can divide the index into discrete portions called index partitions, each holding a separate part of the index. · An index partition is stored in a set of files on a disk. · The search index is the aggregation of all index partitions. Index replicas · Each index partition holds one or more index replicas that contain the same information. · You have to provision one index component for each index replica. · To achieve fault tolerance and redundancy, create additional index replicas for each index partition and distribute the index replicas over multiple application servers. Query processing component Analyzes and processes search queries and results. Crawl component · Crawls content based on what is specified in the crawl databases. · Add crawl components to address capacity requirements and to increase crawl performance. Search administration component · Runs system processes that are essential to search. · Only one search administration component can be active per Search service application. Content processing component Carries out various processes on the crawled items, such as document parsing and property mapping, before feeding the items to the index component. Analytics processing component Carries out search analytics and usage analytics. Index component — The index component is the logical representation of an index replica.

Search databases

Search admin db Crawl database · Stores the crawl history · Manages crawl operations · Each crawl database can have one or more crawlers associated with it. Link database Stores the information extracted by the content processing component and also stores click-through information. Analytics reporting database Stores the results of search usage analytics. Search administration database · Stores search configuration data. · Only one search administration database per Search service application. Link db Analytics db Crawl db

Crawl component

The crawl component crawls the content sources. You can crawl a wide variety of content sources, for example file shares, SharePoint content, line of business applications and many more. To retrieve information, the crawl component connects to the content sources by invoking the appropriate indexing connector or protocol handler. After retrieving the content, the crawl component passes crawled items to the content processing component.

Content processing component

The content processing component processes crawled items and sends these items to the index component. The content processing component performs operations such as document parsing and property mapping. It also performs linguistics processing such as language detection and entity extraction. The component transforms crawled items into artifacts that are included in the search index. The content processing component also writes information about links and URLs to the link database. In turn, the analytics processing component writes information related to the relevance of these links and URLs to the search index through the content processing component.

Analytics processing component

The analytics processing component analyzes crawled items, which is referred to as search analytics, and how users interact with search, which is referred to as usage analytics. Examples of search analytics are links, anchor texts and metadata. An example of usage analytics is the number of times an item is viewed. The analytics processing component analyzes search analytics and usage analytics. Search analytics information is stored in the link database and usage analytics information in the analytics reporting database.

Index component

The index component is the logical representation of an index replica. In the search topology, you have to provision one index component for each index replica. The index component receives processed items from the content processing component and writes those items to an index file. Index files are stored on a disk in an index replica. The index component receives queries from the query processing component and returns result sets. You can divide the search index into discrete portions, called index partitions. Each index partition holds one or more index replicas. The search index is the aggregation of all index partitions.

Query processing component

The query component analyzes and processes queries and results. When the query processing component receives a query, it analyzes and processes the query to optimize precision, recall and relevance. The processed query is submitted to the index component. The index component returns a result set based on the processed query to the query processing component, which in turn processes that result set, before returning it to the front-end.

Search administration component

The search administration component runs the system processes for search. This component performs provisioning, which is to add and initialize instances of the other search components.

Crawl database

The crawl database stores tracking information and details about crawled items. For example, it stores information about the last crawl time, the last crawl ID and the type of update during the last crawl.

Link database

The link database stores information extracted by the content processing component. It also stores information about the number of times people have clicked on a search result. The information is stored unprocessed; the analytics processing component performs the analysis.

Analytics reporting database

The analytics reporting database stores the results of usage analytics and extracts information from the link database when it is required.

Search administration database

The search administration database stores search configuration data and the access control list (ACL) for the crawl component. There can be only one search administration database per search service application.

Share: 


Didn't find what you were looking for? Find more on Search Architecture in SharePoint 2013 Or get search suggestion and latest updates.

Destin Joy
Destin Joy author of Search Architecture in SharePoint 2013 is from Pathanamthitta, India. Destin Joy says

 Hello Everyone,

I am Destin Joy from India I have MCPD in SharePoint 2010, MCTS SharePoint 2010 application development and MCTS in SharePoint 2007. I am mostly working in  core part of SharePoint (2010-2007) and passionate about new Microsoft technologies. Born and brought up in Kerala You can reach me  @ Destin.Joy@hotmail.com

 

 
View All Articles

 
Please enter your Comment

  • Comment should be atleast 30 Characters.
  • Please put code inside [Code] your code [/Code].

 
No Comment Found, Be the First to post comment!