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.
Installing and deploying
Learn how to install and deploy HCL Commerce development environments and HCL Commerce production environments.
Setting up HCL Commerce environments
Learn how to set up development, testing, and production environments, and how to update the production environment through deploying custom changes and applying maintenance.
Setting up an HCL Commerce development environment
This section describes how to set up an HCL Commerce development environment. The HCL Commerce development environment is a flexible collection of software, collectively known as HCL Commerce Developer, for developers or system administrators to develop and test stores and HCL Commerce application code.
Developer Next.js Store environment
Refer to storeseparation/tasks/ruby_downloadsdk.html for instructions on how to download the Next.js Store SDK.

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.
  - HCL Commerce assemblies
    HCL Commerce consists of HCL Commerce Enterprise, and HCL Commerce Developer, a separate offering that is used by developers of the platform. Each offering is logically divided into subpackages called electronic assemblies, or eAssemblies. An eAssembly is a group of software that is devoted to a particular platform or environment. Each eAssembly contains the individual product images for that environment, called parts. Which parts you need depends on your usage and configuration choices.
  - Downloading software
    To set up an HCL Commerce production, development, or test environment, you require the associated product software images.
  - Supported software levels, fixes, and settings
    The following table provides a list of generally available (GA) software levels, fixes, and settings for the latest HCL Commerce Version 9.1 release.
  - Hardware requirements
    The following reference provides a general guideline for the hardware capacity that is required for the HCL Commerce Version 9.1 release. This includes both full development and production environments for sites that are based on different sets of HCL Commerce solutions.
  - Setting up HCL Commerce environments
    Learn how to set up development, testing, and production environments, and how to update the production environment through deploying custom changes and applying maintenance.
    - Setting up an HCL Commerce development environment
      This section describes how to set up an HCL Commerce development environment. The HCL Commerce development environment is a flexible collection of software, collectively known as HCL Commerce Developer, for developers or system administrators to develop and test stores and HCL Commerce application code.
      - Obtaining HCL Commerce Developer software
        To set up an HCL Commerce development environment, you require associated product software images and Software Development Kits (SDKs).
      - Developer Legacy environment
        In previous iterations of HCL Commerce, all site features were developed within a single development environment. This environment was built with the HCL Commerce Developer software package. With HCL Commerce Version 9.1, this software environment has been renamed to the HCL Commerce Developer Legacy environment to more reflect its usage within the product.
      - Developer Search environment
        HCL Commerce Version 9.1 provides support for Elasticsearch by default. Use the HCL Commerce Developer Search environment to make customizations to the search solution.
      - Developer React Store environment
        HCL Commerce provides a standalone HCL Commerce Developer React Store environment. This environment uses the React Store Software Development Kit (SDK) with reference Single Page Application (SPA) Stores that are based on the Node.js react-app. The HCL Commerce Developer React Store environment is completely independent of the HCL Commerce Developer Legacy environment.
      - Developer Next.js Store environment
        Refer to storeseparation/tasks/ruby_downloadsdk.html for instructions on how to download the Next.js Store SDK.
      - Developer Tooling environment
        HCL Commerce provides a standalone HCL Commerce Developer Tooling environment Software Development Kit (SDK).
      - Developer Solr-based Nextjs Store environment
        The Orchestration service acts as a bridge between Ruby applications that can only recognize Elastic-based search formats, and Solr-based search services. If you plan to develop for Ruby applications for use with a Solr-based search solution, you must configure the Orchestration service to test your storefronts in an HCL Commerce development environment.
      - Uninstalling HCL Commerce Developer
        Uninstalling HCL Commerce Developer consists of removing HCL Commerce Developer and Rational Application Developer from your computer.
    - Setting up an HCL Commerce production environment
      You can set up your production environment however you like by using the provided Docker images for your HCL Commerce servers.
    - Default port numbers
      Review this information for the default port numbers that are used by HCL Commerce services or the component products.
  - Deploying custom changes
    With HCL Commerce Version 9.1, you can customize HCL Commerce Docker image with the source code, configurations, and the Docker container start-up logic. Learn how to build Docker images with your customized code and deploy the images (and other changes) to your Docker containers.
  - Updating HCL Commerce overview
    Learn about HCL Commerce release types, and learn how to update your custom HCL Commerce site deployments.
- 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.
- 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.

HCL Commerce Version 9.1.13.0 or later

Setting up the HCL Commerce Developer Next.js Store environment

Refer to Downloading the HCL Commerce Next.js Store SDK for instructions on how to download the Next.js Store SDK.

Procedure

Obtain the Next.js Store SDK.
Clone the project in Git from the Git bundle.
Run the following command:
```
git clone -c core.longpaths=true bundleName projectName
```
Where:

bundleName

The filename of the bundle you are cloning.

projectName

The name of the git project that you are creating.

Note: On the windows platform, if you do not specify the configuration name and value core.longpaths=true, you may encounter the following error when you run the git clone command: Unable to create file <filename>: Filename too long.
For example:
```
git clone -c core.longpaths=true HCL_Commerce_NextJS_Store_9.1.13.0.bundle HCL_Commerce_NextJS_Store 
```
For more information, see the README.md file contained in the project root directory.

Results

The Next.js Store SDK is installed and configured.

What to do next

Ensure you add the code into your source control management system so that your work can be collaborated on and safely persisted.