HCL Commerce production update overview
Releases for HCL Commerce Version 9.1 production environments are delivered as new Docker images. Releases can include code fixes, security fixes, new features, or enhancements.
- Delivered as Docker images, available from HCL License and Delivery portal.
- Each new release consists of the base product, plus all the fixes and
enhancements since the base release.
For example, HCL Commerce Version 9.1.3.0 contains the base Version 9.1.0.0 code and also all the functions and fixes from Versions 9.1.1.0 and 9.1.2.0. Users who are deploying HCL Commerce for the first time, can simply deploy Version 9.1.3.0 directly without setting up the base Version 9.1.0.0 first.
- A mod pack or fix pack release is the only mechanism that HCL uses to deliver features and fixes. Interim fixes are not provided.
- HCL intends to release updates quarterly, or more frequently if security vulnerabilities are identified. The timing and frequency is not guaranteed and can change without notice at the sole discretion of HCL.
- New features, or enhancements to existing features, that can affect your custom code are disabled by default.
- Fixes to co-requisite software (WebSphere Application Server, WebSphere Application Server V8.5.5 Liberty, and IBM HTTP Server) and other open source utilities and libraries are included as part of the Docker images.
To update HCL Commerce production environments, use newer HCL-provided Docker images as a base. Build custom Docker images with your custom code and then deploy new containers. For more detailed information and steps, review the following topics.
Downtime considerations
You must review your environment upgrade plan and consider the required downtime for upgrading your production environments and this impact on the availability of your live site.
A significant site upgrade generally involves bringing down an active deployment, upgrading the database schema, re-deploying the environment with updated custom docker images, as well as building new or modifying existing search indexes. The sum of these processes will typically result in some level of downtime for the production environment. To minimize this downtime, and to avoid disruption to live site traffic, production environment upgrades must be planned carefully. You must consider various factors, such as the method of deployment, the deployment configuration, and the current CI/CD pipelines for deploying the updated custom docker images on the production environment.