| scrollbar |
|---|
| Anchor | ||||
|---|---|---|---|---|
| ||||
Launching Delft-FEWS
Depending on the local installation Delft-Fews FEWS can be started using the Application Launcher or by using an executable program located in the Delft-Fews FEWS binary directory (usually a link/shortcut will have been set up). On Linux systems Delft-Fews 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.
...
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).
...
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.
Launcher.xml (example)
In the Launcher.xml 4 different actions can be configured:
ViewReportsLaunchFewsClientLaunchConfigManagerLaunchAdminInterface
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 explain explained in the beginning of this section.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2009 sp1 (http://www.altova.com) by ICT (Stichting Deltares) -->
<launcher xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/launcher.xsd">
<action id="LaunchFewsClient">
<!-- FEWS Clients-->
<executable>
<appPath>../bin/windows/Delft-FEWS.exe</appPath>
<region>FEWS Scotland</region>
<operationMode>OnLine</operationMode>
<arguments>
<argument>-Dregion.home=../FewsSC_OC-DDASB</argument>
<argument>-Wsplash.image=.\fews-splash.jpg</argument>
</arguments>
</executable>
<executable>
<appPath>../bin/windows/Delft-FEWS.exe</appPath>
<region>FEWS Scotland</region>
<operationMode>StandAlone</operationMode>
<arguments>
<argument>-Dregion.home=../FewsSC_SA</argument>
<argument>-Wsplash.image=.\fews-splash.jpg</argument>
</arguments>
</executable>
</action>
<action id="LaunchConfigManager">
<!-- FEWS Clients -->
<executable>
<appPath>../bin/windows/Delft-FEWS.exe</appPath>
<region>FEWS Scotland</region>
<operationMode>OnLine</operationMode>
<arguments>
<argument>-Dregion.home=../FewsSC_OC-DDASB</argument>
<argument>-Ddatabase.url=INSERT SAME DATABASE URL AS FOR OPERATOR CLIENT</argument>
<argument>-Wsplash.image=.\fews-splash.jpg</argument>
<argument>-Xmx512m</argument>
</arguments>
</executable>
</action>
<action id="LaunchAdminInterface">
<webPage name="Admin Interface (1)" appPath="C:\Program Files\Internet Explorer\iexplore.exe" arg="http://COMPLETE URL TO ADMIN INTERFACE"/>
<webPage name="Admin Interface (2)" appPath="C:\Program Files\Internet Explorer\iexplore.exe" arg="http://COMPLETE URL TO ADMIN INTERFACE"/>
</action>
<action id="ViewReports">
<webPage name="FEWS Trouble-Shooting" appPath="C:\Program Files\Internet Explorer\iexplore.exe" arg="ANY HTTP(S) URL TO BE OPENED"/>
</action>
</launcher>
|
4 different actions can be configured:
ViewReportsLaunchFewsClientLaunchConfigManagerLaunchAdminInterface
The IDs of the 4 actions must match exactly. All paths configured need to be absolute paths, not relative.
...