HCL Commerce Version 9.1.2.0 or later

Collecting Elasticsearch based search-related MustGather data for Search Term Associations (STA)

Prepare the following MustGather information before you call HCL Support to help with the troubleshooting process.

Procedure

  1. Log into the Query server Docker container. Edit the configuration file /profile/apps/search-query.ear/search-query.war/WEB-INF/classes/logback.xml. Update the trace level parameter from "error" to "all."
    <logger name="com.hcl.commerce.search" level="all" additivity="false">
  2. The scanPeriod parameter determines how long you will have to wait for your changes to be picked up. If you have set this parameter to a high number, you can restart the Query server in order to have your changes picked up immediately. A representative value for the parameter is shown below.
    <configuration scan="true" scanPeriod="30 seconds"> 
  3. Reproduce your search term association issue. Record the specific steps that you used to reproduce the problem and any details that might be relevant.
  4. Collect the trace files generated in the following directory.
    /app/ESQueryService/logs/​ 
  5. Save the response to the following REST API.
    GET http://{{elasticsearch_hostname}}​:30200/{{environment_type}}.{{storeId}}.product/_settings
  6. Run the following database queries to collect the necessary information from your database (the output will be produced in CSV format).
    SELECT * FROM SRCHTERM;
    SELECT * FROM SRCHTERMASSOC;