Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
Administering
The site administrator performs the tasks needed to support day to day operations of the Commerce+ site.
Logging services
Commerce+ maintains a detailed set of logs related to a variety of processes and functions. These logs are available upon request.
Configuring logging for runtime environments
You can manage logging and tracing configurations in your runtime environments by using Run Engine commands.
Logging services
Commerce+ maintains a detailed set of logs related to a variety of processes and functions. The Catalog import service uses Logback for logging, integrated with Spring Boot. Logging settings are configured in the logback-spring.xml file.

Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
- Overview
  Welcome to the HCL Commerce+ overview. Explore these feature overviews to learn how Commerce+ operates. Refer to the related links listed at the end of each topic to access expanded product documentation.
- Deploying
  This section provides details on deploying HCL Commerce+. It explains how to download the Docker images and Git bundles that comprise the product, how to create a minimal environment, and how to plan for a full deployment. It details supported software versions, patches, and configurations to ensure the platform performs well.
- Migrating
  The following topics show how to migrate an existing HCL Commerce Version 9.1 environment to Commerce+. The process consists of an initial migration of your database contents. This is followed by a code migration. Both are fully described.
- Operating
  The topics in this section focus on tasks that are performed by business users, marketers, and customer support representatives to connect with partners and attract and satisfy customers.
- Administering
  The site administrator performs the tasks needed to support day to day operations of the Commerce+ site.
  - Member groups
    A member group is a grouping of members - users, organizations, or other member groups - used for various business purposes. Two kinds of member groups exist: implicit and explicit. An implicit member group contains users that share common attributes and are therefore considered members of a specific member group. An implicit member group specifies criteria or attributes that users must satisfy in order to be considered members of that member group. You can also explicitly exclude certain users although they satisfy the criteria. An explicit member group contains explicitly assigned users, who may or may not share common attributes. A member group can be both implicit and explicit at the same time.
  - Inventory management
    Use the HCL Commerce+ Inventory to manage your inventory and access your Inventory Locations (ILs), where your inventory is physically stored and is delivered or shipped from.
  - Approvals
    Accurate, secure transactions require that a second individual approve some electronic marketplace actions before they proceed. This individual, called an approver, can accept or reject requests to perform a specific action. During the organization registration process, the organization administrator selects the business processes for which they want to enable approval. This is done by signing up for the appropriate approval member group during membership registration. The organization administrator also populates the approver member groups. Only users within these groups have the authority to accept or reject requests to perform those actions for which approval has been enabled.
  - System Administration
    Commerce Lab allows you to manage transport, messages, scheduler, Connectors, registries, and security policies.
  - Staging environment
    An Commerce+ staging environment is a runtime environment where business and technical users can update and manage store data and preview changes. The changes can then be propagated to the production environment.
  - Workspaces
    Workspaces provide a powerful and flexible way to manage and preview changes to your e-commerce website without affecting the live production environment.
  - Commerce+ database
    As a site administrator, maintain the Commerce+ database and ensure that any Commerce+ utilities and processes that load and retrieve data from the database is configured to connect to the database properly.
  - Extracting and loading data
    Commerce+ provides utilities for preparing and loading data into a Commerce+ database. The loading utilities are flexible and you can continue to use these utilities when you customize the Commerce+ schema.
  - Administering Search
    HCL Commerce+ Search provides the core search capability for Commerce+, enabling product indexing and retrieval for customer queries across the storefront. It supports guided navigation, landing pages, and dynamic merchandising, helping shoppers quickly find relevant products while giving merchandisers tools to influence search results.
  - Logging services
    Commerce+ maintains a detailed set of logs related to a variety of processes and functions. These logs are available upon request.
    - Configuring logging for runtime environments
      You can manage logging and tracing configurations in your runtime environments by using Run Engine commands.
      - Configuring logging for the Transaction server
        You can configure logging in the Transaction server Docker container by using one of two methods.
      - Configuring logging for the Quote server
        You can configure logging in the Quote Server Docker container by running the set-trace-specification script.
      - Configuring logging for the Approval server
        You can configure logging in the Approval server Docker container by running the setRuntimeTraceSpecs script.
      - Configuring logging for Kubernetes
        You can configure centralized logging for your Kubernetes deployment using Elastic, Fluentd, and Kibana (EFK).
      - Logging services
        Commerce+ maintains a detailed set of logs related to a variety of processes and functions. The Catalog import service uses Logback for logging, integrated with Spring Boot. Logging settings are configured in the logback-spring.xml file.
    - Trace components
      Use the following trace strings and logger information to gather the information that you need to troubleshoot problems.
  - Business events
    Each time that a command triggers a business event, a record is added to the BUSEVENT database table to persist data from the event. Event listeners and external systems (such as the Marketing component, a back end order management system, or an external analytics system) can use this data to perform further processing.
  - Business Object thresholds
    Applying limits on business operations reduces the risk of system attacks where unbound conditions might result in system failures.
- Extending
  Using Commerce+'s xC programming model, you can use HCL-provided extension points to extend existing Commerce logic. You can implement these extensions with the xC Customization toolkit provided by HCL. Commerce+ also provides Packaged Business Capability integrations that extend the product's reach and functionality.
- Securing
  These topics describe the security features of Commerce+ and how to configure these features.
- Performance
  Topics in the Performance section describe the means by which to plan, implement, test, and re-visit the optimization of Commerce+ site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with Commerce+, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the Commerce+ reference documentation.

Catalog import logging services

Commerce+ maintains a detailed set of logs related to a variety of processes and functions. The Catalog import service uses Logback for logging, integrated with Spring Boot. Logging settings are configured in the logback-spring.xml file.

Default logging level: By default, the logging level for all com.hcl.* packages is set to DEBUG.
Note: This level should be changed to INFO for production environments.

Enabling TRACE logging for specific packages

To enable more granular logging for a specific package, you can configure TRACE-level logging in the logback-spring.xml file. For example, to enable TRACE logging for the com.hcl.catalog.controller package, add the following entry:
```
<logger name="com.hcl.catalog.controller">
    <level value="TRACE" />
</logger>
```
After updating the configuration, restart the catalog data service for the changes to take effect.

Dynamically enabling TRACE logging (No restart required)

You can enable TRACE logging for a specific package at runtime using Spring Boot Actuator’s loggers endpoint.
```
POST {{catalog-url}}/catalog/api/actuator/loggers/com.hcl.catalog.controller
Content-Type: application/json

{
  "configuredLevel": "TRACE"
}
```
This allows dynamic logging changes without restarting the catalog server.

Listing logging levels

To view the current logging levels for all packages on the catalog server, call the following endpoint:

GET {{catalog-url}}/catalog/api/actuator/loggers

Method-level entry and exit logging

The Catalog PBC uses Spring (Aspect-Oriented Programming) to trace method-level entry and exit points.

To enable this tracing, set the logging level to TRACE for the com.hcl.catalog.logging. package.
If you enable TRACE logging for a broad package, such as com.hcl.catalog, the configuration includes the com.hcl.catalog.logging subpackage.
If you enable TRACE logging for a narrower package such as com.hcl.catalog.service or com.hcl.catalog.batch, you must also explicitly enable TRACE logging for com.hcl.catalog.logging.
Note: The system disables method-level tracing. The AOP engine remains active, but you must enable TRACE logging to view trace output. If you do not configure TRACE logging, the system does not generate method entry and exit logs.