Persisting changes in configuration files from file system to database
As of BMC Server Automation 8.6, the latest copy of configuration data is maintained on the database. When an Application Server is started, it synchronizes various configuration files, updating them in the database according to the values stored on the file system. This synchronization is applied to configuration files such as those discussed in configuration files, certificates, keystores, and third-party configuration files, but is not applied to configuration files for the Application Server services.
Any changes that you apply to these configuration files are not synchronized until the next time that the Application Server is restarted. The
syncFile blasadmin command enables you to persist all changes that have accumulated in the configuration files from the file system to the database, without having to restart the Application Server. As shown in the following command line, no parameters are required by this command:
Changes that you perform on configuration files for Application Server services through blasadmin are persisted to the database automatically. Therefore, you do not need to run the syncFile command on configuration files for Application Server services.
For changes that you want to apply to the configuration files, BMC recommends using the Application Server Administration Console (blasadmin utility) wherever appropriate blasadmin options are available. Do not manually edit files unless explicit instructions are provided for doing so.