...
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.
security.xml
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 click here. This file links actionIds to user roles.
...
- 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).
...
- The encryption of the security.xml
...
- into a security.sec file can be done by the EncryptionDialog-tool.
EncryptionDialog under Windows
Under Windows create the following jpif in the bin dir, and copy the FEWS<regionconfigname>.exe file to a file named EncryptionDialog.exe.
This will start up a
| Code Block |
|---|
..\jre
-mx128m
-cp
$JARS_PATH$
nl.wldelft.fews.encryption.EncryptionDialog
|
...
launcher.xml
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
...