Page History

...

The archives.xml will be used by the archive display panel to identify were the webservices of the archive are located. 

In addition you will need to configure a file called ArchiveModuleDisplay.xml in the DisplayConfigFiles folder.

...

To restrict thist list, for example when not all datasets-types are exported by FEWS to archive, the tag searchDataTypes can be used.

The configuration file for this display resides in the DisplayConfigFiles folder. It primarily contains references to the archive server, while it also specifies tte download folders, i.e. the destination folders for data being downloaded.

Image Removed

While the xsd is mostly self explaining some remarks can be made:

• it is recommended to use global properties to define the server details and the download folders.
• When Historical Events are defined as an event type, the defaultHistoricalEventTimeStep needs to be defined. This time step becomes part of the historical event definition as the system needs to know which of the archived observed timeseries has the proper timestep for use as a histroical event.
• Not all archive systems will hold/store all dataset types. To prevent confusion with the user, the search options can be restricted to a limited list of dataset types that can be searched for, using element searchDataTypes.

...

In the archive is not installed according to the conventions desribed in the installation manual than it might be needed to configure custom endpoint for several webservices of the archive which

are called by the archive panel. This custom configuration can be done in the tag "archiveServer", below an example is given.

	<archiveServer>
		<archiveWebService>http://server-name:8080/deltares-archive-server

</archiveWebService>
		<archiveConfigFileUrl>http://server-name:8080/thredds/fileServer/Config

</archiveConfigFileUrl>
		<eventsFileServerUrl>http://server-name:8080/thredds/fileServer/Events

</eventsFileServerUrl>
		<dataFileServerUrl>http://server-name:8080/thredds/fileServer/archive</dataFileServerUrl>
	</archiveServer>