...
You should get a response like this.
Enabled
In some configurations maybe not all components of the system need direct access to the Archive, so an optional Enabled element can be added to control this:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews https://fewsdocs.deltares.nl/schemas/version1.0/archives.xsd">
<enabled>$ARCHIVE_ENABLED$</enabled>
<catalogueUrl>http://dummy_server:7080/deltares-archive-server/catalogue</catalogueUrl>
<elasticSearchUrl>http://dummy_server:7080/deltares-archive-server/elastic</elasticSearchUrl>
</archives> |
In this example a global property $ARCHIVE_ENABLED$ is used to control if the archive connection is enabled, this allows for example OC clients or FSS nodes (each having their own global properties) to not allow connections to the archive in specific cases. Doing so will of course disable seamless integration on these systems.
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.
...