Automation Parameters / Silent Installation
work in progress!
Automating Login VSI
Components that support automation:
- Installers -- Target setup -- data server setup - Management console - analyzer
Target setup The target setup is a UI that drives a batch script. The batch script expects up to 6 parameters. These parameters control what application is being installed and which applications is not.
The first parameter controls if DoroPDF should be installed. Passing 0 means that DoroPDF will not be installed. Passing anything else will mean that DoroPDF will be installed.
The second parameter controls if Adobe Reader should be installed. Passing 0 means that Adobe Reader will not be installed. Passing anything else will mean that Adobe Reader will be installed.
The third parameter controls if Adobe Flash player should be installed. Passing 0 means that Adobe Flash player will not be installed. Passing anything else will mean that Adobe Flash player will be installed.
The fourth parameter controls if Java should be installed. Passing 0 means that Java will not be installed. Passing anything else will mean that Java will be installed.
The 5th parameter controls if a group should be added to the local Remote Desktop Users group. Passing this parameter will cause the value of the parameter to be added to the Remote Desktop Group.
For example: VSITarget.cmd 1 1 1 1 "LoginVSI" This will install every component and add a group named LoginVSI to the local Remote Desktop Users group.
Data server setup Supported parameters: -s \\server\vsishare -i -qb -ns
The s parameter indicates that the setup should run in silent mode. When using silent mode the setup will expect the VSIshare location to be specified along with the s parameter. A silent setup will not show any indication of starting, progressing and ending the setup. It is completely silent.
The i parameter indicates that the setup should ignore the server operating system requirement. This allows the data server setup to be ran from a desktop operating system. Keep in mind that running a VSIshare from a desktop operating system is not recommended because a desktop operating system has a limited amount of file server connections that are allowed.
The qb paramter is only usable in combination with the s parameter. The qb parameter will run the installer with a minimum GUI.
The ns paramter is only usable in combination with the qb paramter. Using the ns parameter will cause the installer not to install shortcuts
The management console has a command line interface that can be found in the VSIshare under _VSI_ManagementConsole\LoginVSICMD.exe. The command line interface accepts 2 parameters: - profile, profile is a profile saved using the save profile button in the GUI version of the management console - testname, the name of the test that you want to start Please note that while the command line interface for the management console will check if the session monitor and launcher(s) are running, it will not run the launcher workflow.
The analyzer has a command line interface that can be found in the VSIshare under _VSI_Binaries\Analyzer\Login VSI Analyzer Console.exe. The command line interface accepts 4 parameters:
- The first parameter is unnamed and is the path to the log folder you want to analyze.
- The second parameter is unnamed and is the path to a CSV file in which the results will get appended.
- The third is -graph, this indicates that the analyzer should generate an image of the VSI max graph in the indicated location.
- The fourth is -zero, this lets you generate results if VSImax is not hit.