...
Code Block | ||||
---|---|---|---|---|
| ||||
<?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 httphttps://fewsfewsdocs.wldelftdeltares.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 (testing only)
...
- Upload the configUpdateModule config file in the ModuleConfigFiles directory and make sure it is part of a workflow.
- Start an OC and create a replica of the database with config (F12 – Database – replicate central database) time series are not necessary
- Create a SA with the replicated localdatastore without (!) config directory
- Place new version of the active .csv, .dbf and .shp files in the configured import directory
- Start the SA and run de ConfigUpdateModule
- When a new config revision set has been created it will have an id like: "unknown;X"
- 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.
- Close the SA and restart
- Export the default config (F-12 export – default config)
- Check whether the new .csv, .dbf en .shp files are present.
...