Depending on the local installation Delft-FEWS can be started using the Application Launcher or by using an executable program located in the Delft-FEWS binary directory (usually a link/shortcut will have been set up). On Linux systems Delft-FEWS is started using a shell script. When using the Application Launcher a user must select a profile and enter the required password at startup.
There are four profiles with each of them its own password:
- Configuration Manager
- System Manager
The Viewer profile is the most restricted profile, a user with this profile can only launch the FEWS Webserver. The System Manager Profile, on the other hand, has all the rights to launch Stand Alone and Operator Clients, launch the Configuration Manager and use the Admin Interface. Depending on the configuration of FEWS all or some profiles may be present.
A screen dump of the FEWS Application Launcher for the National Flood Forecasting System for England & Wales is presented as an example below.
Configuration changes when migrating to 2018.02
The launcher GUI is also available in 2018.02 (and higher). A few changes have to made to get this working (when migrating to 2018.02).
Below described example is based on the following directory structure:
/bin (directory containing the Delft-FEWS 2018.02 binaries)
/FewsSC_OC-DDASB (directory containing an Operator Client)
/FewsSC-SA (directory containing a Stand Alone)
/FEWSSC_Launcher (directory containing the Launcher files)
Assuming there is a launcher directory which should contain the following files
If you are using the launcher before 2018.02 you should replace the Launcher.exe and the Launcher.ini (click on the links to download the new versions). Please overwrite the old ones with these new files.
In the Launcher.xml 4 different actions can be configured:
The IDs of the 4 actions must match exactly. All paths configured can be relative paths.
Within the action tags you can choose from 3 options for the configuration. Use webPage for ViewReports and LaunchAdminInterface. Use executable for LaunchFewsClient and LaunchConfigManager. The third choice, javaApp is no longer supported since 2018.02.
The launcher.xml example below is consistent with the directory structure explained in the beginning of this section.
A few remarks:
- the <appPath> element is new in 2018.02
- All CAPITALIZED parts from the example below should be adjusted to your situation:
- -Dregion.home arguments should be pointing to existing directories
- for launching the Config Manager, the Database URL should also be specified (-Ddatabase.url)