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 13 Next »

How to launch 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 (i.e. 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

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 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.


This file 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 security.xml.

  • No labels