This walkthrough describes how to set up Solr for use with Sitecore. It does not cover all configuration options available in Solr: it only documents configuration details specific for using Solr in Sitecore.
This walkthrough describes how to:
- Install Solr
- Generate an XML Schema for Solr
- Verify that Solr is running correctly
- Configure an IOC container
- Configure Sitecore to work with Solr
- Rebuild the search Indexes
You must you use a separate core for each index. This topic on the Solr wiki introduces the multiple core concept.
When you configure Solr, use the 64-bit version of the Java Virtual Machine (JVM) for production servers. Solr allocates 512 MB of memory by default. If you require Solr to have access to more memory you can adjust these limits when Solr starts up. See the official Solr documentation for more information.
Generate an XML Schema for Solr
Solr needs a defined XML schema when working with documents.
You can modify an existing schema with the Generate the Solr Schema.xml file tool. This tool automatically generates a basic schema and ensures all the fields that Sitecore needs are present. You can add your own fields to this schema, as long as you do not change the system index fields.
To generate a new
Solr schema.xml file:
- In the Control Panel, click Generate the Solr Schema.xml file:
- In the Source file field, enter the path to the Solr schema that you want to use.
- In the Target file field, enter the destination for the new schema file, for example, the website root folder:
- Click Generate. Sitecore updates the
schema.xmlfile and adds all the necessary fields that it needs.
- Copy the file to the conf folder of the relevant core.
Note If you have any other field definitions, copy fields, or dynamic fields configured in your schema, they are overwritten by the schema generator. To preserve these fields, copy your original schema and merge it with the newly generated schema afterwards.
If you have any other field definitions, copy fields, or dynamic fields configured in your schema, they are overwritten by the schema generator. To preserve these fields, copy your original schema and merge it with the newly generated schema afterwards.
Note about Sitecore 8.2, Update 6 Sitecore 8.2, Update 6 and later versions of Sitecore 8.2 support later version of Solr. The procedure changes slightly in these versions:
Note about Sitecore 8.2, Update 6
Sitecore 8.2, Update 6 and later versions of Sitecore 8.2 support later version of Solr. The procedure changes slightly in these versions:
The screenshot in step 3 will look like this:
Add these steps:
- Open the
solrconfig.xmlfile, and add a
schemaFactorynode under the
<schemaFactory class="ClassicIndexSchemaFactory" />
- Remove the managed-schema file from your
Verify that Solr is running correctly
After generating a new
schema.xml file and updating the
solrconfig.xml file, you must verify that Solr runs correctly.
To verify that Solr is running correctly:
- Ensure Solr is not running. A full restart is needed so that it loads the new configuration.
- Start Solr.
- Check the output log files. If there are no errors, then open the Solr administration page.
To open the administration page, enter the following URL in your browser: http://localhost:8983/solr/admin:
- Click Core Admin and then click a core. In this example, there is one core, called itembuckets:
If you can see the Solr administration page and do not get any errors in the log files, then Solr is running correctly.
Configure an IOC container
In Sitecore 8.2, Update 1, and later you do not have to install an IOC container. Sitecore already has a default Solr provider. The following information is only applicable if you need to use another implementation.
The Sitecore Solr provider uses an IOC (Inversion of Control) container so that all the elements inside it can be swapped without re-compilation. The default Sitecore installation includes a default implementation of the Solr connector (SolrNet.dll).
If you need to use another IOC, download the Solr support package for your version of Sitecore:
- For Sitecore 8.2 Initial Release, download from dev.sitecore.net (in the Additional tools section).
- For Sitecore 8.2 Update-1 and later, download from the Sitecore/Solr.SupportPackage repository on GitHub.
This package contains files that you must copy to the /bin folder of your installation. You can also acquire these packages via NuGet.
The following versions are currently verified, but later versions may also work:
- Castle Windsor v18.104.22.168
- AutoFac v2.5.2
- Ninject v3.0.0
- StructureMap v2.6.2
- Unity v2.1.505
These projects are open source and updated regularly. You might have to request a specific version of the container from NuGet using the –Version switch in the NuGet command line.
Select the correct support DLL files
When you choose a suitable IOC container, ensure that you include the correct support DLLs in the bin directory alongside the DLLs installed for the container.
Depending on your container, ensure that you also copy the following DLL files into the /bin folder:
Configure Sitecore to work with Solr
Follow the steps in this section to configure Sitecore to work with Solr.
Note Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during runtime.
Do not make changes directly to the configuration files. Instead, you must create a patch file that performs the required changes during runtime.
Enable the Solr Config File
Your website Include folder contains several configuration files. Lucene search is enabled by default. If you want to use Solr, you normally disable the Lucene search config files and enable the Solr config file (although it is technically possible to use Lucene for some indexes and Solr for other indexes). This enables Solr integration and gives you access to all the Solr specific configuration settings.
- Navigate to the website Include folder:
- Disable the following Lucene configuration files by adding
.exampleto the file name extension:
- Enable the
Sitecore.ContentSearch.Solr.*.configfile by removing
.examplefrom the file name.
Solr specific settings
The following Solr specific settings can be found in the
- Specifying a Solr Service Address
This setting tells Sitecore where the Solr server is located. Sitecore appends the core name so only the base address needs to be supplied.
<setting name="ContentSearch.Solr.ServiceBaseAddress" value="http://localhost:8983/solr" />
- Enabling a Search Provider
This setting tells Sitecore that Solr is enabled and so attempts to connect to the Solr server the next time the index is accessed. If it cannot connect you get an error. To disable, set this back to Lucene, which was the default setting.
<setting name="ContentSearch.Provider" value="Solr" />(Default: “Lucene”)
- Maximum Number of Search Results
This is a global setting found in the Sitecore.ContentSearch.config file.
This setting contains the maximum number of documents to retrieve on a single request if a limit has not been specified in the query, for example, Take(10). It is important to remember, for performance reasons, when querying how many results will be returned from the query being run and to handle them correctly, for example by using paging.
<setting name="ContentSearch.SearchMaxResults" value="500" />
- Enabling Batch Mode
When an item is indexed the composed document is saved to the search index. When the default Lucene provider is enabled then each write is being flushed to a file on the local disk. When a document is written using the Solr provider the update has to travel over a network.
When an index is rebuilt a large number of document updates are created, this could result in a lot of network traffic which is not very efficient. Therefore using batch can help to optimize the update process as your indexes grow in size.
<setting name="ContentSearch.Update.BatchModeEnabled" value="true" />
<setting name="ContentSearch.Update.BatchSize" value="500" />
Batch mode (enabled by default) takes these document updates and only flushes to the Solr server when the batch has reached a certain size.
As your index grows you may want to increase this batch size to gain the most out of this process.
Specify an IOC container
Solr provider is ready to use. However, if you decide to use a third-party IOC for Solr configuration, you must replace the default connector with the one that has been implemented for the chosen IOC. You do this in the
Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config configuration file and replace the default processor in the
<initialize> pipeline with a specific one.
To replace the default connector, for example, to use Castle Windsor:
- In your \App_Config\Include folder, locate the
- Open the file for editing and find the
- Replace the processor below:
<processor type="Sitecore.ContentSearch.SolrProvider.Pipelines.Loader.InitializeSolrProvider, Sitecore.ContentSearch.SolrProvider"/>
with the following processor:
<processor type="Sitecore.ContentSearch.SolrProvider.CastleWindsorIntegration.WindsorInitializeSolrProvider, Sitecore.ContentSearch.SolrProvider.CastleWindsorIntegration"/>
This registers the IOC (inversion of control) components for Castle Windsor, enabling Solr integration to work correctly.
Alternatively, you can replace the default processor with a reference to one of the following IOC containers:
Rebuild the search Indexes
Before you can start using the Solr indexing system, you must re-index Sitecore content.
To rebuild the Sitecore search indexes:
- In the Control Panel, and click Indexing manager.
- Select Select all, and then click Rebuild.