...
The configuration of Delft-FEWS is defined in a set of XML files and a properties file. In this section the different parts of the configuration are introduced. An understanding of these different parts of the configuration is required before attempting configuration of a Delft-FEWS system. Normally, when developing a Delft-FEWS configuration, this is first setup in a Stand alone application, which typically has a configuration setup on the local file system. When distributing the application, the configuration files are instead shared via a local database or the central database.
...
In this case, the configuration is defined by a fixed set of directories, each containing different parts of the configuration. These directories are all contained under the Config directory.
...
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 configuration directory structure in dedicated SQL tables, each table containing different
...
configuration
...
directory. When initiating the Stand alone 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. 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. 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.
...
Configuration Item | Directory on File System | Table name in file system | Single/ |
Definition of regional configuration, including all locations, parameters etc. | RegionConfigFiles | RegionConfigurations | Single |
Definition of system configuration items, including the plug-ins available to the system, definition, icons etc. | SystemConfigFiles | SystemConfigurations | Single |
Definition of modules for handling data and running forecasting models | ModuleConfigFiles | ModuleInstanceConfigs | Multiple |
Definition of workflows for running sequences of modules | WorkflowFiles | WorkflowFiles | Multiple |
Cold states for modules. Zip file containing model specific data exported by GA usually before running a model | ColdStateFiles | ColdStateFiles | Multiple |
Definition of mapping of ID's and parameters between external sources (e.g. telemetry, modules) and ID's and parameters defined in the DELFT-FEWS configuration | IdMapFiles | IdMaps | Multiple |
Definition of unit conversions between external sources (e.g. telemetry, modules) and units used in DELFT-FEWS | UnitConversionFiles | UnitConversions | Multiple |
Definition of flag conversions between external sources (e.g. telemetry, modules) and flags used in DELFT-FEWS | FlagConversionFiles | FlagConversions | Multiple |
Definition of layout of user displays, including What-if scenarios, Grid Display etc.) | DisplayConfigFiles | DisplayConfigurations | Multiple |
Definition of module parameters stored in DELFT-FEWS | ModuleParameters | ModuleParameters | Multiple |
Zipped files containing datasets for modules used by the forecasting system. | ModuleDataSetFiles | ModuleInstanceDatasets | Multiple |
Definition of HTML template files used in creating HTML reports for use on the web server. | ReportTemplateFiles | ReportTemplates | Multiple |
Map layers (shape files) used in main map display and spatial interpolation | MapLayerFiles | MapLayerFiles | Single |
Images used in reports etc. | ReportImageFiles | ReportImageFiles | Single |
Icons used in main map display and button bar | IconFiles | IconFiles | Single |
Several XML files describing some of the settings specific to the Operator Client used (e.g. client configuration, IP addresses) | RootConfigFiles | RootConfigFiles | Multiple |
...