| scrollbar |
|---|
| Table of Contents |
|---|
Introduction
The configuration of DELFT-FEWS is defined in a set of XML files. 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.
...
Besides this configuration that is synchronised, there is also a small set of XML files referred to as the root configuration files. These may be unique to each 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, and for the latter cases information such as IP-addresses for the Master Controller the operator client should log on to. 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 DELFT-FEWS.
Elements of the configuration
The two tables below provide an overview of the configuration elements of DELFT-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.
...
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 DELFT-FEWS in either the database or on the file system as described above, various versions of configuration may exist.
...
In the database the default version for each configuration item is identified in an associated table. For each configuration item a default table is available. This is identified by a table with the same name, prefixed by "Default". For example for the SystemConfigurations a table with the name DefaultSystemConfigurations identifies which of the available versions in the former table is to be used a default.
Naming conventions for defining module config files
For complex forecasting systems the number of configuration files can be very large. This is particularly the case for the module config files, and because the names of these are used in Time Series Sets for storing and retrieving data, the names given should be chosen logically. Before configuring large numbers of XML files it is wise to define a naming convention and use this throughout. An example of such a convention is where a number of steps are used to process data prior to running a model.
...
This clearly indicates the association between modules and brings structure to the configuration.
XML Schemas and schema validation
Each configuration item contained in an XML file must be formatted as specified in an appropriate XML schema (XSD file). Validating against the schemas is an important step in configuring DELFT-FEWS, as the primary validation makes sure the syntax of the configuration made is correct.
...