Editing Configuration Files

You can copy configuration files to a location where Brand Mobiliser reloads them automatically. You can also track configuration-file changes.

1. To make changes to a system configuration file, and have those changes take effect without restarting Brand Mobiliser:
   1. Change the configuration file in the conf/cfgbackup folder.
   2. Copy the modified file to the conf/cfgload folder.
   Brand Mobiliser loads the file automatically, and moves it back to the conf/cfgbackup folder. By default, changes are not logged.
2. To track configuration-file changes:
   1. Edit the conf/cfgbackup/org.ops4j.pax.logging.properties file.
   2. Change the value of log4j.logger.com.sybase365.arf.container.system from WARN to INFO:

      log4j.logger.com.sybase365.arf.container.system=INFO, main, osgi:VmLogAppender 
      log4j.additivity.com.sybase365.arf.container.system=false

   When the property file is reloaded, the log is written to log/felix.log. The following example displays log entries that resulted from reloading the service.webui.security.properties file.

   16:15:53,507 | INFO | Thread-1 | cm-loader | ldap.port:389   
   16:15:53,513 | INFO | Thread-1 | cm-loader | ldap.userpath:uid={uid},ou=people,o=sybase365   
   16:15:53,513 | INFO | Thread-1 | cm-loader | ldap.security.authentication:SIMPLE   
   16:15:53,513 | INFO | Thread-1 | cm-loader | ldap.host:localhost   
   16:15:53,513 | INFO | Thread-1 | cm-loader | service.pid:service.webui.security   
   16:15:53,513 | INFO | Thread-1 | cm-loader | authentication.bean:AuthenticationManager   
   16:15:53,513 | INFO | Thread-1 | cm-loader | arf.filename:service.webui.security.properties