...

Figure 1: Illustration of interaction between Data Interface Module (DiM) and Data Conversion Module (DCM).

Binaries / installation

For FEWS versions 2018 and earlier The DCM had a separate bin folder and its own patches and was using the installed Java runtime version 1.8 (or earlier) These can still be requested through FEWS Support.

Starting with FEWS release 2019.02 rather then distributing a separate bin folder (which would need to include Java 11 runtime files) the choice was made to include DCM in the main FEWS distribution. The code of the data conversion module is now part of the main Delft_FEWS.jar and is run using the Delft-FEWSc.exe executable. The deliverable package for DCM that can be requested through FEWs support now contains a standalone configuration to use as a template for you project and a startup script (DataConversion.sh / DataConversion.bat) that you can use to start the DCM.

To install the DCM, the procedure is pretty much like any FEWS installation, the main difference difference is that after installing a base-build, you request from the same branch the data conversion package, with the file name dataconversion-stable-NNNN,NN.zip (where NNNN.NN is the FEWS version number) and unzip this as your region home folder. Then finally you get the latest FEWS patch for the given branch, however instead of putting the patch in the  region home folder you need to put it in the main DCM folder and rename it to patch.jar.

Configuration

File structure of DCM after installation

...

• bin                               Directory containing the FEWS distribution (2019.02 or newer)
• patch.jar                       latest patch file for this FEWS distribution
• DataConversion_SA     FEWS Region Home directory for the DCM (contains the XML-configuration files)
• DataConversion.bat     Script file needed to run DCM on a Windows machine
• DataConversion.sh       Script file needed to run DCM on a Linux machine
  
  

...