HCL Commerce Version 9.1.7.0 or later

Applying a class patch to Ingest

Complete the following steps to apply a class patch to NiFi.

Procedure

  1. Open a web browser and log in to the HCL License and Delivery portal website to download the code patch JAR.
  2. Place the code patch JAR into the /patches directory. If this folder is mapped to an external storage volume, place the patch JAR there. This will save you having to log into the Ingest container.
  3. The patch will be applied automatically upon next start up if the AUTO_PATCHING deployment variable is set to true. This variable is not set by default at deployment time in the HCL Commerce Helm or Docker-compose files. Therefore you must add the AUTO_PATCHING variable and set it to true, or else apply the patch manually. To manually apply the patch, log on to the container and run patch.sh from within the /SETUP/bin directory.
  4. HCL Commerce Version 9.1.8.0 or later In previous versions, following the update of your NiFi registry you had to also update the ingest API. It was necessary to run the upgrade API to synchronize with the update registry and manually rebuild your connectors before any changes would be live. Now, rather than rebuilding your connectors, you can select the particular pipe you want to update and change the version there. A new Ingest endpoint is provided, upgradeVersion, that automatically updates the version number. Since the scheduler runs every five minutes, the registry is not only capable of importing patches, it can also export what has recently been changed. If you enable this capability, the exported material will appear in the export directory five minutes after the update. If you are also using Java code, it will however have to be added separately.