The solrconfig.xml controls how Solr behaves by mapping requests to
different handlers. One index can be represented as one core. If you want to use multiple indexes,
for example, a book of recipes and a book of countries, these different indexes or books represent
different cores. The solrconfig.xml contains most of the parameters for
configuring Solr. It defines how search requests are managed, and how to manipulate data for the
user.
The Solr configuration file is stored in the following location:
- solrhome/MC_masterCatalogId/locale_name/indextype/conf/solrconfig.xml
Solr exposes various components as services. These components are managed with the following
RequestHandler components:
- Query handler
- A handler that is implicitly mapped to the /select path, unless another
name is explicitly used instead.
- Replication handler
- A handler that is mapped to the /replication path. This handler controls
index replication between the master and subordinate servers.
- Data import handler
- A handler that is mapped to the /dataimport path. It is used to load
structured content using the Data Import Handler (DIH). It handles both full and incremental (delta)
imports.
Configurable properties for search
In the Solr configuration file, the search properties are grouped into sections. For each
property, you can read a description, and examples for some of the more complex properties. The
following table summarizes the types of configurable properties in the files. Refer to the comments
within the file for more details.
Note: You cannot extend the Solr configuration file. Ensure that
you track the changes you make to the file, so that you can reapply your changes when you update
WebSphere Commerce search to a later feature pack version.
In the Solr configuration file, you can
configure the following search-related properties:
| Search property |
Purpose of property |
| Update processor chain |
Contains properties for the update processor chain
- wc-conditionalCopyFieldChain
- When enabled, it copies the source fields into the target field if the conditions are met. The
target field is tokenized with the store and catalog. For example, it creates store and
catalog-specific spell check columns to be used by the term component.
|
