Since 2014.02 configure a ini file
In the bin from before 2014.02 there will also be a file of the same name with the extension .ini (e.g. Your_region.ini. Since the executable is generic (except for the name) this file contains all the information required to launch your application. Since 2014.02 a Delft-FEWS.exe, Delft-FEWSc.exe and Delft-FEWS.ini are provided in the Delft-FEWS bin dir. The Delft-FEWS.exe can be renamed to a more suitable executable name, e.g. Midlands_SA.exe, Midlands_OC.exe, Midlands_DDA.exe. The executable needs to have a file with the same base name with the .ini extension, e.g. Midlands_SA.ini, Midlands_OC.ini, Midlands_DDA.ini. You can use the sample Delft-FEWS.ini provided in the bin directory as a starting point. Below you will find a description of the entries that can be specified in the .ini file.
JVM arguments are all specified in a ascending order without gaps, i.e. vmarg.1, vmarg.2, .., vmarg.n. Similarly, command-line arguments are all specified in a numbered fashion such as arg.1, arg.2, .., arg.n. For specifying where to find the region home directory you will need to specify arg.1=<region_home>.
The location of the JRE folder
|#JVM arguments -X and -D are added as vmarg.|
|vmarg.1=-Xms512m||Initial amount of memory available for FEWS|
Amount of memory available for FEWS
all the jars in the Delft-FEWS bin dir forming the classpath
Location of the Delft-FEWS bin dir
Path to the folder containing the configuration. Note that when the tag $USER_HOME$ is part of the foldername, it will be resolved by Delft-FEWS to the user.home directory.