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 store preview issues
Prepare the following MustGather information before you call HCL Support to help with store preview issues.

Collecting MustGather data for store preview issues

Prepare the following MustGather information before you call HCL Support to help with store preview issues.

Procedure

Configure the following trace strings.

In the Transaction server Docker container

com.ibm.commerce.foundation.logging.ServiceLogger=finest: com.ibm.websphere.commerce.WC_BUSINESSCONTEXT=all: com.ibm.websphere.commerce.WC_SERVER=all: com.ibm.commerce.content.preview.*=all: com.ibm.commerce.context.preview.*=all

For information about how to set trace strings, see Configuring logging for the Transaction Server.

Reproduce the problem.

Record the specific steps that you used to reproduce the problem and any details that might be relevant.
Collect the following files.
- From the Transaction server Docker container:
  - /opt/WebSphere/AppServer/profiles/default/logs/server1/SystemOut*.log
  - /opt/WebSphere/AppServer/profiles/default/logs/server1/trace*.log