This section demonstrates the common download and installation steps for all the launcher applications. Each launcher application has an install wizard that will guide you through the installation process. The installation steps are common for all the launchers with a few exceptions depending on the operating system you're using.
Although you can run the Ignition Gateway and Perspective Sessions on ARM-based Desktops (such as a Raspberry Pi), the Designer, Vision Client, and Perspective Workstation cannot be run on ARM-based Linux machines. Instead, the Designer, Vision Client, or Perspective Workstation will need to be installed and run from an Intel-based machine.
For the sake of brevity, this section will focus on installing the Designer Launcher, but the steps for installing the Vision Client Launcher and Perspective Workstation are all very similar.
Work through the install wizard. There are only a handful of options in the installer:
Whether or not to create a desktop icon
The installation directory for the launcher.
If this is a first time install, the Designer Launcher wizard has an additional step. It will prompt you to select the install mode. Installing locally installs the launcher in the user's AppData\Roaming folder whereas 'all users' installs it in Program Files.
To install the Designer Launcher application, drag the Designer Launcher icon to the Applications folder.
Extract the contents of the 'tar.gz' file to your desired install location.
Navigate to your install folder, and click the 'designerlauncher.desktop' file. A message box may popup about the launcher application being an untrusted application. Click Trust and Launch.
Once the installation process reaches its end, click Finish .
Whenever an Application is launched from a Launcher, the Launcher will check to see if it needs an update. If the Gateway containing launched application is several revisions ahead of the Launcher, the Launcher will provide a popup notifying you that an update is available.
However manual upgrades can be performed. Simply download and run a new launcher installer from a more recent Ignition Gateway. During installation, simply set the installation directory to the same directory as the old launcher.
You can return the Vision Client Launcher, Perspective Workstation, and Designer Launcher versions using your operating system's terminal (PowerShell for Windows). The following table lists the commands for returning the version number by launcher:
The process for adding Applications/Designers to the Designer Launcher is very similar to adding Applications to the Vision Client Launcher and Perspective Workstation. This section demonstrates how to add new Applications.
The following Designer Launcher example is used to show how to add applications for the Designer and Vision Client Launchers and the Perspective Workstation.
Once added, the new Applications will appear on the starting screen of the Launcher.
# Shows a simplified user interface C:\Users\user\Downloads\VisionClientLauncherSetup.exe /CURRENTUSER /SILENT # Shows no user interface at all. C:\Users\user\Downloads\VisionClientLauncherSetup.exe /CURRENTUSER /VERYSILENT # The following option installs silently without installing a desktop shortcut C:\Users\user\Downloads\VisionClientLauncherSetup.exe /CURRENTUSER /VERYSILENT /MERGETASKS="!desktopicon"
Commands above are taken from: https://jrsoftware.org/ishelp/index.php?topic=setupcmdline
Using ALLUSERS may trigger a check from User Account Controls, so you may need administrator access for the following command to offer a truly silent installation:
Normally, each Ignition Gateway includes files for the various launchers. When you download a launcher from a Gateway, it will stream its local launcher files. However, you can override this behavior, causing the Gateway to ignore its local launcher files and instead download launchers from the internet. For more information, see the Gateway Configuration File Reference page.
Installers for Windows systems in
.msi format are available on the Inductive Automation downloads page. To access them, click on either "Other operating systems and versions" or "Other Versions" on the downloads page, and scroll down to the "Launchers" section.
.msi installers help make pre-deployment easier in enterprise environments and utilizes existing Windows Installer toolchain features. Notably,
.msi installers support two features which make large-scale deployments easier:
If you wanted to download one of our hosted launchers, without modifying your Gateway's configuration file, you can download them directly from your web browser:
Where VERSION is the Ignition version (i.e., 8.1.0), and LAUNCHER is the name of the launcher. Launcher names are listed below.
|Launcher||Operating System||Launcher Name|
For example, the following would download an 8.1.0 version of Perspective Workstation for Windows:
When a shortcut to an application is created, a launchable link is placed on the desktop of the user. This link uses the configuration of the application that is saved in the launcher. This ensures that updates to the launcher are respected even if the link was created before the changes. That being said, you can override the following settings for the shortcut itself:
The values for these settings can be found elsewhere in this User Manual: general launchers settings are on the Launcher Settings page, while each of the three launcher pages list settings unique to particular launcher.
Add additional arguments to the end of the Target field:
Add additional arguments to the end of the command, but before the &”:
... -Dapplication=test -Dwindow.mode=fullscreen
You can also redirect the cache directory that is used by the launcher. Typically the user’s cache is in their home directory in the “.ignition” directory. This holds all the resources that are required for launching a client as well as the resources for each launcher. Sometimes this is not desirable, for example in cases where you want a global cache that all users on a machine rely on or when you want the users client cache to reside in a different directory under AppData.
To change this directory, place a file named
redirect.txt inside the
.ignition directory in their user home directory. This file should have a single line in it which is an absolute path to the appropriate file.