#Admin Console

For configuration, management and monitoring purposes Webswing provides a convenient web interface.

#Installation

Since Webswing 20.2, Admin Console is distributed as a standalone web server application in its own war file. To start Admin console simply run webswing&admin.bat on Windows to start both Webswing and Admin Console. On Linux, you start Admin Console separately using admin.sh which you can find in admin folder in the distribution package. You can also deploy the webswing-admin-server.war manually in a servlet container, however this has not been documented yet.

To connect Webswing server with Admin Console server, you have to configure following:

• Admin Console URL in webswing.config file
  • under "/" path set field "adminConsoleUrl": "http://localhost:8090" or the current URL where your Admin Console server is running
• Connection secret in webswing-admin.properties
  • use the same webswing.connection.secret value as configured in webswing.properties file

The admin folder also contains two configuration files:

• jetty.properties - similar to Webswing server jetty configuration, configure host, port and SSL here
• webswing-admin.properties - several Admin Console server properties described in a table below

By default, Admin Console server runs on http://localhost:8090. You can either access it directly on this URL or click the Manage link in the application selector.

If you don't want to use Admin Console and want to remove the Manage link from selector, simply remove adminConsoleUrl field from your configuration in webswing.config.

#Overview

This section shows you the overview of the server statistics. You can see how many session pools are available, how many users are connected, how many instances are running and how many apps are configured. You can also enable verbose mode and go to server logs.

On the left sidebar, under the statictics you have server configuration option. Server configuration form allows you to configure your server.

#Applications

Applications section is for applications management and configuration. In this section you can see the list of all existing apps.

You can select and configure, enable/disable or remove a single application, also create new or duplicate selected one. For more details on how to configure your application please refer to this page.

#Sessions

In the top navigation bar you can access Sessions. This page contains table of Running & Finished sessions, which you can filter by selecting the application name on the left sidebar. There are also options to filter and sort the sessions list.

#Running

Here you can see details about each running session with options to shutdown, create thread dump, record or view the session detail. When you extend the table by clicking toggle switch on the top of the table, It will become wider with more details such as session metrics (aggregated data about CPU, RAM and network consumption) and IDs needed for session identification.

#Finished

In Finished sessions tab you can see the history of all finished sessions with some useful details - username, IP address, session duration and warnings.

#Session Detail

Session detail view contains all the details, metrics and options for session management & monitoring. There are also controls for mirror view, recording & playback, session logs and warnings.

#Latency

The Latency Graph consists of the following partial graphs

1. Average HTTP ping latency - delay between sending a request and obtaining response (no business logic is performed on the server)
2. Average Server Rendering latency - delay between sending user event to Swing app and receiving rendering event from the AWT framework
3. Average Client Rendering latency - delay between receiving rendering event and displaying it to user in JavaScript
4. Max E2E frame based latency - latency from the user event to server + server rendering + sending the change back to user + client rendering

#Customization

By default the graphs show CPU/Memory usage history of the last 10 minutes. This is due to memory requirements of the data. The defaults can be changed during startup of Webswing Server by providing specific System properties. Please note that low interval and high history size results in extended Memory and CPU usage.

webswing.stats.interval=10 (Granularity of the metrics, average of last 10 seconds is default)
webswing.stats.historySize=60 (Number of observations kept in memory, 60 by default)
webswing.stats.memUsageWarn=0.8 (Threshold to generate a memory usage warning, 80% default)
webswing.stats.latencyWarn=700 (Threshold to generate a network latency warning, 700ms default)
webswing.stats.pingWarn=500 (Threshold to generate a ping warning, 500ms default)

#Mirror view

In the session detail page you can click the Mirror View button to see the live view of the user's session. You can take control of the session using the Control switch.

#Mirror and recording consent

Using mirror and recording feature by administrator may bring privacy concerns for your end-users. In that case you can enable requesting user consent before mirror view or recording starts. Simply enable Require Recording Consent or Require Mirroring Consent in your application configuration.

If you'd like to change the text in consent dialogs, add the following system properties to vmArgs configuration of your application:

#Logs

In the top navigation bar you can access Logs. Within the logs page 3 types of logs are accessible:

• Audit - application access logs (audit.log)
• Server - server and application event logs (webswing.log)
• Session - application event logs, as configured in the application (if session logging is enabled)

Logs section provide you with ability to view any logs mentioned above in your browser, but if you prefer to download them, you can do so by clicking the download icons above logs table or in sidebar

#Hide configuration options in Admin Console

In webswing.config it is possible to define set of configuration fields that will be hidden in Admin console. The value of these hidden fields will only be visible in JSON view and changes of hidden fields will not be allowed. This settings are useful for example if you need to forbid access to session recording or session mirroring, you can disable these features in configuration and blacklist the configuration option to prevent users simply re-enabling it in admin console. Blacklisted configuration options can only be changed directly be editing the config file.

Blacklisting configuration fields can be done using "blacklist" field followed by array of blacklisted fields:

"blacklist" : [ "mirroringAllowed", "recordingAllowed" ],

Alternatively you can decide to blacklist everything and then only allow changing only selected options using blacklist/whitelist combination:

"blacklist" : ["*"], "whitelist" : ["maxClientsPerUser","dataStore" ],

All configuration fields can be blacklisted and whitelisted (except nested ones). For example, inner entries in the "security" entry can't be blacklisted, only the whole "security" entry can be blacklisted.

When an entry is blacklisted and whitelisted at the same time, entry will be displayed, because the whitelist has higher priority.

In cluster server the configuration of the application is divided into web config and app config (entries in "swingConfig" entry, in standalone server case) we have to blacklist / whitelist entries in these configuration areas separately.

STANDALONE DEPLOYMENT EXAMPLE

Server configuration (webswing.config) example:

"/swingset3" : {
  "path" : "/swingset3",
  "name" : "SwingSet3",
  "enabled" : true,
  "icon" : "icon.png",
  "security" : {...},
  "blacklist" : [ "mirroringAllowed", "recordingAllowed" ],
  "whitelist" : [ ]
  ...
  "swingConfig" : {
    "directdraw" : true,
    "fontConfig" : {...},
    "launcherConfig" : {...},
    "blacklist" : [ "*" ],
    "whitelist" : [ "directdraw", "fontConfig", "launcherConfig" ],
     ...
  },
},

CLUSTER DEPLOYMENT EXAMPLE

Cluster server configuration (webswing-server.config) example:

"/swingset3" : {
  "path" : "/swingset3",
  "name" : "SwingSet3",
  "enabled" : true,
  "icon" : "icon.png",
  "security" : {...},
  "blacklist" : [ "mirroringAllowed", "recordingAllowed" ],
  "whitelist" : [ ],
  ...
},

Session pool configuration (webswing-app.config) example:

"/swingset3" : {
  "directdraw" : true,
  "fontConfig" : {...},
  "launcherConfig" : {...},
  "blacklist" : [ "*" ],
  "whitelist" : [ "directdraw", "fontConfig", "launcherConfig" ],
  ...
},