Page History

...

<?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 http://fews.wldelft.nl/schemas/version1.0/archives.xsd">
	<catalogueUrl>http://myserver:7080/deltares-archive-server/catalogue</catalogueUrl>
	<elasticSearchUrl>http://myserver:9800</elasticSearchUrl>
</archives>

Reverse proxy (FEWS 201802 and higher)

A FEWS OC or SA needs access to the catalogue to search for data in the archive.

...

The reverse proxy is available at the relative URL /elastic in the Archive web application.

It is therefore highly recommended to connect the FEWS OC or SA to the read-only reverse proxy. A configuration example is given below.

 If you want the FEWS clients to 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="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/archives.xsd">
	<catalogueUrl>http://myserver:7080/deltares-archive-server/catalogue</catalogueUrl>
	<elasticSearchUrl>http://myserver:7080/deltares-archive-server/elastic</elasticSearchUrl>
</archives>

If the FEWS OC or SA connects to the read-only reverse proxy instead of to elastic directly it is possible to restrict the access to the elastic.

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

You should get a response like this.

Image AddedThe harvester always needs direct access to elastic because the harvester also updates the catalogue.