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.
Customizing
The topics in the Customizing section describe tasks performed by an application developer to customize Commerce+.
Search
Commerce+ comes with a powerful and fully integrated search function. The search functions in Commerce+ provide an enriched customer experience, with features such as automatic search term suggestions and spelling correction. Since it is built on industry standards, Commerce Search is highly flexible and extensible. Starter stores can use the search engine's most sophisticated features without requiring extra customization. The Commerce Search Elasticsearch microservices manage indexing and other crucial tasks, with no performance impact on the storefront or transaction server.
Elasticsearch-based solution
The topics in this section describe tasks performed by an application developer to customize the Elasticsearch-based search solution. You can extend the search-migration/tutorials/concepts/csdelasticsearch.html and Query Service to meet your business requirements.
Fine-tuning search results
Commerce Search helps you to enhance the search experience of shoppers by adjusting your search results based on your shoppers' interactions at the storefront.

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+.
    - Search
      Commerce+ comes with a powerful and fully integrated search function. The search functions in Commerce+ provide an enriched customer experience, with features such as automatic search term suggestions and spelling correction. Since it is built on industry standards, Commerce Search is highly flexible and extensible. Starter stores can use the search engine's most sophisticated features without requiring extra customization. The Commerce Search Elasticsearch microservices manage indexing and other crucial tasks, with no performance impact on the storefront or transaction server.
      - Search terminology
        Commerce+ Search uses a number of specialized terms. A concise list of the most commonly used terms is provided to get you started.
      - Elasticsearch-based solution
        The topics in this section describe tasks performed by an application developer to customize the Elasticsearch-based search solution. You can extend the search-migration/tutorials/concepts/csdelasticsearch.html and Query Service to meet your business requirements.
        Indexing choices
        You have two options for indexing Extended Site (eSite) stores, the legacy eSite Store indexing model, or the Catalog Asset Store (CAS) model. The CAS model is recommended because of its speed and scalability.
        Extending the Ingest service
        The Commerce Search service includes Ingest and Elasticsearch, which together form a distributed, scalable search and analytics engine. You can chain together the Ingest service's rule-based aggregations to boost relevancy for hero SKUs or certain facets, and use sophisticated metrics to analyze your search performance.
        Extending Elasticsearch
        You can customize the behavior of Elasticsearch through ZooKeeper, or by adding your own REST API endpoints. A variety of approaches to extending the Elasticsearch service are discussed and methods are provided.
        Fine-tuning search results
        Commerce Search helps you to enhance the search experience of shoppers by adjusting your search results based on your shoppers' interactions at the storefront.
        Programming with facets
        Facets are filters that allow storefront customers to narrow their search according to catalog entry attributes. You can control the behavior of facets by changing how attributes are displayed. For example, a product with an attribute named size could display the four allowed values of the attribute as S, M, L, XL.
        CI/CD strategy to deploy customizations
        The Commerce Search Elasticsearch solution does not dictate the data repository or scripting needed to automate a Continuous Integration/Continuous Delivery (CI/CD) pipeline. You have the flexibility to use your own data repository and build structure. The following topics describe a recommended approach including a suggested data pipeline structure.
        Updating Elasticsearch-based search customizations
        You can update existing Solr extensions to the data service model, and keep your custom connectors and NiFi flows up to date with the latest version of Commerce Search.
      - Solr-based solution
        In keeping with HCL's commitment to current and open standards, Commerce Search uses Apache Lucene as the basis of its Search framework. Lucene powers the Apache Solr search engine and the Elasticsearch search engine. The indexing pipeline is a more open, flexible and scalable and is tightly integrated with the data service. Using the underlying dataflow technology and architecture, you can easily customize the pipelines. This open-standards approach considerably eases the process of integrating Search with existing and third-party applications.
    - Customizing with xC
      Commerce+ service includes access to an externalized customization server that runs your custom Connectors and any functional extensions you may write. The xC service uses an Open Liberty server on OpenJDK, with webapplications executed via Spring Boot 3.x for development.
  - Developing stores
    Commerce+ offers customizable features for storefronts using the Next.js framework. Commerce+ supports headless commerce to use any front end storefront.
- 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.

Fine-tuning search results

Commerce Search helps you to enhance the search experience of shoppers by adjusting your search results based on your shoppers' interactions at the storefront.

A Swagger interface to the Query Service API endpoints is available in the Query REST API. By calling the endpoints Search Ranking and Search Config, you can do the following things:

Using the Search Ranking endpoint, fine-tune the search results by pinning, unpinning, re-sequencing, adding, and hiding the products for a specific search term (new or existing search terms).
Using the Search Ranking endpoint, fine-tune search results either by creating a new search ranking or by updating/deleting the existing search ranking for a specific search term (new or existing search terms).
Using the Search Config endpoint, fine-tune the search results by assigning new colors to the existing color family or by updating/deleting the existing colors assigned to the color family. To know about the default color families provided by the Commerce+ and the colors defined in these default color families, refer to About color families

Important: On performing push to live operation for the search rankings, the NiFi processor makes a call to the configuration endpoint of data query using the PUT request method to move data from ZooKeeper search rankings/auth node to search rankings/live node.

Request Method: PUT
Request URL: -${QUERY_SCHEME}://${QUERY_HOST}:${QUERY_PORT}/search/resources/api/v2/configuration