For all products shipped as WAR files (CIP, CWC and Portals), the configuration files are located within the WAR's WEB-INF/conf/ folders by default.
However, these config files can be stored in any other file system path. If a config file is stored outside the default location, it will not be overwritten if a new version of the respective webapp is installed, that is, your previous configuration settings are retained.
The exact path plus the file name of a config file must be made available to the web app via an environment variable. The variable name must include the webapp’s context name (e.g. cwc, cwc-branded) so that multiple instances of the same webapp under different contexts can be deployed. All config files can be stored in the same folder, e.g:
If the environment variable is not set or the config files can't be read from the specified locations, the config files embedded in the WAR's WEB-INF/conf directories are used instead. If no config file is available at all, the webapps can’t be started.
NOTE: Unlike the files mentioned above, the customization.js file is always retrieved from the root of the Portals web app and MUST NOT be stored in a different path!
Employing CWC Plugins
If custom CWC plugins are employed, they must be installed in a plugins folder in the same path as the config file, e.g.
• cwc: /opt/cumulus_conf/plugins
• cwc-branded: /opt/cumulus_conf/plugins
In this example, both Web Client instances (“cwc” and “cwc-branded”) use the same plugin(s).
In order to use different plugins with different instances, the config file and plugin folder must be stored in an individual path for each instance.