How to handle different client versions on one platform with vlxshell

VLX Shell is being used as a framework to different clients (Xterm, Gnome, Firefox, RDesktop, ICA, freeRDP). 
Depending on the client, the vlxtransit directory is provided. (Firefox as the default download directory, RDP or ICA drive redirection).

The client binary is searched in some dirctories during startup:

/usr/bin, /usr/local/bin, /usr/lib/ICAClient, /usr/opt/Citrix/ICAClient, /opt/Citrix/ICAClient

If the client is not found an error is thrown. It is also possible to address the client binary directly using the -clientcmd option.

vlxshell.tcl -client firefox -clientcmd /path1/firefox

With this option it is possible to address different versions of the client with the same type on the same platform.

vlxshell.tcl -client firefox -clientcmd /path1/firefox
vlxshell.tcl -client firefox -clientcmd /path2/firefox
vlxshell.tcl -client firefox -clientcmd /path3/firefox

vlxshell.tcl -client ica -clientcmd /path1/wfica
vlxshell.tcl -client ica -clientcmd /path2/wfica

 More useful parameters of vlxshell.tcl

• When application launch is slow, the session is closed by the VISULOX PORTAL Service because of an empty screen.
  The following parameter will keep the session open, so the application now has time to launch:

  CODE

  vlxshell.tcl -wait <sec>

  This allows to give slow connections a chance for presentation.
  
  

• Activate vlxtransit and vlxupload for the application:

  CODE

  vlxshell.tcl -sync

Related articles

VISULOX user sandbox (vlxjail)

Enable events for VLX Shell, FreeRDP and File Transit connections

VISULOX Firefox Wrapper setup

VISULOX Firefox integration