Search Components

Search Components

When we configure the search in SharePoint 2013,we need to assign the roles and distribute the components in between the servers, In this article I am explaining in detail the roles of the search components.

Please go through the link provided to know what are the components for search.

http://expertsharepoint.blogspot.de/2014/12/manage-search-schema-in-sharepoint.html 

http://expertsharepoint.blogspot.de/2014/12/manage-search-topology-in-sharepoint.html 

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.
Source from: http://www.c-sharpcorner.com/UploadFile/Roji.Joy/enterprise-search-configuration-in-sharepoint-2013/
Thanks to Destin for the great Article.

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Migration of search Admin component to different server in the same farm

Migration of search Admin component to different server in the same farm.

Recently one of the farms got some additional servers joined to the farm. The Search Admin was running on a WFE, and we wanted to move search off to some dedicated servers. Here is the Power Shell script for moving Search Admin:

$SSA = Get-SPEnterpriseSearchServiceApplication "Current Search Service App"
$SA = Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $SSA
$SA | Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance NewServerName –Force

After moving the Search Admin you’ll want to kick start the crawlers with the following:

Suspend-SPEnterpriseSearchServiceApplication $SSA
Resume-SPEnterpriseSearchServiceApplication $SSA

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Manage the search schema in SharePoint Server 2013

Crawled properties are metadata that is extracted from documents during crawls. Metadata can be structured content (such as the title or the author from a Word document), or unstructured content (such as a detected language or extracted keywords). 

Users can only search on managed properties and not on crawled properties. To make a crawled property available for search queries, you must map the crawled property to a managed property. You can map multiple crawled properties to a single managed property or map a single crawled property to multiple managed properties.

Link from MS: 

http://technet.microsoft.com/en-us/library/jj219667%28v=office.15%29.aspx#proc2 

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Manage the search topology in SharePoint Server 2013

Manage the search topology in SharePoint Server 2013

The following articles on Tech Net provide information about how you manage search components in SharePoint 2013

  http://technet.microsoft.com/en-us/library/jj219705%28v=office.15%29.aspx


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

SharePoint Server 2013 crawler has insufficient permissions to crawl file shares

SharePoint Server 2013 crawler has insufficient permissions to crawl file shares

Issue: SharePoint Server 2013 crawler has insufficient permissions to crawl file shares

Solution: Please follow the below steps to resolve the issue.

1.    Click Start, click Run, type gpedit.msc, and then click OK.

2.    Navigate to the following location in the Local Group Policy Editor:

Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment

3.    In the right pane, locate and right-click Manage auditing and security log, and then click Properties.

4.    Click the Add User or Group button in the Manage auditing and security log properties dialog box, and then add the crawl account that the SharePoint 2013 crawler uses.

5.    Click OK in the Manage auditing and security log properties dialog box.

Note: If you assign the Manage Auditing And Security Log permission by using a Group Policy Object (GPO), add the crawl account to the GPO.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.