Area: Web Start configuration

SiteArchitect and ServerManager are started via the FirstSpirit Launcher.

Launcher: The FirstSpirit Launcher provides a continuously updated, extensively tested, and license-free Java Runtime Environment which is rolled out when the Launcher is installed. This allows SiteArchitect and ServerManager to be operated in a preconfigured environment which is independent of the Java version on the client computer – even if there is no Java version installed at all.

The parameters for starting the FirstSpirit applications (SiteArchitect and ServerManager) are transferred to the FirstSpirit Launcher via the .fslnch configuration file.

The configuration is set:

• global (server-wide): via FirstSpirit ServerManager (see Webstart). A graphical user interface is provided for the configuration in the ServerManager. The values configured there are adopted to the fs-server.conf configuration file (see below).
• user-specific: via the connection settings on the FirstSpirit start (see page User).

Web Start configuration for starting the FirstSpirit SiteArchitect: the parameters configured here affect all “SiteArchitect” type quick-start entries on the start page if no other parameters were explicitly defined for the entry in the “Start page” area (see Start page).

webstart.client.connection=
webstart.client.server=
webstart.client.port=
webstart.client.memory=
webstart.client.compression=
webstart.client.encryption=
webstart.client.servletZone=
webstart.client.usehttps=
webstart.client.parameters=

The configuration options correspond to the user-specific Web Start configuration (see User).

TLS encryption (parameter value 1) cannot be used for the webstart.client.encryption parameter if WebSphere is used as the application server for the fs5root web application. In this case, ChaCha20 encryption (parameter value 2) is available for SOCKET or HTTP implementation or HTTPS use. When using HTTPS, encryption is not necessary and therefore parameter value is to be set to 0.

Configuration for the ServerManager application:

webstart.admin.connection=
webstart.admin.server=
webstart.admin.port=
webstart.admin.memory=
webstart.admin.compression=
webstart.admin.encryption=
webstart.admin.servletZone=
webstart.admin.usehttps=
webstart.admin.parameters=

The configuration options correspond to the user-specific Web Start configuration (see User).

TLS encryption (parameter value 1) cannot be used for the webstart.admin.encryption parameter if WebSphere is used as the application server for the fs5root web application. In this case, ChaCha20 encryption (parameter value 2) is available for SOCKET or HTTP implementation or HTTPS use. When using HTTPS, encryption is not necessary and therefore parameter value is to be set to 0.