Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 38 Next »

How to setup the launch of Delft-FEWS

There are a number of options when configuring the launch of your Delft-FEWS application. The most simple is to double click on the appropriate executable in the bin directory e.g. C:\FEWS\bin\Your_Region.exe - this will launch FEWS directly.

In the bin there will also be a file of the same name with the extension .jpif (e.g. Your_region.jpif). Since the executable is generic (except for the name) this file contains all the information required to launch your application.


The location of the JRE folder


Amount of memory available for FEWS






Application type*


Name of folder containing the configuration

*If wanting to use the config manager use line: nl.wldelft.fews.configmanagement.ConfigManagementApplication or for the launcher use nl.wldelft.fews.launcher.Launcher

It is possible to add JAVA runtime options the .jpif file.


JRE Folder


Set initial java heap space


Set maximum java heap space


Set PermSize (default 64m, which is sometimes too low and results into PermSize errors)


turns on/off all usage of Direct3D

Use the LAN system proxy settings (default FALSE)


switch on/off the rolling barrel (default TRUE) in the OC






$USER_HOME\Application Data\FEWS\Anglian_SA

Folder name of configuration, of which a working copy will be copied and used in the defined directory. The base directory should always be at the same level a JRE and BIN

Notice that JAVA system properties should be defined after the -D keyword.

How to launch Delft-FEWS using the launch menu

Organisations which have multiple instances of Delft-FEWS (for example multiple regions or online/shadow type systems) may wish to use the Delft-FEWS launcher.

You must create a folder in the root directory (same level as the bin and jre) which will contain the launcher configuration files (called for example FEWSLauncher). You will need to have an executable and jpif in the bin directory - you start the launcher by double clicking on the executable. But first we need to set up the launcher config files...

Firstly you can configure the password protected level of access required. Please note that this is not a highly secure method of password protection but is meant simply to restrict access to those who require it.

This is done using the security.xml file (details below). The passwords are contained in the binary security.sec file.

Once you have entered the correct password you will be shown the appropriate screen from which you can choose the FEWS appplication you wish to launch.

This is configured using the launcher.xml (details below). You can also display your organisations logo or picture of your choice by adding an image in the FEWSLauncher directory called LauncherImage.jpg of size 455 x 540 Pixels.


The security.xml file needs to follow the diagram in the following schema.

This security.xml contains the actions and roles required. The actions are linked directly to the launcher.xml. The 'role' describes which users are have access to which actions. For example a forecaster might have access to the explorer only, while a system administrator may have access to the admin interface and configuration management interfaces. For an example file click here. This file links actionIds to user roles.

The following actionIds are allowed:

  • ViewReports
  • LaunchFewsClient,
  • LaunchConfigManager,
  • LaunchAdminInterface,
  • Upload OnLine

In the example, the launcher is setup like the following:

  • The role of Forecaster has the privileges to run the fews client (LaunchFewsClient).
  • The role of ConfigManager is allowed to run fews, to run the configmanager, and upload files (LaunchFewsClient, LaunchConfigManager, Upload OnLine).
  • The SystemManager is allowed what the configmanager can do as well as login to the admin interface (LaunchFewsClient, LaunchConfigManager, LaunchAdminInterface, Upload OnLine).

Howto create a security.sec file from a security.xml is specified in the privileged section, see

security.xml can also be configured to skip the login window. For this to happen, configure as follows:

  • Specify only 1 role
  • The "password" element should be empty
  • The "noPasswordRequired" element should be set to "true"


This file contains the actions which are accessed through the launcher. The id links with the id given in the security.xml. You can see from the schema that the action can link to a web page (for example the admin interface) or to a java application (fews explorer or config manager). You will notice similarities between the attributes of the JavaAppType and those found in the .jpif file in the bin directory. An example file can be seen here

The jvm Option gives you the chance to tweak the heap size used by the java virtual machine. Use -Xms for the initial java heap size (e.g. -Xms256m), -Xmx for the maximum heap size (e.g. -Xms1G). The syntax is then as follows:

jvmOption="-Xmx1G -Xms256m"

If the javaApps defined only use one operation mode (e.g. Stand Alone), it is possible to hide the operation mode dropdown box in the launcher window by setting the "operationModeHidden" attribute to true.

  • No labels