Version: Episerver Find for Episerver Commerce 1 R2 SP2             Release date: Dec 18, 2012

About this Release

This download provides the installation package for installing the search provider  Episerver Find with Episerver Commerce 1 R2 SP2. The package includes the compiled binaries with the necessary binaries for Commerce 1 R2 SP2.

The core files and sample templates for Episerver Commerce 1 R2 SP2 are downloaded separately.


The following is required for installing Episerver Find for Commerce:

  • A running Episerver Commerce 1 R2 SP2 site.
  • An Episerver Find index:
    - Go to the Episerver Find site to create a developer index.
    - Create an account, log in and select the "Add Developer Service" option.
    - When setting up the index service, make sure to include the languages that the Commerce test catalog will index.
    - On the index details page, copy the serviceUrl and defaultIndex values from the sample web.config snippet.
    - Other designated test indexes for Find can also be used.


Follow the steps below to install Episerver Find on an Episerver Commerce 1 R2 SP2 site.

Step 1. Download and extract the installation files.

Step 2. Add the EPiServer.Business.Commerce.FindSearchProvider.dll, EPiServer.Find.dll, and Newtonsoft.Json.dll to the bin directory (from either the Distribution/Debug or Distribution/Release directory in the installation package).

Note: They may need to be added into two bin directories if there are separate front-end and Commerce Manager sites.

Step 3. Configure the Mediachase.Search.config file in the environment (again, there may be two).

The important parts to set are:

  • Set the defaultProvider attribute of the SearchProviders element to “FindSearchProvider”.
  • Add the FindSearchProvider element to the <providers> section.
  • Set the serviceUrl and defaultIndex attributes to point to the Find index.
  • The indexedLanguages and IndexedCurrencies need to be set to comma separated lists of all the indexed language/locales. These must be a full locale, like EN-US, instead of just EN, to match up with the catalog system, and all the indexed currency codes. These values should be comma separated lists, and are case insensitive. Any metafields for unlisted languages, prices or currencies will not be searched.
  • In the indexers section, change the catalog indexer’s type attribute to match the FindSearchIndexBuilder type, as shown in the sample configuration file (see above).

Step 4. In the Commerce Manager site, go to Administration in the left menu, and open Systems Settings. Click Search Index to rebuild the index. The search should now be using the Find service.

Related Information