The Designer Launcher can now be installed as an "all user" application on a Windows operating system providing launcher access to all users on the same machine from a single installation. The first time you install the Designer Launcher, you will be prompted to select your install mode: "Install for me only" or to "Install for all users." If the Designer Launcher was already installed, subsequent install attempts are treated as an upgrade and you will not be prompted to select the install mode. This new option will only appear on new launcher installations, or after uninstalling a prior version of the installer.
When installing for "all users," the installer will be placed in the following folder: "%Ignition Installation Directory%\Program Files\Inductive Automation."
The Designer Launcher for Windows, Linux, and Mac OS are available on the Home tab of the Gateway Webpage. Use the following steps to do an install of the Designer Launcher.
From the Gateway Webpage, click the Download button for the Ignition Designer Launcher.
Run the downloaded file (DesignerLauncherSetup.exe) found on the lower-left of the window, or go to your Downloads folder and double-click the file to run it.
If this is the first time installing the Designer Launcher, you will be prompted to select an install mode. Select either "Install for me only," or "Install for all users."
The Install Wizard will select a default destination location folder for the Designer Launcher application files. If you are "installing for me only", the destination folder will be different from the "all users" destination folder.
The Designer starts up and the login window is displayed. Enter the credentials for the administrator or user with full privileges for the Designer, and click Login. It should be the same as the login for the Gateway Config section.
Login credentials are set in the Config section of the Gateway Webpage, under Security > Users, Roles.
Replace the image above with the one below. No banner necessary.
Configuring the Designer Launcher is fairly simple. The Designer Launcher finds the Gateways, you add the Gateways to My Designers, and the only thing left to do is create your Designer shortcuts. You can create a shortcut for each Designer, or use the Designer Launcher to display all your Designers. Creating shortcuts makes them readily accessible for opening a Designer quickly. Let's open the Designer Launcher to create a few shortcuts.
If you followed the steps in the previous section for installing the Designer Launcher, then you already have the Designer Launcher shortcut on your desktop which looks like the image below.
If you don't, then go back to the Gateway Webpage and download and install the Designer Launcher again. Follow the wizard instructions as shown in the previous section. Be sure to check the Create a desktop shortcut on the Select Additional Tasks window.
Find the Designer Launcher shortcut on your desktop and click it to open the Designer Launcher window. A list of Designers will be displayed.
Go to your desktop and click the shortcut to open your Designer. You'll notice that name of your Designer is also the name of the shortcut (i.e., Controller).
You have the option of customizing the Designer Launcher Settings.
When the Designer Launcher Settings window opens, you can choose to use the default settings or customize each Designer. When finished, click Save Changes.
|Launcher Settings - Configurations for the Launcher|
|Property Setting||Description||JSON Name|
|Default Application||When set, the Launcher will attempt to automatically launch the specified Application when running. If left blank/null, an Application will not automatically start|
|Logging Level||Level of logging that will be used for the launcher: INFO, TRACE, DEBUG, WARN, and ERROR.|
|Multicast Address||The address that will be used to listen for multicast broadcasts from Gateways.|
|Multicast Ports||The port that will be used to listen for multicast broadcasts from Gateways.|
|Auto Exit on Launch||Automatically close the launcher window when a client is started.|
|Application Defaults - Default Configurations for New Applications|
|Property Setting||Description||JSON Name|
|Timeout||Maximum number of seconds allowed for any Gateway communication. Any communication that exceeds this amount will cause the client launcher to abort the communication and try again if configured.|
The number of times a Client will to attempt to contact a gateway again if an error occurred during communication. Available values are:
|Initial Heap||Amount of memory to be allocated at startup.|
|Max Heap||Maximum amount of memory allocation for heap size.|
|JVM||Arguments to append to client startup. These should start with a '-D' and be separated by semi-colons.|
|Client TagOverrides||Client Tags and their values that are set when the client launches.|
There are three different Action buttons in settings in the Designer Launcher.
|Export Launcher Config||Exports all Designer Launcher settings to a json file.|
|Import Launcher Config||Imports Designer Launcher settings from a json file.|
|Import Application Config||Imports a Designer configuration from an export json file.|
Adding additional Designers is simple since the Designer Launcher does all the work for you.
|Application Name||The name of the Designer application, as it appears in the launcher.|
|Timeout||The maximum number of seconds to allow for any gateway communication. Any communication that exceeds this amount will cause the Vision client launcher to abort the communication and try again if configured.|
How many times to attempt to contact a gateway again if an error occurred during communication. Available values are:
|Initial Heap||The initial heap size (memory) for the client.|
|Maximum Heap||The maximum heap size (memory) for the client.|
|JVM Arguments||Additional JVM arguments to add to that specific application if desired. The defaults are created from the global jvm-args that exist at the time of the creation of the application. These can then be modified and the modifications will persist and never be updated again from the global setting.|
When using a self-signed SSL certificate, the certificates for the gateway must be locally accessible to the client launcher in the following directory:
When a certificate is placed in the directory above, the launcher will attempt to automatically add the certificate(s) to the local keystore upon application launch.
If the Designer Launcher fails to launch a designer for some reason, the log file can be found at:
This log should contain any errors that occurred.