Custom Properties

The customization init image can be used to configure override files and adding new or updating existing product property files.

The customization init image defines the below directory and file structure for custom properties with placeholder files for customer_overrides.properties and system_overrides.properties which can then be updated by extending the image:

ibm
 b2bi
  customization
   properties
    customer_overrides.properties
    system_overrides.properties

Note: The helm chart config folder will always take precedence over any liberty override files or property files applied through the customization init container. If you want the liberty override files or property files from the customization init container to be applied then all the sample files from the helm chart config folder should be removed and placed in a different backup location.

Product configurations supported by the customer overrides or system overrides framework can be added to the overrides property files following the standard nomenclature as below:

<file-prefix>.<property-name>=<property-value>

Apart from the above overrides files, any product configuration or property file with or without the .in extension can be updated with custom values and placed in the properties folder. Also, new properties files that need to be added to the <install-dir>/properties location can be placed in the properties folder. At runtime these property file(s) will be copied and replaced in the <install-dir>/property folder. This provides a better alternative to the current property customization option by placing the property files (*.in) under the <helm-chart>/config folder.

Note: If the property file is specific to ASI, AC, or API, the property file name should be prefixed with asi-, ac-, or api-, respectively.