Basic configuration

The Archives.xml can be used to configure the connection between your sa,oc or fss with the archive. For an sa or oc the configuration only consists of the catalogueUrl in case you have configured the archive according the standard (which is usually the case).

An example is given below.

<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="" xmlns:xsi="" xsi:schemaLocation="">

Data from the Open Delft-FEWS Archive can be used in a Stand Alone or Operator Client FEWS client; this functionality is called seamless integration. The Archives.xml file, located in the SystemConfigFiles folder, is used to add this seamless integration functionality to the Delft-FEWS system. Seamless integration between the Open Delft-FEWS Archive and the Operational Delft-FEWS Database means that when data is not found in the operational database, FEWS will search for this data in the Open Archive.

The seamless integration functionality is now available in the Time Series Display for external historical scalar time series. Additional functionality for simulations and external historical time series is included in the FEWS pi-services.

Below an example of the content an Archives.xml configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="" xmlns:xsi="" xsi:schemaLocation="">

Note that a very common mistake made in configuring the Archives.xml is that the catalogueURL does not end with catalogue!

The only configuration needed in the Archives.xml is the location of the catalogue and thredds:

  • The catalogue used for seamless integration is the internal elastic search catalogue (not the Geonetwork catalogue). The catalogue is used by the FEWS client to find archived data.
  • The fileserver used for seamless integration in the THREDDS server. The fileserver is used to download the data from the archive.

The datafolder is optional. It is used by the pi-service (rest and soap) to read the data. If the datafolder is configured the data is read from the folder directly and not from THREDDS. Reading the data directly from disk is faster than reading the data from THREDDS. So the datafolder should be the root of the datafolder of the archive as it is on the server on which the pi-service is configured.

Test of the Archive configuration

To test if the catalogue url is correct, paste the url in an internet browser. If the config is correct the response below will be visible (or something similar). The response either indicates that the catalogue is moved to another URL (releases prior to august 2020) or the response will look like

This url was used to host the embedded catalogue prior to the 201802 release.
Now it is used to verify that the correct catalogueURL is configured correctly in the Archives.xml
The URL http://localhost:7080/deltares-archive-server/catalogue should be used as the catalogueURL in the Archives.xml

To test if the fileServer url is correct append /catalog.html to the url configured and paste this url in an intenet browser. If the url is correct a list of the files and directories in the root of the data folder in the archive will be visible. 

Optional configuration


By default FEWS will assume that the elastic catalogue is running at the same server as the archive web application at the port 9200.

The default can be changed by using the tag elasticSearchUrl. Below an example

<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="" xmlns:xsi="" xsi:schemaLocation="">

Reverse proxy

A FEWS OC or SA needs access to the catalogue to search for data in the archive. This requires direct access to elastic from a FEWS OC or SA, introducing a attack vector. Since August 2020 the Deltares Open Archive contains a read-only reverse proxy inside the Archive web application. This reverse proxy redirects only the limited set of read-only elastic requests which an FEWS OC or SA needs. The reverse proxy is available at the relative URL /elastic in the Archive web application. In order to make Operator Clients connect to the reverse proxy instead of connecting directly to elastic you should configure tag elasticSearchUrl like example below. 

<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="" xmlns:xsi="" xsi:schemaLocation="">

Both the catalogueUrl and the elasticSearchUrl tags should be configured!

You can test the elasticSearchUrl by pasting the URL in a browser.

You should get a response like this.

Archive database

It is possible to store scalar data inside a database instead of in netcdf files. In the Archives.xml the details of the database (URL, username and password) and the details about how to load the plugin for the archive database should be configured. At the moment there is a plugin available for MongoDB. 

A configuration example for the MongoDB plugin is available below:

<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="" xmlns:xsi="" xsi:schemaLocation="">

The archiveDatabaseUrl and the username and password are dependent on the system setup. If you use the MongoDB-plugin then you should use the pluginClass and pluginFactoryMethod as shown in the example. The plugin can be provided by Deltares on request.

Optional binDir

You can configure a custom directory to install the jar-files of the plugin in. If you do not configure a custom pluginDir then you should located the plugin .jar file in the same directory as the FEWS jars.

Uploading edited data to the archive

When data is edited in FEWS then the data edits are by default not send to the archive. When the option uploadEditedDataToOpenArchive is set the data edits are send to the Archive.

It also necessary to configure the uploadEditedDataToOpenArchive. This  location attribute function will be used to determine to which area (one or more) each location belongs.

Below a configuration example

<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="" xmlns:xsi="" xsi:schemaLocation="">

In addition a workflow needs to scheduled to insert the data edits into the archive. More details can be found here 22-4 Merging edited data - DELFT-FEWS Documentation - Deltares Public Wiki

Custom export folders

Data is exported to the open archive according to fixed folder structure. In some cases this folder structure is customizable by using configuration options. From FEWS Release 202302 and higher it is possible to configure a custom export folder for each data type in the archive.

A configuration example is given below:

<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="" xmlns:xsi="" xsi:schemaLocation="">

It is possible to a  use date/time pattern in the folders structure. The pattern will be parsed during export by using the time relevant for the export. The time that is used to parse the date/time pattern is dependent on the type of export. Below an overview of the time used for each export type.  

Time used 
External historicalstart time exported data
External forecastexternal forecast time
Simulated forecasttime zero
Simulated historicalstart time exported data
Snapshotcurrent time
Configcreation time latest revision
Productstime zero
Rating curvescurrent time
Log messagesstart time exported data
Forecaster notesstart time exported data

In addition it is possible to use plain text in the folder structure.

A set of tags like %areaId% are supported and will be parsed during the export. Note, however, that not all tags are supported for each type of export; below overview shows which tags are supported for each export type.

areaIdsourceIdcurrentTimetaskRunIdwhatIfIdworkflowIdsupplied attributesrevisionId
External historicalxx

External forecastxx

Simulated Forecastxxxxxx

Simulated historicalx





Rating curvesx

Log messagesx

Forecaster notesx

  • No labels