After installing with the Installer, Ignition will have a service representing it on the operating system. By default Ignition will start when the system starts, but you can manually start and stop the system with the following terminal commands:
The examples below assume "Ignition" is the service named used during installation (which also happens to be the default service name). You may need to modify the examples below using your system's service name.
net start Ignition net stop Ignition
/usr/local/ignition/ignition.sh start /usr/local/ignition/ignition.sh stop /usr/local/ignition/ignition.sh restart
The examples below use the default installation directory
/usr/local/bin/ignition/ignition.sh start /usr/local/bin/ignition/ignition.sh stop /usr/local/bin/ignition/ignition.sh restart
Upgrading Ignition is as easy as running the installer. When you run the installer from the same directory as a previous install, our installers are able to detect that Ignition is already installed. If Ignition is already installed, the installer will ask if you would like to proceed with the upgrade. A wizard takes you through the upgrade in a similar workflow as installation workflow.
As of 8.0.14, Ignition installers can be used to upgrade any edition of Ignition (i.e., Edge, Maker, or Standard) with the exception of ARM as that will require a zip installer for upgrading.
Older versions of the Linux installer would place files across multiple different directories. Running an 8.0.14+ installer will move all those files to the specified installation directory.
During the upgrade process, the Gateway will have to restart, so make sure to account for downtime when upgrading.
When you upgrade Ignition, you'll also be given the option to update any additional modules you currently have installed, including Third-Party modules. On the Select Modules screen, there is a tab for the modules included in your version of Ignition, and a tab for Additional Modules you may be using. Under the Action column, you can choose to upgrade or remove the module or leave it unchanged.
If you are updating from one major version to the next (i.e, upgrading from version 8.0.# to version 8.1.#) , you will need an updated license. You can do this before upgrading so there is no unlicensed time after the upgrade.
There are a few extra things to consider when upgrading a redundant pair of Gateways. When performing the upgrade locally, the order of the upgrade technically doesn't matter. However, we recommend upgrading the Master first. This allows the Backup to take over when the Master is down for an upgrade, and the Master can resume operations when it comes back online. At this point the Backup can be upgraded without interruption. The same considerations mentioned above should also be applied to the redundant pair, but you only need a Gateway Backup file from the Master Ignition Gateway.
If the upgrade will be performed remotely using the Enterprise Administration Module, then the Backup Gateway should be upgraded first. This allows the EAM controller to manually tell clients/sessions to communicate with the newly upgraded Backup Gateway, even though the Master will be a different version, allowing time to upgrade the Master.
To reset the main password for the user with full privileges, use the Gateway Command-line Utility (gwcmd) utility. The 'gwcmd' utility triggers system commissioning, and prompts the user to reset the username and password for the main user (with full privileges) after the Gateway restarts. Linux and Mac OS platforms also use the 'gwcmd' utility for password reset. For more information, see the Gateway Command-line Utility page.
Uninstalling Ignition will remove any projects or Gateway level configurations you made. If you wish to preserve anything, make sure to take a Gateway backup first.
To uninstall Ignition, run the uninstaller file. This file can be found in the main Ignition installation directory, for example:
C:\Program Files\Inductive Automation\Ignition\Uninstall.exe