...
Optional element with references to the ModuleDataSetFiles module data set files that should be extracted when an OC or FSS starts . Whenever an FSS initiates a workflow, it verifies if it should (re-)extract these ModuleDataSetFiles. This verification is done based on comparing checksums (database contents versus local checksum which is logged in /temp/moduleDataSetsCheckSums). If a change is identified, files will be deleted and then re-extracted. Likewise, if no extracted files are found, a fresh extract will be performed.for the first time or after a new config revision set and a version of one of the listed module data sets is changed in the new config revision set. Since 2022.01 only the changed module data sets are re-exported.
The %REGION_HOME%/exportedModuleDataSetFiles.txt lists all the exported module dataset names and the files that are unzipped from the module dataset files. The listed files are first deleted before exporting a new version of a module dataset file. The exported version numbers of the exported module data set files are stored in %REGION_HOME%/temp/moduleDataSetsCheckSums
This option is mostly valid for FSSs since they are running the models. In fact: the complete structure on an FSS underneath the "/Modules/" folder should (ideally) be stored in one or more ModuleDataSet files. Only in this way, FSSs can be used for scaling up/down since its content is generated automatically. See below mentioned image with a number of references to ModuleDataSet files.
...
Unzips the VIC_Products.zip to %REGION_HOME%/products (d:\fews\fss\1\products ) ( /opt/fews/fss/1/products)Before FEWS 2022.02 all data sets are re-exported when one of the listed module data sets is changed
truststore
When the ssl certificate issuer used by a https web host mentioned in the FEWS configuration isn't bundled with the (Amazon) java run time you need to create a truststore file. Unfortunately this will not work when the certificate is used by the database connection itself.
...