The application control variable "vlxMode"

Usage

In the application definition in the VISULOX PORTAL Datastore, the variable vlxMode controls some parameters for the behaviour of the application.

The variable can be set in the Hints field of an application object in VISULOX PORTAL Console.

The format is:

CODE

vlxMode=flag:flag:flag

The following flags are possible:

Flag	Meaning
R	Enforce recording of the application. It overrides the recording flag in the Application Policy and the welcome message in Application Policy is overwritten with the the default text.
IU	Isolated User: Starts a visulox.exp application with its own transit user and Transit Zone (IU application must be started after the original app).
OCR	Enforce optical character recognition on the application.
WM	Add the VISULOX window manager with taskbar in the application. Only useful with X11 applications in Independent Window or Kiosk Mode The VISULOX window manager (default: JVM) is also used for example by VISULOX Jump Shells and can be changed with: visulox config -name x11.windowmanager
NOSC	No session controller. This is used, if an application should not be under control of the VISULOX Session Controller.
SYNC	The user's Transit Zone is provided into his shell or file explorer. All applications with visulox.exp, vlxUnix.exp and vlxWindows.exp (former: vlxRdp.exp) will get the VISULOX Transit Zone with vlxMode=SYNC set. On VISULOX Nodes wiithout VISULOX PORTAL Service, the replication has to be set at least to ftonly. sshfs must be installable. For OL 8 use "Oracle Linux 8 CodeReady Builder (x86_64) - Unsupported" as repository. If the user has two applications on the same server with the same shell. vlxTransit is seen in both applications, even if vlxMODE=SYNC is set only for one.
UPLOAD	The user's upload directory is provided into his shell or file explorer.
SCX<pixels>	The default value of the Session Controller GUI in Independent Windows mode is on the right hand side 10 pixel below the top. This can be not enough and covers part of the functionality in some applications (like desktops) . By adding SCX<int> via vlxMode the offset can be increased up to 200 pixels.
D<delayinms>	The SessionGuard (SG) is launched by VISULOX for any application which has to be controlled. The SG has to connect to the display after the application. The default delay value for the SG is 500ms. If application launch is slow, 500ms sometimes is not enough. vlxMode=D<delayInMs> can override this value. In Windows sessions, the ttaXPE should have the same color depth as the RDP session. In this case the "Delay" parameter is not needed. If different color depths are used, the color depth will be reinitialized, there are two possibilities: The "Delay" parameter can be used Testing different color parameters This is the preferred method because the "Delay" parameter does not lock the session until the session controller is up.

All applications with visulox.exp will have vlxtransit. Applications with vlxUnix.exp or similiar applications will have vlxtransit only, if VISULOX is running on the target system and if vlxMode=SYNC is set and the replication is at least ftonly.

Configuration for standard x11 and RDP / Windows applications

The vlxMode variable can be set for x11 and RDP applications in the Hints field on the General page of the application via VISULOX PORTAL Console:

For standard applications, a resource can be set as well in the hint field of the application with vlxResource=<resource-name>.

Related information

How to pass user credentials to an application - VISULOX Single Sign On - SSO