One of the common processes on-premise with Oracle Utilities products is altering the various properties files to implement site specific settings. Some of the settings in these files are inherited from the various configuration files (such as etc/ENVIRON.INI) and others are unique enough to be defaulted for you. To change the latter settings, the product allowed for custom templates to be created to implement special settings or other custom settings. Whilst this is still supported, a global capability has been introduced in 4.4.x implementations to handle global configuration settings in a single override file.
This file is etc/cm_properties.ini which hold the additional instructions for the configuration utilities (such as initialSetup) to implement changes. This file has four styles of entry:
||Override the setting <properties_name> to <value> in configuration file <properties_file>. If the property does not exist in the file, it will be added.|
||Override the setting <properties_name> to <value> in all properties files where the property exists.|
||Remove the setting <properties_name> from the configuration file <properties_file>.|
||Remove the setting <properties_name> from all properties files where the property exists.|
Note: Removal of properties will revert to implied defaults so should be used with caution.
This would override and delete entries from various hibernate properties files.
Note: The product teams may deliver overrides for their products but the cm file would be the last file provided to override across properties files.
For more examples of this capability, refer to the Installation Guide and Server Administration Guides shipped with the products or on the Oracle documentation site.