...
Since 2014.02 a Delft-FEWS.exe, Delft-FEWSc.exe and Delft-FEWS.ini are provided in the Delft-FEWS bin dir. Delft-FEWSc.exe is a console version of Delft-FEWS.exe and is only recommended when a console is required. The Delft-FEWS.exe can be renamed to a more suitable executable name, e.g. MyRegion_SA.exe (Stand alone), MyRegion_OC.exe (Operator Client), MyRegion_DDA.exe (Direct Database Access) or MyRegion_CM.exe (ConfigManager) depending on your needs. The executable needs to have a file with the same base name with the .ini extension, e.g. MyRegion_SA.ini, MyRegion_OC.ini, MyRegion_DDA.ini or MyRegion_CM.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. For specifying where to find the region home directory you will need to specify arg.1=<region_home>.
The two executables are copies of java launchers provided by winrun4j. (see http://winrun4j.sourceforge.net)
Sample Delft-FEWS.ini
Code Block |
---|
#Delft-FEWS ini file main.class=nl.wldelft.fews.gui.explorer.Application classpath.1=*.jar #Java Runtime jvm.dll location vm.location=../jre/bin/client/jvm.dll vmarg.1=-Xms512m vmarg.2=-Xmx1024m #location of the bin dir working.directory=. #region_home directory - <region_home> to be replaced with actual region home directory arg.1=../<region_home> #optional splash file - <region_home> to be replaced with actual region home directory #splash.image=../<region_home>/splash_screen.jpg #optional debug log - enable these #log and #log.overwrite for obtaining debug logging when the application fails to start, <region_home> to be replaced with actual region home directory #log=../<region_home>/startup_debug_log.txt #log.overwrite=true |
...