Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
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.
Minimal environment
Best practice for installing HCL Commerce+ is to start with a preconfigured 'minimal environment.' To install Commerce+, first, set up and test the minimal environment, then plan for your production environment using your own organization's IT and business experts.
Users and privileges
You define your users and their privileges in the Docker containers using the default Helm chart deployed on Kubernetes. It provides guidance to ensure compatibility with the default non-root user setup, focusing on a minimal test environment as a starting point.

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.
  - Software stack
    The following table provides a list of generally available (GA) software levels, fixes, and settings for the latest HCL Commerce+ release.
  - Downloading
  - Minimal environment
    Best practice for installing HCL Commerce+ is to start with a preconfigured 'minimal environment.' To install Commerce+, first, set up and test the minimal environment, then plan for your production environment using your own organization's IT and business experts.
    - Resources
      The minimal environment is designed for feature and customization validation, such as testing with the Ruby reference store, and assumes the default configuration. It is not intended for performance testing, capacity planning, or production use. For production environments, resource needs will vary based on business requirements such as catalog size or customizations, and should be assessed separately with load testing.
    - Installation
      Use Kubernetes to deploy the basic HCL Commerce+ environment with the default configuration provided by HCL.
    - Users and privileges
      You define your users and their privileges in the Docker containers using the default Helm chart deployed on Kubernetes. It provides guidance to ensure compatibility with the default non-root user setup, focusing on a minimal test environment as a starting point.
  - Commerce+ environment
    Kubernetes is the default tool for deploying a live HCL Commerce+ production site. HCL provides all the required applications as Docker images for you to use in a configuration of your choice. Also included are Kubernetes Helm Charts.
  - xC development environment
    HCL Commerce+ includes an xC service that you can use to create custom plugins .
  - References
    The following topics contain information that you can use in planning and implementing custom production and development environments.
- 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.
- 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.

Defining container users and privileges

You define your users and their privileges in the Docker containers using the default Helm chart deployed on Kubernetes. It provides guidance to ensure compatibility with the default non-root user setup, focusing on a minimal test environment as a starting point.

Default User Configuration

Default User: All HCL Commerce+ containers run as the non-root user comuser (UID 1001) by default, as configured in the default Helm chart.
Purpose: Enhances security by restricting container access to system-level resources in Kubernetes.
Scope: Applies to all HCL Commerce+ containers (ts-app, store-web, nextjs-app, etc.) in the deployment.

Key considerations for HCL Commerce+ containers

Custom code permissions

Ensure that custom code files (for example, for xc-app) are owned by comuser (UID 1001) in the Helm deployment.
Use /home/comuser or /tmp for temporary files. Avoid root-owned paths like /root.
Verify file permissions allow comuser read/write access when mounting into containers.

Utilities in the ts-utils container

Set ownership of utility input/output files to comuser in the default Helm values.yaml configuration file, or inside mounted volumes. Ensure mounted files (e.g., via Kubernetes volumes) have comuser permissions for seamless operation.
Confirm accessibility by comuser to avoid permission errors during deployment.
Tools like dataload in ts-utils require configuration and data files owned by comuser.

Building custom Docker images

Use comuser as the default user in custom images for HCL Commerce+.
For privileged tasks (such as installing tools), switch to USER root in the Dockerfile, then revert with USER comuser.
Example: COPY --chown=comuser:root ./custom-script /SETUP/bin/