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.
Performance
Topics in the Performance section describe the means by which to plan, implement, test, and re-visit the optimization of HCL Commerce site performance.
Measurement
As each deployment of HCL Commerce is different, a measured approach to modifying your defaults must be taken to successfully tune your site. The following collection of topics provides details on how to measure and troubleshoot site performance.
Performance Measurement tool
As a developer, you can use the Performance Measurement tool to gather performance data on a running application to help you identify any performance bottlenecks. You can use this tool in both your development environment to test operation performance, and in your production environment to analyze the actual performance of an operation. When you run this tool, you can generate different reports to help you identify operations that impact performance and determine how to improve caching performance.
Execution reports
You can use the Performance Measurement tool to generate execution reports. Execution reports include the measurements for a single execution stack.

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.
- Getting started
  HCL Commerce has different advantages for business users, administrators and developers. HCL Commerce targets each of these roles with a tailored set of offerings so that each of your users can get maximum benefit.
- Installing and deploying
  Learn how to install and deploy HCL Commerce development environments and HCL Commerce production environments.
- Migrating
  Before you migrate to HCL Commerce Version 9.1, review this information to help plan and execute your migration.
- Operating
  Topics in the Operating category highlight tasks that are typically performed by business users, customer support representatives, to complete their day-to-day tasks in the operation of the HCL Commerce site.
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using HCL Commerce in combination with other products.
- 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.
- Customizing
  The topics in the Customizing section describe tasks performed by an application developer to customize HCL Commerce.
- Tutorials
  HCL Commerce provides many tutorials to help you customize and understand your HCL Commerce instance and stores.
- Samples
  Topics in the Samples category highlight the various samples that are provided with HCL Commerce.
- Compliance
  The following section describes how you can leverage HCL Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of HCL 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 HCL Commerce site performance.
  - Methodology
    Like site security, a proper approach to site performance requires planning, execution, testing, monitoring, and maintenance. The following collections of topics describe each phase of this process, and contain the recommended considerations, and best practices for getting the most out of your HCL Commerce deployment.
  - Setting cache providers
    Starting with HCL Commerce Version 9.1, all caches are automatically configured to use the HCL Cache. However, the cache provider for each cache can be set to use the DynaCache provider, or the WebSphere Extreme Scale DynaCache provider.
  - HCL Cache
    The HCL Cache integrates with DynaCache and improves performance and scalability with features such as remote caching, real-time monitoring, and auto-tuning capabilities.
  - Experiments considerations
    When experiments that you have created in WebSphere Commerce Accelerator are running in the store, the Scheduler launches a job that determines whether any of the current experiments have expired. The job compares the expiration date specified in the experiment to the current system date. When an experiment is identified as expired, its status is updated in the database, and the experiment is prevented from displaying to customers.
  - Website performance tuning
    There are four steps for evaluating performance of an HCL Commerce website that is based on Transaction server.
  - Tuning the price rule object cache
    You can improve performance by changing the size of the cache used to store price rule business objects during storefront runtime.
  - Data Load utility performance tuning
    Scheduled Data Load utility jobs can affect HCL Commerce performance. You can reduce the impact of this process by tuning the data load performance appropriately for your implementation.
  - Workspaces performance tuning
    Workspaces use database views instead of tables to retrieve data. Retrieval of underlying data might be more time-consuming because of the complexity of SQL statements that are used in workspace view definitions.
  - Configuring custom DynaCache objects in WebSphere Liberty
    The WebSphere Liberty profile, can be configured with distributed map for the custom cache objects. To configure the custom cache objects for WebSphere Liberty in Runtime and Development, follow the steps outlined below:
  - Configuring custom DynaCache objects in HCL Commerce
    Define the custom cache in WebSphere Application Server. You can then use the cache name to store and retrieve the cache objects.
  - Preparing HCL Commerce for the peak shopping periods
    When preparing for peak shopping periods, such as the holiday season, use the following best practices to effectively manage your HCL Commerce environment for peak efficiency, and to ensure that your HCL Commerce site is ready to handle the increased load.
  - OneTest Performance sample script for Emerald B2C Store
    HCL OneTest provides software testing tools to support a DevOps approach: API testing, functional testing, UI testing, performance testing and service virtualization. This approach aids in test automation, for earlier and more frequent discovery of errors.
  - Ruby store performance tuning
    Performance tuning in the Ruby store is important for delivering the best browsing experience. If your storefront is slow, you can improve its performance by checking and optimizing the following points.
  - Docker performance tuning
    The following performance tuning information can be used to help you configure your containerized HCL Commerce environments for optimal performance.
  - Thread Monitor - Yaml configuration file
    The Thead Monitor tool gathers thread dumps and Javacores at a configured interval, and during events such as high WebContainer/Default_Executor pool thread usage. Yaml configuration file must exist with name /SETUP/support/thread_monitor.yaml, or under the location specified with the THREAD_MONITOR_CFG environment variable.
  - Search health check
    The search health check API is used to regularly check the status of Commerce containers to make sure they are in a healthy state.
  - Elasticsearch performance tuning
    You have numerous options when tuning the performance of NiFi and Elasticsearch. The following guide introduces tools for monitoring performance and validating key tuning parameters, and provides a performance tuning strategy that you can use with the component.
  - Optimizing index build and overall flow
    Optmizations are provided full index builds and for tuning parameters. Potential improvements that can be implimented for Near Real Time (NRT) index updates are not described.
  - Monitoring the metrics
    You can use Grafana and related tools to analyze the performance of the Ingest pipeline, and Kibana to do the same with Elasticsearch.
  - Tunable setup parameters
    How you can modify the values for the tunable parameters, and some default values and how they can be improved in different circumstances.
  - Scaling and hardware requirements
    You can achieve additional capacity by implementing or extending pod clustering on Elasticsearch, NiFi, or both. You can also consider the hardware footprint and key resources that impact the processing and index creation speed.
  - Elasticsearch with dedicated Auth and Live nodes
    For production environments, Elasticsearch is recommended in a clustered configuration for high availability and scalability considerations.
  - Recommended parameter values
    Two configurationsof the NiFi tunable parameter values are presented, a minimal and an optimal value.
  - Measurement
    As each deployment of HCL Commerce is different, a measured approach to modifying your defaults must be taken to successfully tune your site. The following collection of topics provides details on how to measure and troubleshoot site performance.
    - Extensible metrics for monitoring and alerts
      You can use the HCL Commerce Version 9.1 Metrics Monitoring framework with built-in performance dashboards, or build your own. The monitoring data are collected using Micrometer and are provided in the industry-standard Prometheus format. This means you can use them with many different tools. HCL provides a set of Grafana dashboards to get you started.
    - Performance Measurement tool
      As a developer, you can use the Performance Measurement tool to gather performance data on a running application to help you identify any performance bottlenecks. You can use this tool in both your development environment to test operation performance, and in your production environment to analyze the actual performance of an operation. When you run this tool, you can generate different reports to help you identify operations that impact performance and determine how to improve caching performance.
      - Using the Performance Measurement tool
        The Performance Measurement can help you analyze your cache settings and improve performance.
      - Performance reports
        You can use the Performance Measurement tool to generate performance reports for operations. You can use performance reports to measure the impact that your caching practices have on your system performance. You can then analyze these reports to help you adjust your caching to improve performance.
      - Stack reports
        You can use the Performance Measurement tool to generate stack reports. Stack reports include the measurements for the stack of operations that are used when you run a sample operation.
      - Execution reports
        You can use the Performance Measurement tool to generate execution reports. Execution reports include the measurements for a single execution stack.
      - Caller reports
        You can use the Performance Measurement tool to generate caller reports, which identify the source of the calls to run an operation. With these reports, you can analyze operations and identify the sources for numerous calls for the operation to run.
    - Analysis with IBM Cloud tools
      A suite of IBM Cloud tools is available to diagnose the overall health and performance of your site. Run diagnostics and upload various metric containing files to get guided feedback and analysis to help you understand your site configuration and performance.
    - Performance logger
      The performance logger produces trace information about the response time when HCL Commerce calls out to an external system. The trace can be used by a monitor to measure response times.
    - Data recording: Improving runtime performance
      Two options are provided which can improve runtime performance regarding the recording of user behavior data.
  - Emerald REST Caching On TS Server for Commerce 9.1
    Emerald Store is powered by the REST framework, and the cache is implemented using a REST servlet.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with HCL Commerce, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the HCL Commerce reference documentation.

Execution reports

You can use the Performance Measurement tool to generate execution reports. Execution reports include the measurements for a single execution stack.

Note: When you are reviewing an execution report, use an XML editor so that you can collapse and expand XML elements to make analyzing the report easier.

Execution reports are similar to stack reports, with the following differences:

Each server request generates one execution report.
Each execution report contains a single execution stack from the start of the server request to its completion.

If a servlet request is called 20 times and each time the request executes two different commands (A and B), The Performance Measurement tool generates the following reports:

Three stack reports. One for the servlet request, command A, and command B.
20 execution reports that show the execution stack for each of the 20 executions.

You can use the information in this report to help troubleshoot potential performance problems for a single execution stack.

Each node within an execution report can contain the following information for each operation execution:

duration: Duration of the operation in milliseconds
name: Name of the operation.
identifier: Unique identifier for the operation execution. This value is used to correlate parent-child relationships.
parent-identifier: Unique identifier for the parent operation execution. This value is used to correlate parent-child relationships.
start-time-nano: Operation start time in nanoseconds. This nanosecond value is relative to the end-time-nano parameter value.
end-time-nano: Operation end time in nanoseconds. This nanosecond value is relative to the start-time-nano parameter value.
duration-nano: Operation duration in nanoseconds.
result-size: Size of the result in bytes.
cache-enabled: Indicates whether the cache was enabled while the operation ran.
from-cache: Indicates whether the operation fetched the result from the cache while the operation ran. The values can be true or false.
unique-key: Unique key that was used while the operation ran. This key is formed by concatenating the parameter names and values within a single string.