Note: Launcher groups are required for all type of (Continuous, Load and Application test environments). Read below on how to create Launcher groups.
Note: Search capabilities are only available in version 4.9.X and higher of Login Enterprise
This section will show you the status of the Launchers that are currently available. The system requires a minimum of one Launcher for any connections other than the Desktop Mode. The Launcher will also need the relevant connection client installed.
You can use the search function to search for a specific launcher.
When Login Enterprise is updated to a new version, Launchers may also be updated to take advantage of new features and functions. When there is a version mismatch between the Virtual Appliance and the Launcher it will show in the Launcher status pane.
Installing Login Enterprise Launchers
To add Launchers to the Login Enterprise environment, download the installation file. You can choose between the 32bit and 64bit version of the Launcher. The 32bit installer is primarily designed for windows thin-clients.
NOTE: Starting with Login Enterprise version 4.10 our launcher software will install to the following location: "C:\Program Files\Login VSI\Login Enterprise Launcher\LoginEnterprise.Launcher.UI.exe".
Please make sure update any scripting or automation that is based on the former install directory for Login Enterprise Launchers version 4.9 and earlier.
- Microsoft .NET Framework 4.6.1
The instructions below will show you how to do so.
- Click the download arrow at the end of the row to download the Launcher zip file
- Extract the Launcher zip file and run the Setup.msi file on the Launcher machine you want to execute the test sessions
Once the Launcher has been installed on the target machine you can start the launcher. As of Login Enterprise 4.10, the Launcher interface looks like this:
The Windows 7 Launcher is command-line based due to some web limitations. The Launcher functions the same way but simply looks different;
As of 4.11, all new Login Enterprise installations will come with a default "All" Launchers Group. This group will contain all existing Launchers, as well as any that are added later. This "All" Group is not permanent, and can be deleted if desired.
Launcher groups are used to specify which Launchers should be used for a particular test. Having at least one Launcher Group is a requirement, because creating a test requires at least one Launcher Group. This is helpful when trying to logically divide Launchers, for example based on geographic location. There are two ways to create a Launcher Group: through a Filter, or by Selection. Click the green "+" button, and select your method for grouping.
You can use the search bar to search for a specific group or description.
Selecting Filter will allow you to fill out the details and the launchers you want to add to the group. You can also use wildcards so you will not have to enter 20 different launcher names. Wildcards accepted include * and ?.
Using the Selection method to group launchers will allow you to manually select launchers to add to the new group.
To facilitate automatic deployment and update we have added commandline functions to the launcher installation.
If you want to run the msi file silently you can use these command line parameters (replace url and secret of course):
msiexec /I "\\fileserver\share\Setup.msi"/qb! serverurl=https://loginvsi.demo.com secret=E0733F0B555035C7E377CA8797530855770141C1
The launcher secret can be found in the launcher page under the download section: