Introduction

The <cartridge_name>.properties were moved from \share\system\config\cartridges to <cartridge_name>\src\main\resources\cartridges in ICM 7.10. This has the following implications:

• The <cartridge_name>.properties are always deployed to the same location, regardless where the cartridges are deployed.
• A different finder (cartridge-resource) is used to load these properties.
• For compatibility reasons, the previous used finder (cartridge-folder) is still available and this finder even provides an higher priority then the newly introduced.

Overwriting Properties

It is still possible to overwrite these properties using the configuration framework, see Guide - Configuration Framework (valid to 7.10). If a customer wants to overwrite some cache properties, these properties have to be added into a properties file, which has a higher priority than the current cartridge-resource finder. These are the finders, which are listed above the cartridge-resource finder in the configuration.xml file (in <IS_SHARE>/system/config/cluster). So the customer can add the properties to the production.properties (represented by ${environment}.properties in the code below) for example.

<configuration-setup>
  ...
  <sets>
	...
    <set finder="property" scope="cluster,server,domain" fileName="${IS_SHARE}/system/config/cluster/${environment}.properties"/>
	...
    <set finder="cartridge-folder" scope="cluster,server,domain" cartridges="${cartridges}"/>
    <set finder="cartridge-folder" scope="cluster,server,domain" enabled="${system.dbInitMode}" cartridges="${cartridges.dbinit}"/>
    <set finder="cartridge-resource" scope="cluster,server,domain" cartridges="${cartridges}"/>
    <set finder="cartridge-resource" scope="cluster,server,domain" enabled="${system.dbInitMode}" cartridges="${cartridges.dbinit}"/>
	...
  </sets>
</configuration-setup>