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+.
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.
Command extensions
The xC programming model enhances the Commerce Service command framework, enabling remote extension customization of Commerce Service business logic, specifically controller and task commands.
Supported extensions
The following section lists the available extension points available in Commerce+. You can browse the extensions to find which suit your customization requirements.
Inventory
You can customize how Commerce+ integrates with external inventory management systems, such as how Commerce+ consumes inventory availability updates from external inventory management systems.

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.
    - 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.
      - Command extensions
        The xC programming model enhances the Commerce Service command framework, enabling remote extension customization of Commerce Service business logic, specifically controller and task commands.
        Extension lifecycle
        The customization lifecycle outlines the steps to create, test, and deploy command extensions in HCL Commerce+. These extensions allow users to customize the app to fit their business needs and keep the process simple.
        Supported extensions
        The following section lists the available extension points available in Commerce+. You can browse the extensions to find which suit your customization requirements.
        Inventory
        You can customize how Commerce+ integrates with external inventory management systems, such as how Commerce+ consumes inventory availability updates from external inventory management systems.
        Order
        You can customize how Commerce+ handles cart and order capture operations and integrations with an external order management system.
        Users
        You can customize how Commerce+ handles user registration. For example, use these extension points to add custom logic to validate user information before the user profile is updated.
        Assigning code to extension points
        After developing your xC extension code, register and associate it with extension points via the Commerce+ database. You will need to update two database tables: UEConfig and CmdReg..
      - Inventory management for developers
        Use or extend the HCL Commerce+ Inventory to manage your inventory and your Inventory Locations (ILs), where your inventory is stored and is delivered or shipped from.
  - 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.

Inventory xC extension points

You can customize how Commerce+ integrates with external inventory management systems, such as how Commerce+ consumes inventory availability updates from external inventory management systems.

The following table identifies the classes for inventory-related commands that you can customize through an externalized customization extension.


				Sample CSV input files
inventory-update	The SyncInventoryAvailability service calls the inventory-update extension point to perform custom actions (for example, change the available quantities) before updating the inventory availability cache.	ChangeInventoryAvailabilityBasePartExtCmdUEInput, ChangeInventoryAvailabilityBasePartExtCmdUEOutput	The updateInventoryQuantity method in `workspace_dir`/commerceue-app/src/main/java/com/ibm/commerce/inventory/ue/rest/InventoryResource.java	inventory_update

Sample input files for registering and assigning order xC extension points


Extension point	Registering extension code with UEConfig.csv	Assigning extension code to extension points with CmdReg.csv
inventory-update	Sample UEConfig_invupdate.csv Set UEConfigId column to a unique integer value. Set Url column to the URL of the extension code, relative to https://`hostname`:9443/commerceue. Set Properties column as name-value pairs. For more information, see Adding xC configuration information.	Sample CmdReg_invupdate.csv Set Properties column to include the `UEConfigId` integer value. Set StoreIdentifier column to include the name of your store. If you want all stores to use the same extension code, then specify NullEntity. For more information, see Registering custom xC extensions.