OOTB we do not search against long description, short description is queried against OOB. Although long description was added to the index in FEP3 we do not search against it.
If your business has a need to include in the search results a term found in long description you may implement the following changes to the schema.xml and wc-search.xml.
1. Set indexed="true" for long description in schema.xml as follows:
Catentry's description: map to table CATENTDESC
<field name="name" type="wc_text" indexed="true" stored="true" multiValued="false"/>
<field name="shortDescription" type="wc_text" indexed="true" stored="true" multiValued="false"/>
<field name="longDescription" type="wc_text" indexed="true" stored="true" multiValued="false"/>
2. In wc-search.xml add <_config:field name="longDescription"/> to the default search profile. OOB "IBM_findCatalogEntryByNameAndShortDescription" search profile is used when searching on the store front, so the field "longDescription" would be added as follows:
This profile inherits all the elements defined in IBM_Global profile.
<_config:profile name="IBM_findCatalogEntryByNameAndShortDescription" extends="IBM_findCatalogEntryByName">
After the above changes, long description will be included in the final solr query and will be searched against when a search is performed on the store.
- The schema.xml that you should be changing is the one located on the server that's queried during search.If you have a remote solr server, the schema.xml that's on the remote solr server that accepts query requests should be edited with the change. For the change to take effect the solr server should be restarted.
- The wc-search.xml that you should be changing is the one located at /opt/IBM/WebSphere/AppServer/profiles/<profile_name>/installedApps/WC_<profile_name>_cell/WC_<profile_name>.ear/xml/config/com.ibm.commerce.catalog-ext on the WCS server. The Commerce Server then should also be restarted for the change to take effect.