Operator Client

This module is specifically designed for FSS's with DDA.

Since 2017.02 the config management has been redesigned making the old Config Update Script obsolete.

A new simplified module has been introduced which imports and updates new versions of MapLayerFiles: .csv files and .dbf files with corresponding .shp, .shx and .sll files.

The map layer files need to be already present in the default config (current config revision set) and is case sensitive.

It will check whether all imported files are present in the current revision.

It will validate whether the new configuration is still valid.

If the new configuration is not valid the new files will be imported and a new config revision set will be created. The files will be moved to the backupDir.

When the new configuration is NOT valid NO files will be imported and NO new config revision set will be created. The files will be moved to the failedDir.

<?xml version="1.0" encoding="UTF-8"?> 
<configUpdateModule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/configUpdateModule.xsd">
    <mapLayerImport>
        <importDir>%REGION_HOME%/configUpdate/inputFiles/MapLayerFiles/</importDir>
        <backupDir>%REGION_HOME%/configUpdate/backup</backupDir>
        <failedDir>%REGION_HOME%/configUpdate/failed</failedDir>
    </mapLayerImport>
</configUpdateModule>

Stand Alone

This module is not designed for a SA application, but can be used for testing.

For this the next steps need to be taken:

1. Start an OC and create a replica of the database with config (F12 – Database – replicate central database) time series are not necessary 
2. Create a SA with the replicated localdatastore without (!) config directory
3. Place new version of the active .csv, .dbf and .shp files in the configured import directory
4. Start the SA and run de ConfigUpdateModule 
5. When a new config revision set has been created it will have an id like: "unknown;X"
6. If a new config revision has been created, errors can occur due to on the fly config update which a SA can not handle. The errors should disappear after restart.
7. Close the SA and restart
8. Export the default config (F-12 export – default config)
9. Check whether the new .csv, .dbf en .shp files are present.