The page Archive Tasks can be used to start and stop archive tasks. It also possible to see which tasks are scheduled and what their task schedule is.
This page shows an overview of the tasks which are configured for the archive. The configuration of the archive tasks can be done by adjusting the ArchiveTaskSchedule.xml. Detailed information about the configuration of this file can be found here:See also Configuration of the Delft-FEWS Archive Server
...
Tasks which can be scheduled have a start time, an end time and a run interval. The start time and end time indicate the time window in which the task is allowed to run. The run interval shows how often the task should run. A scheduled task only runs periodically if it is activated. The last column "activated" shows if the task is activated or not. Tasks can be activated or deactivated by changing the configuration. More details can be found hereSee also: Configuration of the Delft-FEWS Archive Server
...
The task "internal harvester" is responsible for updating and maintaining the catalogue. The catalogue is used to find data sets in the archive. The task "clear internal catalogue" is used clear the entire catalogue. When you run the task the entire catalogue will be empty! The tasks "internal harvester" and the task "clear internal catalogue" are the two most important and most used tasks of the archive. The internal harvester can not run if the clear catalogue task is running. If the Clear Catalogue Task is running the start button of the Internal Harvester Task will be disabled. You will have to run the task "internal harvester" again to rebuild the catalogue. The are a lot of other tasks available: More details can be found here:See also: Configuration of the Delft-FEWS Archive Server
Merge new data into archive
It is possible to upload new external historical data to the archive by using the archive display. To insert these new data sets the task merge new data into archive should be scheduled. This task will merge newly uploaded datasets with the existing datasets in the archive.
| Code Block | ||
|---|---|---|
| ||
<scheduledArchiveTask>
<predefinedArchiveTask>merge new data into archive</predefinedArchiveTask>
<description>merge data</description>
<startTime>03:00:00</startTime>
<endTime>20:30:00</endTime>
<runIntervalInSeconds>60</runIntervalInSeconds>
<active>false</active>
</scheduledArchiveTask> |
If you use this feature you also need to configure the immediate harvester task. This will ensure that after the merge activity the newly added data sets are directly available in the archive.
Immediate harvester task
The immediate harvester task will harvest data sets on demand.
| Code Block | ||
|---|---|---|
| ||
<scheduledArchiveTask>
<predefinedArchiveTask>immediate harvester task</predefinedArchiveTask>
<description>immediate harvester task</description>
<startTime>00:00:00</startTime>
<endTime>23:59:00</endTime>
<runInterval>2</runInterval>
<active>false</active>
</scheduledArchiveTask> |
Custom tasks
It is also possible to define custom tasks. To make sure that the archive can start the script correctly, you can start the script from the commandline and check if it runs correctly. Usually configurators create a .bat-file or a .sh file to launch another executable. Below an example.
...
The page task history shows when certain archive tasks were started and when they were finished. The page also indicates if the tasks was finished succesfully or not. For the standard tasks like file sweeper, harvester, clear archive and the historical events exporter there is a tab available for each task. Custom defined tasks are shown in the tab custom.
