Home
Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels. Business users can also use AI enabled content management capabilities.
Administering
Topics in the Administering category highlight tasks that are typically performed by the Site Administrator, to support daily operations of the HCL Commerce site.
Logging services
HCL Commerce provides facilities for logging. For existing customers, ECTrace and ECMessage are still supported. For new implementations, use the WebSphere Application Server recommendation for logging and tracing.
Trace components
Use the following trace strings and logger information to gather the information that you need to troubleshoot problems.
… for search cache invalidation issues
Prepare the following MustGather information before you call HCL Support to help with the troubleshooting process.

Collecting Solr based search-related MustGather data for search cache invalidation issues

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

Procedure

Configure the following trace specifications.
- In the Search server Docker container:
```
*=info:com.ibm.commerce.foundation.*=all: com.ibm.commerce.search.*=all: org.apache.solr.*=all: com.ibm.commerce.solr.*=all
```
  For information about how to set trace strings, Configuring logging for the Search Server.
For information about how to configure trace strings, see
- Configuring logging for the Search Server
Reproduce the problem.

Record the specific steps that you used to reproduce the problem and any details that might be relevant.
Run the following database queries to collect the necessary information from your database (output results in CSV format).
```
SELECT * FROM CACHEIVL WHERE INSERTTIME > (PLS SET TO some time before current time as the table is very big)
```
Note: To monitor cache content or run cache invalidation instance, see Enabling cache monitoring.