Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
Performance
Topics in the Performance section describe the means by which to plan, implement, test, and re-visit the optimization of Commerce+ Transaction Server 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 Commerce+ Transaction Server deployment.
Tuning
A Commerce+ Transaction Server deployment consists of multiple components working together to deliver the e-commerce experience. By default, each component is set up for baseline performance, but individual optimizations can enhance overall efficiency. The following topics outline how to fine-tune these components for improved performance.
Tuning best practices
Use these tips and best practices to help you successfully work with Workspaces and Commerce Search, deploy Commerce+ Transaction Server, and develop reusable and easily maintainable JSP pages within the Commerce+ Transaction Server store development framework.

Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
- Overview
  Welcome to the HCL Commerce+ Transaction Server overview. Explore these feature overviews to learn how Commerce+ Transaction Server 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+ Transaction Server. 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+ Transaction Server.
- 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+ Transaction Server site.
- Extending
  Using Commerce+ Transaction Server'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+ Transaction Server 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+ Transaction Server 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 Commerce+ Transaction Server deployment.
    - Design phase
      During the design phase of your project, it is important to consider performance priorities. It is important to design a solution that has a good balance of features and performance consideration, build a performance test environment, and begin to deploy tools that are required to support your performance strategy. It is also important to identify architecture limitations that might change a non-functional requirement.
    - Development phase
      During the development phase, it is important to measure the response time of business critical steps in the development environment.
    - Testing phase
      During the testing phase, it is important to start with simple, common test cases and gradually go to more complex scenarios and environment configurations. Other priorities include measuring the performance of the application as load scales up to projected peak and identifying and resolving the root causes of resource constraints and application bottlenecks.
    - Maintenance phase
      Post-launch, during the maintenance phase, instrument and monitor performance indicators in the production environment to enable the team to proactively identify and address potential issues before users are affected. Priorities also include fostering communication between marketing, performance, and operation teams to be better prepared for promotional events. And using the data that is captured from production to optimize planning for future marketing and promotional activities.
    - JDBC_MONITOR_ENABLED parameter
      JDBC Monitor (Java Database Connectivity) is a debugging tool that allows you to examine SQLs that are executed in any application for performance and troubleshooting purposes. This document provides the installation steps for JDBC Monitor.
    - Tuning
      A Commerce+ Transaction Server deployment consists of multiple components working together to deliver the e-commerce experience. By default, each component is set up for baseline performance, but individual optimizations can enhance overall efficiency. The following topics outline how to fine-tune these components for improved performance.
      - Commerce+ Transaction Server performance tuning
        Commerce+ Transaction Server by itself does not have too many performance tuning knobs. Consider Commerce+ Transaction Server to be a Java EE application that consists of business logic and relies on Open Liberty Server to provide the core function to make Commerce+ Transaction Server perform well.
      - Tuning best practices
        Use these tips and best practices to help you successfully work with Workspaces and Commerce Search, deploy Commerce+ Transaction Server, and develop reusable and easily maintainable JSP pages within the Commerce+ Transaction Server store development framework.
        Workspaces best practices
        When you use workspaces, you should have strong business processes in place to prevent the situations outlined in Workspaces limitations and restrictions.
      - Search performance tuning
        Consider these search performance tuning hints and tips when you administer Commerce Search.
      - Database performance tuning
        The database is usually one of the potential areas for bottlenecks that makes Commerce+ Transaction Server unable to scale and perform well. It is therefore crucial that the database is tuned appropriately for your implementation.
      - Promotion performance tuning
        Commerce+ Transaction Server provides business users with multiple features and functionality to help enhance developing promotions for a store. However, planning is required to use the various techniques available to achieve and maintain wanted site performance.
      - Performance improvements for large shopping cart
        The following shopping cart commands have been optimized for performance: OrderItemAdd, OrderItemUpdate, OrderItemDisplay. These changes optimize the commands so that performance gains can be achieved, especially in cases where shopping carts typically contain hundreds of order items.
      - Enabling and disabling large shopping cart performance enhancements
        The large shopping cart performance enhancement consists of many different elements, which can be enabled or disabled separately. The enhancements are disabled by default.
      - Enabling and disabling the optimized large shopping cart order commands
        To improve the performance of large shopping carts, you can optimize the OrderItemAdd, OrderItemUpdate, OrderItemDisplay, and OrderCalculate commands.
      - Enabling and disabling the optimized tax command
        The optimized tax command provides improved performance for sites that encounter shopping carts that include hundreds of order items or more.
      - Enabling and disabling the optimized shipping calculation command
        The optimized shipping calculation command provides improved performance for sites that encounter shopping carts that include hundreds of order items or more.
  - OpenTelemetry
    OpenTelemetry is an open source framework for gathering performance traces, metrics and logs from your HCL Commerce+ Transaction Server system.
  - 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 Commerce+ Transaction Server 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 Commerce+ Transaction Server 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.
  - 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.
  - 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.
  - Tuning ingest performance in Elastic part II
  - Recommended Parameters for NIFI and Elastic
    You can run your Elastic and NiFi environments using the default settings, which provides a minimal resource set. For best performance, tune your configuration or use the recommended parameters for CPU, memory and system resources.
  - Measurement
    As each deployment of Commerce+ Transaction Server 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.
  - REST caching on TXN server
    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 Commerce+ Transaction Server, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the Commerce+ Transaction Server reference documentation.

Tuning best practices

Use these tips and best practices to help you successfully work with Workspaces and Commerce Search, deploy Commerce+ Transaction Server, and develop reusable and easily maintainable JSP pages within the Commerce+ Transaction Server store development framework.