This topic describes the indexing scheduled job in an integration of Episerver Search & Navigation (formerly Episerver Find) with EPiServer 7/7.5 CMS.
The EPiServer.Find.Cms assembly ships with a scheduled job plug-in, which allows administrators to re-index the entire site from within the Episerver CMS admin mode. The job is named Episerver Find CMS indexing job, and it can be started either manually or via the standard scheduling functionality in Episerver CMS.
There are primarily two scenarios for using the scheduled job:
Note: When started manually, the job (as all Episerver jobs) runs within the application pool of the IIS server and is interrupted by IIS when the Idle Time-out passes. By default, the timeout is set to 20 minutes.
While indexing a large site may take more than 20 minutes, it is not advisable to increase the timeout to handle this. Therefore, it is recommended to always trigger the job by scheduling, because it will be executed by the Episerver scheduled job process and not affected by the timeout.
At the completion of an indexing job, a report is printed to the history log displaying execution time and the number of pages indexed.
Indexing job: Reindexing completed. ExecutionTime: 0minutes 18seconds Number of pages indexed: 180
When an error occurs, the report will notify where it occurred and give the error message. Two types of errors are counted:
Example of error notification:
Indexing job: Reindexing completed. ExecutionTime: 0minutes 16seconds Number of pages indexed: 169 Number of page errors: 11 Number of batch errors: 0 An error occured while filtering Page: 113. The 'ShouldIndex' function could not be evaluated for Page: 113. ShouldIndex-exception. (see log for more information)
To see the stack trace, activate the logging functionality and trace it in your log file.
Last updated: Oct 31, 2016