The Search Service in SharePoint 2013 is completely re-architected.
The provisioning of the service application and its constituent components changes significantly, however from a multi tenancy perspective all we need to do is create the service application in Partition Mode as we did with SharePoint Server 2010. What is
brand new and you should like this, is that unlike SharePoint Server 2010 which did not expose any tenant specific configuration, Tenant Administration now provides access to all of the key settings.
Many of the *.EnterpriseSearch* Windows PowerShell cmdlets also are partition aware and can be used to automate some of the above configuration.
Be sure that the Search Service Application has been created and the service is
up and running.
The first new thing that I saw is the “Where should users searches go?”When you click on it, it will ask you to fill the “preferred search center”. At the right side, you can see that the service has never been runned, so
you can click on the left side “Content Sources”.
So we are going to test the search on my Portal SPPirate, I made a search on Gokan, but the search
Under Content Sources we can define with site should be
crawled for search. I have only one site, but if you have many sites, you can edit them here.
Under the version 2010, you had incremental and full crawl. Now there is a new crawl:”Continuous Crawl”.
This is a special type of crawl that eliminates the need to create incremental crawl schedules and will seamlessly work with the content source to provide maximum freshness.
When you start the crawl you will see that the status will change.
Now, when we made a new search under the Portal SpPirate, the Search WebPart will return now values.
We even can now apply filters with a progress bar. Great thing !
Even, when you wait on a searched element, you will be promted by a new great tool where you can:
I was too curious and clicked directly on SEND. But be sure that a client is installed for sending this one.
When editing you page, you can see search webparts:
Or even Search-Driven Content.