Skip to main content

SharePoint 2013 Search Extensibility Points

SharePoint 2013 buzz word "Search 2013 Extensibility" related to the Search prospective. In SharePoint 2013 following are the points where we can customize the search experience. 
  1. BCS Connector 
  2. Content enrichment web service 
  3. Custom entity extraction 
  4. Pre/post security trimming 
  5. Custom Ranking Models
  6. User Experience (UX)

  • BCS Connector: SharePoint 2013 there are some of the new method added in the BCS entity connector framework that works well and more stable for large items. Crawl data from the external system you can use the BCS connector and crawl the data into your SharePoint 2013. Please refer the below link that refer the BDC Mode properties and method that need to incorporate in your BDC file. 
    • SharePoint BCS Connector and its method that required for crawl
      • No Code
        • OData
        • SQL
      • Code
        • .Net Assembly
        • WCF
    • BCS Request Methods 
      • Full Crawl
        • Finder(): Return All Docuemnt
        • SpecificFiner(Id1): Return the properties to the single Item. 
        • StreamAccessor(Id1) (Optional): Only way to get the data like attachments like word document and excel document & you wanted to parse the data into text. So you need to use this method.
      • Incremental Crawl following two methods used instead of finder
        • ChangedIdEnumerator
        • DeletedIdEnumerator
If you do not specify the incremental crawl methods, during incremental crawl behind the seen it will run full crawl.
http://msdn.microsoft.com/en-us/library/gg294165.aspx#SearchBDCModelProperties_Performance

  • Content Enrichment Web Service: Content Enrichment web service is called during the content processing. So any crawl properties during content processing you want to change it. You can use the content enrichment web service. 
  • Custom Entity extraction: SharePoint Server 2013 administrators can create and deploy custom entity extraction dictionaries to configure the search system to look for specific words or phrases (entities) in unstructured content. The extracted entities are stored in separate managed properties, and you can use them to improve your organization’s search experience.
    • Determine which type of custom entity extraction dictionary you want to create: Word, Word Part, Word exact or Word Part exact

Comments

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis