Exalead CloudView modules are managed by a distinct configuration system, introducing a new staging area and a per module configuration management. The configuration works as follows:
• On save (through Mashup Builder / Administration API), files are staged in <DATADIR>/gct/staging
• On apply (through Mashup Builder / Administration API), all or specified files are copied in <DATADIR>/config/360. Configuration files in this directory are considered as applied. Then, the applyConfiguration call of the underlying Exalead CloudView instance is invoked.
• At runtime, services read their configuration from <DATADIR>/gct/<last version>/master/360
• When a new configuration is applied, services are notified and reload their configuration without having to restart.
If you want to modify the Mashup Builder configuration manually in the <DATADIR>/config/360 directory, you need to invoke an apply configuration order on Exalead CloudView by running the command: <DATADIR>/bin/cvcmd.sh applyConfig