...
When distributing the application, the configuration files are instead shared via a local datastore or the central database. The local datastore or the central database, stores the same local filesystem configuration directory structure in dedicated SQL tables, each table containing different configuration directory. The configuration in the central database belongs to a dedicated Delft-FEWS implementation of a particular forecasting system. In the live system situation the contents of the database will be shared between all operator clients and forecasting shell servers in the system, and is therefore expected to be identical in all parts of the system. In the central database active versions of configuration items have synchLevel 11 whereas inactive configuration files have synchLevel 0. The ConfigRevisionSets table defines the metadata of the active configuration.
| Info |
|---|
When initiating the Delft-FEWS application, it will look for configuration stored in the local datastore or in the filesystem. If both are found, then the system will ask the user to choose which to use. If neither is found then an appropriate error message is issued and the system will stop |
...
. |
RootConfig files
A small set of XML files referred to as the root configuration files may differ between operator client and/or forecasting shell server. This root configuration is required to identify for example if the particular instance of Delft-FEWS is operating in stand-alone mode or as an operator client, or on windows or linux. These root configuration files have no effect on the hydrological configuration and are normally not changed during configuration of the forecasting system side of Delft-FEWS.
...