| Table of Contents |
|---|
Root configuration files
The following root Configuration Files are required or optional for either an Operator Client (OC) and a Forecasting Shell Server (FSS)
...
Optional element with references to all ModuleDataSet files which should be extracted when an OC or FSS starts. Mostly the ModuleDataSetFiles 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 by comparing the version number that is held in the database versus the version number of what has been extracted. The latter information is held in the exportedModuleDataSetFiles.txt file in region_home. If a newer version is found in the database, files will be re-extracted. Likewise, if no extracted files are found, a fresh extract will be performed.
This option is mostly valid for FSSs since they are running the models. In case of using the new Web Browser Display this option should also be used to distribute the required libraries for an OC. 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.
In case of using the new Web Browser Display this option should also be used to distribute the required libraries for an OC.
The exportDir is relative to %REGION_HOME% unless otherwise specific. The name references the moduleDataSet file-name without the zip-extension. It is not required register to this file-name as a moduleInstanceId.
...