...
| Code Block |
|---|
<arc:dataManagementTool xmlns:arc="http://www.wldelft.nl/fews/archive" xsi:schemaLocation="http://www.wldelft.nl/fews/archive http://fews.wldelft.nl/schemas//version1.0/archive-schemas/dataManagementTool.xsd" xmlns="http://www.wldelft.nl/fews/archive" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <outputFile>d:\fews\output\managementreport.csv</outputFile> <backupFolder>d:\fews\backup</backupFolder> <lifeTimeRules> <defaultLifeTime unit="year" multiplier="10"/> <defaultAction>default</defaultAction> <lifeTimeSimulatedDataSets> <lifeTime unit="year" multiplier="10"/> <action>remove</action> </lifeTimeSimulatedDataSets> <lifeTimeSimulatedDataSets> <sourceId>sourceId</sourceId> <lifeTime unit="year" multiplier="10"/> <action>remove</action> </lifeTimeSimulatedDataSets> <lifeTimeObservedDataSets> <lifeTime unit="year" multiplier="10"/> <action>remove</action> </lifeTimeObservedDataSets> <lifeTimeExternalForecastDataSets> <lifeTime unit="year" multiplier="10"/> <action>remove</action> </lifeTimeExternalForecastDataSets> <lifeTimeMessagesDataSets> <lifeTime unit="year" multiplier="10"/> <action>remove</action> </lifeTimeMessagesDataSets> <lifeTimeConfigurationDataSets> <lifeTime unit="year" multiplier="10"/> <action>remove</action> </lifeTimeConfigurationDataSets> <lifeTimeRatingCurveDataSets> <lifeTime unit="year" multiplier="10"/> <action>remove</action> </lifeTimeRatingCurveDataSets> <eventRule> <eventTypeId>historic event</eventTypeId> <lifeTime unit="year" multiplier="20"/> </eventRule> <eventRule> <eventTypeId>calibration event</eventTypeId> <lifeTime unit="year" multiplier="20"/> </eventRule> <eventRule> <eventTypeId>watercoach event</eventTypeId> <lifeTime unit="year" multiplier="20"/> </eventRule> <eventRule> <eventTypeId>review event</eventTypeId> <lifeTime unit="year" multiplier="20"/> </eventRule> <eventRule> <eventTypeId>flood watch event</eventTypeId> <lifeTime unit="year" multiplier="20"/> </eventRule> </lifeTimeRules> </arc:dataManagementTool> |
Once the configuration of the DataManagementTool.xml is finished it should be added to the configuration of the archive server. You can do this by uploading it to the archive.
Select the tab manage configuration and upload the new DataManagementTool.xml to the archive by using the browse (to select the file) and upload button in the row DataManagementTool.xml.
It is also possible to put this config file directly in the config folder of the archive but you will have to restart the tomcat instance of the archive server to make it aware of the fact that there is new file available.
In the screenshot above the you can see that the file managementreport.csv can be downloaded by pressing the download button.
You can download this file by pressing this button to review which data sets are expired. If needed you can manual edit file by using a text editor or excel.
After you reviewed and/or changed this file you can upload the changed file to the archive by using the upload button.
You can then run a custom script which uses this file as input or you can use the task remove data from archive
After this step it is possible to run the data management tool to search for expired data sets in the archive. This task should be available as one of the tasks in the archive tasks tab. If it is not available there you should add it to your configuration. Go to the manage configuration tab and download the ArchiveTaskSchedule.xml file. Verify if there if the preDefinedArchiveTask remove data from archive is available.
An example is given below.
| Code Block |
|---|
<manualArchiveTask>
<predefinedArchiveTask>data management tool</predefinedArchiveTask>
<description>data management tool</description>
</manualArchiveTask> |
After adding this task you should upload the changed ArchiveTaskSchedule.xml to the archive server.
The task should now be available after selecting the tab archive tasks. You can start this tool by pressing the start-button. After running this task the output should be available in the output file which is configured in the DataManagementTool.xml. You can download this file in the tab manage configuration.