What is Web-launching
Web-launching is the mechanism by which Clients and and the Designers are opened on a computer. They are launched from the Ignition Gateway, you download and run them without requiring any installation steps.
How Web-Launching Works
Web-launching relies on Java Web Start technology. When the user clicks on a project or the Designer link in the Ignition Gateway (or embedded in a separate website), they download a small JNLP file that describes the application. When this file is opened (usually automatically), Java is invoked on the user's machine and directed to the remote application. The application is downloaded and cached, and then executed.
The running application (an Ignition Client or the Designer) communicates with the Gateway via HTTP. It is cached for increased subsequent launch speed, and can optionally install a link in the Start menu and on the desktop for easy access. By default a shortcut is created for you but this setting can be changed in the Java Control Panel.
Troubleshooting Web-launch Problems
There are a few common problems that can cause difficulties with web-launching. Fortunately, they are often easy to fix.
No Java Installed
Before you successfully web-launch the Designer, make sure you have Java 8 installed, see http://www.java.com.
If you're on the computer that's running the Ignition Gateway, you already have Java installed, the Ignition installer makes sure of that. If you're on a computer that is accessing the Gateway over the network, the Java Detection panel on the bottom of the Gateway's Home page detects whether or not Java is installed
No Network Connection
Web-launched clients depend on network connectivity to connect to the server. If the network is unavailable, the client cannot be launched. This is often a problem with clients and the Designers launched directly from desktop/start menu links.
Cached References to Modified Servers
The cached projects/launch shortcuts contain the address of the Gateway machine. If the server is relocated, these links will no longer work. They can be updated by re-launching from the Gateway.
Still having problems?
You can also see Native Client Launchers.