EPiServer CMS 7.5 with updates

Introduction

This document describes the integration between EPiServer Find and EPiServer CMS 7.5 with updates. The EPiServer CMS integration consists of a number of components that makes it convenient to use the Find .NET client API with EPiServer CMS.

Integration components

The integration components are:

• IndexingModule Hooks up events to handle indexing content (IContent objects).
• A set of conventions applied to the SearchClient.Instance object to exclude some properties of the IContent object and other EPiServer classes as well as including some additional fields. This is handled by the IndexingModule at startup using the CmsClientConventions class.
• The ContentIndexer class which handles the indexing, re-indexing and removing content from the index. The content to be indexed can be customized by modifying the conventions it uses.
• A scheduled job - EPiServer Find CMS Indexing Job, for complete re-indexing of all content.
• The GetContentResult extension method that can be called to execute search requests and get actual IContent objects back.
• A number of additional filter methods that make it more convenient to filter on EPiServer CMS types such as ContentReference.

Setting up for development

The CMS integration assumes that each environment has its own Find index. It also assumes that content are added and removed through the CMS API. This means that:

• Each developer should have their own development index unless they use a shared database.
• Each server environment (test, staging etc) should have its own index unless they use a shared database.
• If content are removed or added in other ways than through the CMS API (for instance using a database restore/rollback), the scheduled job for re-indexing should be run.

If any of the above guidelines are not met, the search and querying functionality may appear to be working, but may produce unexpected results. For instance, the GetContentResult method returning less content than its TotalMatching property reports. This would for instance happen if two developers use the same index, and one of them publish a page that does not exist in the other developers database.