| Anchor |
|---|
| _Toc154574508 |
|---|
| _Toc154574508 |
|---|
|
Managing configurations
When the Configuration Manager is started, it is initialized with the information available in the local datastore. The datastore that is used is specified in the database URL (Delft-FEWS 2018.02 and higher) or the *.ini file (Delft-FEWS 2016.01 - 2017.02) that needs to be provided with the executable file.
After startup the user can to connect to the Master Controller of the application. The details of which are obtained from the synchronization configuration files or the DDA (direct database access details) for that application. If a connection has been established successfully, the download and upload buttons will be activated. If a connection cannot be established, the buttons will remain inactive.
...
Three types of configuration files are handled by the configuration manager: XML, HTML and Binary files. The handling of each file type is slightly different, as is shown in the following table.
FileType | Handling |
XML | The file is stored in a readable form in the data store. The content of the xml file is validated before being imported. Invalid files will not be imported. |
HTML | The file is stored in a readable form in the data store. The content is not validated, as no schema will be available to validate against. |
Binary | Binary configuration files include all other configuration files. These may be xml configuration files, module data sets or module states. |
When a configuration file is imported, the user that has imported the file is registered.
How are configuration files displayed?
An active configuration is shown having a yellow background. A selected configuration file is shown having a blue background. An active selected configuration file is shown with a blue background, except for the ID which is shown with a yellow background. Below an example is given of two available ManualForcastDisplay configuration files. The active file is selected.
| Anchor |
|---|
| _Toc154574511 |
|---|
| _Toc154574511 |
|---|
|
Make a selected configuration file the active file
...
The uploading of configuration files is carried out in a transaction, enabling the complete transaction to be rolled back if an error occurs.
| Anchor |
|---|
| _Toc154574515 |
|---|
| _Toc154574515 |
|---|
|
Changing an existing configuration file
...