SLLauncher can optionally be used with any published application running on the Citrix server. This is to preserve backwards compatibility with pre-6.1 Citrix published applications that were created using the sllauncher.exe in the Citrix published application shortcut, and also to specify use of sllauncher.exe command line switches as detailed in Using SLLauncher Syntax.
If SLLauncher is not found within the server's path environment variable, you must include the full path to SLLauncher. For example, replace the command line of the published application as follows:
|
Before |
After |
|---|---|
|
C:\Program Files\NetIQ\SecureLogin\tlaunch.exe /q /auto /eWallData Rumba /pnetiqMainframe |
SLLauncher.exe C:\Program Files\NetIQ\ SecureLogin\tlaunch.exe /q /auto /e“WallData Rumba” /pnetiqMainframe |
To run SLLauncher, use the following command:
SLLauncher [/wd] Citrix Published Application Parameters
IMPORTANT:If your executable contains a path or command line parameters that include spaces, enclose the spaces in quotes. Even if your application normally accepts the parameters with spaces, SLLauncher interprets them as separate parameters, and unexpected results might occur.
SLLauncher includes two command line parameters that control its behavior:
Table 5-2 Command Line Parameters
|
Parameter |
Explanation |
|---|---|
|
/w executable name |
Specifies another process to wait for before closing SecureLogin. Example, SLLauncher.exe /w rumbadsp.exe C:\Program Files\NetIQ\SecureLogin\tlaunch.exe /q /auto /e"WallData Rumba" /p"netiqMainframe" SLLauncher.exe /w mspaint.exe run_MSPaint.CMD |
|
/d |
Debug option. This option generates a debug log file (c:\sllauncher.log) and shows dialog boxes during the progress of SLLauncher. The switch must appear before the executable that you want to run. Examples: SLLauncher.exe /w rumbadsp.exe /d /p"netiqMainframe" C:\Program Files\NetIQ\SecureLogin\tlaunch.exe /q /auto /e"WallData Rumba" SLLauncher.exe /w /d mspaint.exe run_MSPaint.CMD |