This topic describes the indexing scheduled job in an integration of Optimizely Search & Navigation with Optimizely CMS.
How it works
The EPiServer.Find.Cms assembly ships with a scheduled job plug-in, which lets administrators reindex an entire site from the Optimizely CMS admin mode. The job, Episerver Find Content Indexing Job, can be started manually or via the job scheduling feature.
Note: You only need to schedule the indexing job for specific circumstances described below. Optimizely instantly indexes any content changes. If you run the indexing job when it is not necessary, you are unduly adding to the system load.
Using the scheduled job
There are two legitimate scenarios for using the scheduled indexing job to index all pages:
- After installing the Search & Navigation CMS integration for the first time. Otherwise, existing pages are only indexed when manually republished.
- The automatic indexing failed, or pages should be reindexed for another reason.
When started manually, the job runs within the IIS server application pool and is interrupted by IIS when the Idle Time-out passes. By default, the timeout is set to 20 minutes. Indexing a large site may take more than 20 minutes, and it is not advisable to increase the timeout. Therefore, it is recommended to schedule the job, as the Optimizely scheduled job process is not affected by the timeout.
Log of indexing activity
At the completion of an indexing job, a report prints to the history log displaying execution time and number of pages indexed.
Indexing job: Reindexing completed. ExecutionTime: 0minutes 18seconds Number of pages indexed: 180
If an error occurs, the report notifies you where it occurred and gives the error message. Two types of errors are counted:
- Page errors, relating to filtering or loading page.
- Batch errors, relating to transmitting and indexing files to Optimizely Search & Navigation.
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