When the client launcher opens for the first time, you must select a Gateway on the Gateway Configuration screen. If your Gateways have multicast enabled, and multicast transmission is allowed on your network, you can see a list of Gateways under the Available Gateways tab. Select a Gateway from the list and click the Select Gateway button. The client launcher will attempt to connect to the Gateway that you selected.
If you do not see your Gateway, you can still manually enter Gateway address under the Manually Input Gateway tab. The format is "host:port":
After you have entered your address, click the Apply button. The client launcher will attempt to connect to the Gateway that you selected.
After you have selected a Gateway, the client launcher will attempt to contact the Gateway and will update the Status field at the top of the screen. If there was an error while attempting to contact the Gateway, you can hold your mouse over the Status field to see what the error was. You can also check <user home folder>/.ignition/clientlauncher-data/clientlauncher.log for error information. Keep in mind that you cannot use a client launcher to connect to older Gateways. The minimum Gateway versions that can be used by client launchers are 7.5.11 for the 7.5 Ignition platform and 7.6.4 for the 7.6 Ignition platform. Any 7.7 or later Ignition platform can be used with the client launchers.
To use the Native Client Launchers
- Go to the Home page on the Gateway.
- Scroll to the bottom of the page to see the Native Client Launchers section.
Click on the Download button to download the native launcher that you need for your operating system.
• For Windows, you will see a clientlauncher.exe file.
• For Linux, open the downloaded .tar.gz file using an archive manager, or use tar -xvf on the command line. You will see a clientlauncer.sh file.
• For Mac OS X, double-click the clientlauncher.dmg file, drag the Client Launcher .app into the Applications folder.
- Click on the .exe, .sh, or .app file (depending on your OS) to open the page that shows URL for available Gateways.
Choose the Gateway you want, click the SELECT Gateway button, and click Save & Close.
On the window that is displayed you can launch your project.
If your Gateways have multicast enabled (Multicast Enable check box is selected on the Gateway Settings page), and multicast transmission is allowed on your network, you can see a list of Gateways under the Available Gateways tab.
Select a Gateway from the list and click the SELECT Gateway button.
The Client launcher will attempt to connect to the Gateway you selected.
If you don't see your Gateway, you can manually enter the Gateway address under the Manually Input Gateway tab, the format is host:port.
For example, you can input
localhost:8088to connect to a Gateway running on your local machine. After you have entered your address, click Apply.
The Client launcher will attempt to connect to the Gateway you selected.
After you have selected a Gateway, the Client launcher will attempt to contact the Gateway and will update the Status field at the top of the screen. If there was an error while attempting to contact the Gateway, you can hold your mouse over the Status field to see what the error was. You can also check
<user home folder>/.ignition/Clientlauncher-data/Clientlauncher.logfor error information.
Keep in mind that you cannot use a Client launcher to connect to older Gateways. The minimum Gateway versions that can be used by Client launchers are 7.5.11 for the 7.5 Ignition platform and 7.6.4 for the 7.6 Ignition platform.
You can hide the Native Client Launcher section on the Gateway Home page by disabling it in the Gateway Settings > Homepage Config tab.
Managing Multiple Gateways
It is possible to configure the client launcher to always start on the Gateway Configuration screen. This allows you to connect to any number of Gateways using the same launcher. To enable this configuration, open the launch.xml file (details on this file are in the Custom Launch Settings section below). Set the initconnect property to false and save the file.
If you are managing multiple Gateways, it may be helpful to mark some Gateways as favorites. These Gateways are always listed first when accessing the Gateway Configuration screen. You can also filter out non-favorite Gateways by checking the Favorites Only checkbox on the Gateway Configuration screen. By setting the initconnect property to false (as documented above in the Managing Multiple Gateways section), you can force the client launcher to always display your favorite Gateways list any time you start the launcher.
After the Gateway has been configured, you can launch a client project or the Designer from the Projects screen. After a project has been launched, a desktop shortcut is created. You can use the desktop shortcut to directly launch the project from the client launcher without needing to select the project again from the Projects screen. A client project will not be visible for launch unless all the conditions below are satisfied:
- The project has at least one main window
- The project is not disabled in the Gateway
- The project is not hidden from launch via the project properties
- The project's configured window launch mode matches the client launcher window mode. For example, if a project's default launch mode is Windowed mode and the "Full Screen" button is not enabled in the project's properties, this means that the project cannot be launched when the client launcher is running in fullscreen mode.
If a project is no longer available in the Gateway, launching the desktop shortcut for the old project will cause the client launcher to display the Projects screen along with an error message at the top of the screen.
The client launcher is typically used to open different projects residing on a single configured Gateway. However, you can also create temporary connections to other Gateways by checking the "Temporary Connection" checkbox on the Gateway Configuration screen. This prevents the selected Gateway from being saved in launch.xml, which may be helpful if you have already configured a default Gateway and you do not want to lose its connection settings. After the connection has been established and saved, the Projects screen will be shown for the temporary Gateway. You can then launch a project or the Designer as you normally would. If the "Create desktop icon" checkbox is checked for the launched project, the temporary Gateway network address is saved in the desktop shortcut.
The client launcher can take advantage of a redundant Gateway setup. Whenever a connection is established with a master Gateway, the backup Gateway IP address is automatically stored in the client launcher configuration file. If the master Gateway cannot be contacted the next time the client launcher is run, an attempt is made to contact the backup Gateway. If the backup cannot be contacted, the client launcher switches between contacting the primary Gateway and the backup Gateway until one responds or the user closes the launcher.
Custom Launch Settings
Client launcher configuration settings, log files and temp files are stored by default in <user home folder>/.ignition/clientlauncher-data/. The following settings can be configured in launch.xml:
The settings below can also be passed to a client launcher executable as startup parameters. Note that many of the settings overlap with the custom launch settings above, and if present, they will override the settings in launch.xml.
Client Startup Examples
For another example of automatically launching clients with the Native Client Launcher, please see the following Knowledge Base Article: Launch Project to Multiple Monitors
Setting client tags
Client tag values in Ignition clients can be set by the client launcher upon startup. There are two ways you can do this. The first way is to add the tag info to the other-args section in launch.xml, as shown below. These settings would take effect for all clients started from the client launcher. The examples below assume that you have two client tags in the root folder of your project, called "LaunchTag" and "LaunchTag2".
Client tags that are set by the client launcher cannot contain spaces in the tag names!
The other way is run the client launcher from a command line or a desktop shortcut and add these lines to the end of the command:
Starting the client launcher from a command line in this case would look like the example below (Linux example shown)
The client launcher can be pre-configured locally and then deployed to remote client machines via a zip file. Using this capability allows a client launcher to immediately connect to a Gateway on the very first launch.
- First, you need to configure a client launcher on a local machine to point to a Gateway.
- Next, copy the <user home folder>/.ignition/clientlauncher-data folder next to the launcher executable.
- Zip everything together and distribute the zip to other machines.
- For Window and Linux machines, the launcher can use the clientlauncher-data/ folder that was placed next to the executable. For OSX machines, you need to copy the clientlauncher-data/ folder to the user's home directory and place the Client Launcher. app wherever convenient.