...
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.
...
Howto create a security.sec file from a security.xml is specified in the privileged section, see http://publicwiki.deltares.nl/display/FEWSDOC/Other+related+installation+information.
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"
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
...
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.