Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
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.
Developing stores
Commerce+ offers customizable features for storefronts using the Next.js framework. Commerce+ supports headless commerce to use any front end storefront.
Remote store toolkit
You can migrate store development environments to Open Liberty and a modern Java Development Kit (JDK) by using Commerce+ remote store dev kit migration to standardize environments and minimize reliance on legacy tooling.

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.
- 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.
  - Customizing
    The topics in the Customizing section describe tasks performed by an application developer to customize Commerce+.
  - Developing stores
    Commerce+ offers customizable features for storefronts using the Next.js framework. Commerce+ supports headless commerce to use any front end storefront.
    - Stores in Commerce+
      Commerce+ supports different types of stores. The assets of these stores can be edited using the Commerce Lab.
    - Ruby storefronts
      The Ruby storefront offers customizable features for storefronts using the Next.js framework. It uses the headless store data template and supports business-to-consumer (B2C) and business-to-business (B2B) use cases. The store includes pages for browsing, shopping, checkout, and account management, and uses Elastic for search functions.
    - The Customer Service Hub
      The Customer Service hub, also known as the CSR tool, provides your Customer Service Representatives (CSRs) an authority to manage Accounts and Orders for a selected store.
    - Remote store toolkit
      You can migrate store development environments to Open Liberty and a modern Java Development Kit (JDK) by using Commerce+ remote store dev kit migration to standardize environments and minimize reliance on legacy tooling.
      - Get started
        Set up the HCL Commerce+ remote store toolkit to create a local development environment for customizing and testing the Commerce+ remote store.
- 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.

HCL Commerce+ remote store toolkit

You can migrate store development environments to Open Liberty and a modern Java Development Kit (JDK) by using Commerce+ remote store dev kit migration to standardize environments and minimize reliance on legacy tooling.

This process updates store development environments by replacing legacy dependencies with a supported Open Liberty runtime and a modern Java Development Kit (JDK). This repeatable framework helps you adopt current development tools, simplifies environment setup, and prepares stores for future Commerce+ releases.

Benefits

Standardize store development environments
Reduce dependencies on legacy toolchains
Support modern IDEs and developer workflows
Improve deployment consistency and environment stability
Simplify onboarding paths for new developers
Provide a clean foundation for future Commerce+ upgrades
Reduce long-term maintenance and operational costs

Migration overview

This migration blueprint contains the components and configuration changes required to transfer an existing store development environment to Open Liberty and a modern JDK. Use this architecture as a reference when migrating legacy HCL Commerce+ environments to the Commerce+ development model.

The migration documentation includes:

Required software and prerequisites
Migration steps for Open Liberty
Configuration changes for the modern JDK
Required scripts and deployment updates
Validation procedures to verify a successful migration
Troubleshooting guidance for common migration issues

Standard operating procedure (SOP)

This documentation serves as the standard operating procedure (SOP) and establishes a centralized source of truth for performing and validating migrations. The SOP contains the following elements:

Technical steps and migration commands
Configuration updates for Open Liberty and a modern JDK
Verification procedures to confirm that the migrated environment functions correctly
Best practices for maintaining the migrated development environment