Ignition Default Installation Directories
The default directories for each operating system are listed below.
C:\Program Files\Inductive Automation\Ignition
MacOS and Linux Installation Directory
Mac and Linux installations contain a
ignition.sh file and
ignition-util.sh file, which both contain some configuration parameters for the installation. Modifying these files is not advised, unless directed to by a member of our support team. Instead, an
ignition.shconf file, which is also located in the installation directory, should be used instead.
Additionally, during installation on Mac and Linux, the installer will create a sudoer file at
installationDirectory/etc/ that insures the gateway can be restarted without an interactive login. In most cases, the sudoer file does not need to be modified or maintained. However more information can be found in the
ignition-util.sh file in the installation directory.
Quick Start Configuration
Once the installation process has finished, you'll be redirected to the Gateway Webpage. From there you'll be asked to opt into the Quick Start configuration, which makes several configuration changes to the system. Quick Start can only be enabled upon a new installation.
The following changes are made once Quick Start is enabled:
- Creates an internal SQLite database connection.
- Configures a device connection to a Programmable Device Simulator instance, and adds Tags from the simulator into a Tag provider.
- Configures an internal alarm journal.
- Creates a sample project.
Start or Stop Ignition
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.
Before completing the upgrade process, it is strongly advised to take a gateway backup of your system first.
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.
Sometimes new versions of Ignition will incorporate new JDBC drivers, which are used to connect to SQL databases. When upgrading Ignition, the JDBC drivers will not be upgraded. The reason being, is that you should only need to change the JDBC driver if you upgrade your database. See the JDBC Drivers and Translators page for more details.
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.
Updating License for an Upgrade
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.
- Let us know.
You can reach Inductive Automation by phone at (800) 266-7798.
Some Major upgrades include new modules or have modified the functionality of pre-existing modules. If your license needs to be updated, call us and we can guide you through it. If you are updating from one version to the next, or from 7.0.0 all the way to the latest version, we can talk you though what is different and what new functionality is available. See the New in this Version page for more specifics about what was updated in the various versions.
- Reload your license.
Once your license is updated in our system, go to your Config section of the Gateway webpage, and click System > Licensing. Click on the Update License icon .
For for a detailed guide on reloading a license, see updating a License on this page. If you are coming from an older version, the Gateway may look different. Don't worry, all this functionality is still there, but you may have to un-activate then re-activate instead if the Update License button is missing.
Upgrading a Redundant Pair
There are a few extra things to consider when upgrading a redundant pair of Gateways. When performing the upgrade locally, 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.
Reset the Password
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 - gwcmd 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