| scrollbar |
|---|
| Table of Contents |
|---|
Introduction
The configuration of DELFTDelft-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 DELFTDelft-FEWS system.
When dealing with the Normally, when developing a Delft-FEWS configuration, it is important to note that the configuration may be retrieved from this is first setup in a Stand alone application, which typically has a configuration setup on the local file system or from the local . When distributing the application, the configuration files are instead shared via a local database or the central database.
- In the former case the the Stand alone application 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.
- In the latter case the configuration is contained entirely within the local database in a set of in a local datastore or central database, the structure of config file directories is stored in dedicated SQL tables, each table containing different parts of the configuration. Each of the tables in the local database reflects one of the sub-directories in the file system.
When initiating DELFTthe Stand alone Delft-FEWS application, it will first look for configuration stored on in the local file systemdatastore or in the filesystem. If this is both are found, then the system will expect to use all configuration from the file system. If the Config directory is not available the system will expect to use all configuration from the databaseask 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 stored in either the Config directory of the database is configuration that is common to all versions of an implementation of DELFT-FEWS for 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 synchronised 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. Besides this configuration that is synchronised, there is also a A small set of XML files referred to as the root configuration files. These may be unique to each may differ between operator client and/or forecasting shell server. This root configuration is required to identify for example if the particular instance of DELFTDelft-FEWS is operating in stand-alone mode or as an operator client, and for the latter cases information such as IP-addresses for the Master Controller the operator client should log on toor on windows or linux. These root configuration files are always used from the file system. They have no effect on the hydrological configuration and are normally not changed during configuration of the forecasting system side of DELFTDelft-FEWS.
Elements of the configuration
The two tables below provide an overview of the configuration elements of DELFTDelft-FEWS. In the first table the configuration contained both in the database and on the file system is described. The second table describes the configuration that is only available on the file system.
Table 1 Overview of different configuration items contained either in the config directory or in the database
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 |
Table 2 Overview of different configuration items contained in the file system only
Configuration Item | Directory on File System |
Root Configuration. Several XML files describing some of the settings specific to the Operator Client used (e.g. client configuration, IP addresses) | These files are contained in the root of the |
Delft-FEWS configuration directory |
Versions of configuration and XML file naming conventions
For each of the configurations managed by DELFTDelft-FEWS in either the database or on the file system as described above, various versions of configuration may exist. Configurations that are active and used as a default can be identified both in the file system and in the database. On the file system a naming convention is introduced to identify which of the possible multiple versions are used as a default. The naming convention for the default version:
| Info |
|---|
<Name of XML configuration file>SPACE<Version number>SPACE<default>.xml |
Other Another version of configuration will have a different version number. The <default> item is omitted.
...