You're currently browsing the Ignition 7.8 docs. Click here to view the latest docs.

 

 

Before you install Ignition, make sure you meet the minimum system requirements:
  • Java 8+ (server), Java 6+ (client)
  • Dual-Core Processor (32 or 64 bit)
  • 4GB RAM
  • 10GB free HD space

Also, it is assumed that you are familiar with operating a shell, and you have root or superuser privileges to run the Ignition installer.

To download and install Ignition on Linux

  1. Go to the Inductive Automation website at
    www.inductiveautomation.com
     
  2. Select Download > Current Release.
     
  3. On the Ignition Downloads page, scroll down to System Installers and select the
    ignition-X.X.X-linux-x64-installer.run installer. 
    If your computer runs on a 32- bit Linux, select the ignition-X.X.Xlinux-32-installer.run.



    Note: If you choose the wrong installer, an Error window is displayed letting you know the correct installer to use for your machine.
    The installers can run in both graphical or command-line mode, allowing Ignition to install on a headless Linux server. The installer will install files in the following locations:

    /usr/local/bin/ignition
    (unless a different installation directory was used) – contains binaries, startup scripts and the uninstall executable

    /var/lib/ignition/data
    contains application-generated files, temporary files and the internal database

    /var/lib/ignition/user-lib
    contains modules and JDBC jars

    /var/log/ignition
    contains the wrapper.log and other log files

    /etc/ignition
    contains configuration files. Symbolic links to these files are created in

    /var/lib/ignition/data
     
  4. You must run all the commands as root. Prefix everything with sudo or first run
    sudo su
     
  5. If Java 8 is not already installed, run the following commands to install it: 
    sudo add-apt-repository ppa:webupd8team/java
    sudo apt-get update
    sudo apt-get install oracle-java8-installer

  6. Open a command shell and navigate to the installer executable, by running the following command from the command line:
    sudo chmod +x ignition-x.x.x-linux-xxxinstaller.run

  7. Start the installer executable.
    The installer can run in a graphical mode or command line mode.
    If you are running the installer in a shell in a graphical environment, the graphical installer opens automatically.
    If you are running the installer in a headless Linux installation or through an SSH shell, the text installer opens automatically.
    To start the text installer in a graphical environment, run the following command:
    sudo ./ignition-X.X.X-linux-xxx-installer.run -- mode text

    The installer starts running.

  8. Agree to the licensing terms.

  9. Ensure the installation directory is the default directory at:
    /user/local/bin/ignition




  10. Specify the user name under which Ignition is to be installed. For Ubuntu installations, the user that invoked sudo is used by default. For other Linux installations, this field is initially blank.

    The Linux installer requires a user name to set the permissions on the folders created by the installer. This user is then able to start and stop Ignition, run the Gateway Control Utility, and the command line interfaces.

    The binaries in the installation folder are still owned by root and cannot be modified without root access. The selected user must already exist on the system before starting the installer.




    Normally, the installer is capable of auto-detecting a Java 8 installation that has been installed through APT or some other Linux package management tool. In these cases, the installer uses that Java installation and skips this step.

    However, if you have installed Java by extracting the Java binaries to a folder and adding them to the system PATH, the installer is unable to find the Java binaries. You must provide the installer with a full path to the Java executable.

  11. If the Java Installation window is displayed, type the full path to the Java executable.




  12. Select either the Typical or the Custom installation mode.

    The Typical mode installs everything that you need to get started.

    The Custom mode lets you add optional modules, such as the OEE Downtime module. It also lets you control and select which modules get installed.




    If you select Custom Mode, the Select Components window is displayed.

    In Graphical mode to view a brief description of the module, click on the module name. Selecting the check box next to a module installs the module as part of the Ignition installation. Clearing the check box next to a module prevents the module from being installed.

    In Text mode a list of all the modules are displayed one at a time. Type y to install the module, and type n to prevent the module from being installed.




    Ignition is now ready to be installed. At this point, you can click the Back button (graphical mode) to change your selections. For the text mode, you can only abort the installation at this point by typing n.

  13. Click Forward (graphical mode) or type y (text mode) to finish the installation.




  14. When the installation is complete, click Finish (graphical mode) or type y to start Ignition (text mode).
    Ignition is started as a background process. 



Once the Ignition Gateway starts up, your web browser opens and brings you to the Gateway home page at 
http://localhost:8088.

On this page ...

IULocgo


Installing Ignition on Linux

 

 

 

 

 

Stop and Start Ignition

After installation, you can start and stop Ignition with the following commands:

/etc/init.d/ignition start
/etc/init.d/ignition stop

 

 

Ignition as a Service

When installing under Ubuntu, Ignition starts automatically whenever the computer reboots. If you wish to stop this behavior, you need to use the update-rc.d tool to remove the service (uninstalling Ignition also removes the service) as follows:

/etc/init.d/ignition stop
update-rc.d -f ignition remove
rm /etc/init.d/ignition

When installing under other Linux distributions, use that distribution's method to automatically start a program after reboot.
For example, this command auto-starts Ignition installed in a Fedora 15 system (run as root user):

chkconfig --level 2345 ignition on

 

 

Set the system PATH

For Ubuntu installations, the installation directory is automatically appended to the system PATH. You can start programs like the Gateway Control Utility from the command line without specifying a complete path to the installation directory.

Note that after installation, you need to close and reopen the command shell for the PATH change to take effect. For other Linux installations, you need to manually add /usr/local/bin/ignition (or your installation directory) to any script that can set the system PATH (such as .profile or .bashrc).

 

 

Automated Installation on Linux

You can automate Ignition installation across different machines using scripts. Ignition is then installed silently from a command shell without showing any user prompts.

Keep in mind that the installer cannot automatically start the Gateway after a silent installation. Use the /etc/init.d/ignition start command as shown in example below.

Command line example

sudo ./ignition-7.x.x-linux-x64-installer.run --mode unattended --prefix /somefolder/bin/ignition --unattendedmodeui none
/etc/init.d/ignition start


Flags

-- mode unattended (ensures that no prompts appear during installation)
-- prefix /somefolder/bin/ignition (optional flag; if a value is set, then Ignition is installed in the specified folder, otherwise Ignition is installed in /usr/local/bin/ignition by default)
-- serviceuser username (allows a Linux system user to be installed (that is, a user that cannot log in to the OS))
-- unattendedmodeui none | minimal (the none flag does not display any sort of graphic during installation; the minimal flag displays a small progress bar and nothing else)

 

Installing using Debian Package Management

By using the package management tools you can quickly install Ignition on Ubuntu and other Debian-based systems. Debian package management is a powerful way to quickly install Linux programs and keep them up-to-date with minimal effort.

Note: that you need to be able to run as sudo to be able to install Ignition. Also, the machine where you want to install Ignition must be connected to the Internet so that the installer and updates can be installed automatically. If you are installing Ignition to a non Internet-connected machine, use the downloadable Linux installers instead (see the Download and Install on Linux section at the Top of this page for more details).

The Ignition Debian installers are dependent on an existing Java 6 or later installation through APT. Java 7 is highly recommended over Java 6. Oracle Java Runtime Environment (JRE) version 7 is officially supported by Inductive Automation, although Ignition runs well in most cases using OpenJDK 7.

The installer installs files in the following locations:

/usr/local/bin/ignition - contains binaries and startup scripts
/var/lib/ignition/data - contains application-generated files, temporary files and the internal
database
/var/lib/ignition/user-lib - contains modules and JDBC jars
/var/log/ignition - contains the wrapper.log and other log files
/etc/ignition - contains configuration files. Symbolic links to these files are created in /var/lib/ignition/data.

When installing Ignition, you can choose whether to use the graphical package management tools, or install completely from the command-line. With either option, Linux automatically downloads the correct 32-bit or 64-bit installer depending on your installed system architecture.

Note that the instructions below are for an Ubuntu Linux system, but other Debian systems will contain the same tools, although they may be under different menus.

Graphical Installation

  1. Download the Inductive Automation public key file from  http://archive.inductiveautomation.com/ia.public.key

    or on the command-line, run
    wget http://archive.inductiveautomation.com/ia.public.key
     
  2. Within Ubuntu, navigate to System > Administration > Synaptic Package Manager.

  3. Within Synaptic Package Manager, navigate to Settings > Repositories.
     
  4. Navigate to the Authentication tab. Click on Import Key File and select the downloaded ia.public.key file.
     
  5. Navigate to the Other Software tab and click on the Add button. Add the following text to the text box:
    dep ://archive.inductiveautomation.com/ignition non-free
     
  6. If you want to add the Ignition beta repository, click the Add button again and add this text to the text box:
    dep http://archive.inductiveautomation.com/apt ignition-beta non-free

  7. Be sure to uncheck the check boxes next to repositories ending with Source Code, as Ignition does not supply source code with the repositories.
     
  8. Click the Close button. Within Synaptic Package Manager, click the Reload button. You can now type ignition into the Quick Filter box and see the latest available Ignition repositories.
     
  9. Right-click on the Ignition repository that you want to install, and select Mark for Installation. Then click the Apply button at the top. Ignition will be automatically downloaded and started. Navigate to http://localhost:8088 to log into the Ignition Gateway.

 

Command-line Installation

  1. Run
    wget http://archive.inductiveautomation.com/ia.public.key

  2. Run
    sudo apt-key add ia.public.key

  3. Copy
    /etc/apt/sources.list 

    to
    /etc/apt/sources.list.bak

  4. Edit
    /etc/apt/sources.list 

    and add the following lines (the ignition-beta line is optional):
    deb http://archive.inductiveautomation.com/apt ignition non-free
    deb http://archive.inductiveautomation.com/apt ignition-beta non-free

  5. Run 

    $sudo apt-get update

    to update the download list within the APT utility.

  6. Run
    sudo apt-get install ignition 

    to install the latest stable Ignition version or run 

    sudo apt-get install ignition-beta 

    to install the latest beta Ignition version.

    If you want to run the Gateway Command Utility or gwcmd right after installation, open a command shell in your home folder and run
    source .profile

    This forces your command shell to reload the .profile script, which has been updated with a path to the Ignition executable during installation.

Upgrades

During an upgrade, the Ignition internal database, configuration files, and any custom installed modules are not changed. Whenever a new version of Ignition is released, the online Debian repositories also get updated with the latest version.

Your Linux environment will list Ignition in the list of package upgrades when a new version is available. As with the installation, you can choose whether to upgrade using a graphical environment or using the command-line.

Graphical Upgrade

Ignition will appear as an entry under your system's Update Manager under the Other Updates section. If you choose to install updates using the Update Manager, Ignition will be upgraded at the same time as other packages.

You can also manually upgrade Ignition using Synaptic Package Manager. Locate ignition or ignition-beta in the list using the Quick Filter.

Ignition can also be found in the World Wide Web section. Right-click and select Mark for Upgrade. Then click Apply at the top. The latest version of Ignition will be downloaded and installed.

Command-line Upgrade

To upgrade all installed packages, including Ignition, run
sudo apt-get upgrade

To only upgrade Ignition, run
sudo apt-get install ignition

or
sudo apt-get install ignitionbeta

The APT utility recognizes that Ignition is already installed, and performs the upgrade.

 

 

Uninstalling Ignition on Linux

Before you uninstall Ignition...

Be sure to back up your Gateway and unactivate your Gateway license.

During a new Ignition installation, an uninstaller executable is created.

When Ignition is uninstalled, the settings database and folder in /data is backed up to /data_<current date>, and modules and user-supplied JDBC jars in /user-lib are backed up to /user-lib_<current date>. Also, the Ignition service is removed from Ubuntu Linux installations automatically. 

Linux – Using Downloaded Installer

Ignition 7.3 or later installations on Linux contain an uninstaller executable.

To run the uninstaller,

  1. Open a command shell and navigate to /user/local/bin/ignition (or your installation folder).
     
  2. As root or sudo, run
    ./uninstall

Linux Ignition installations before 7.3 used a zip file that did not form an installation. Since these installations were never created with an installer executable, no uninstaller executable was ever generated. This is true even if using a 7.3 or later installer executable to upgrade an installation from before 7.3. For installations before 7.3, you must manually remove the Ignition folders using the commands below.

/etc/init.d/ignition stop
*Ubuntu only* update-rc.d -f ignition remove 
rm /etc/init.d/ignition 
rm -rf /usr/local/bin/ignition 
*Recommended* mv /var/lib/ignition/data /var/lib/ignition/data_<current date> 
*Recommended* mv /var/lib/ignition/user-lib /var/lib/ignition/user_lib_<current date> 
*Recommended* mv /etc/ignition /etc/ignition_<current date> 
rm -rf /var/log/ignition

Linux Uninstallation – Using Ubuntu Package Management

Installation using the Ubuntu Package Manager offers the choice to either remove the installation while keeping the configuration files in /etc, or to completely remove/purge the installation from the system.

If you choose to remove the installation and then reinstall Ignition, Ubuntu will need to download Ignition again.

To simply remove the installation,

  1. Open a command shell.
  2. Run 
    sudo apt-get remove ignition (for stable installations) or 
    sudo apt-get remove ignition-beta (for beta installations)

To completely remove/purge the installation,

  1. Open a command shell.
  2. Run
    sudo apt-get purge ignition (for stable installations) or 
    sudo apt-get purge ignition-beta (for beta installations)

 

 

 

 

 

 

  • No labels

2 Comments

  1. Anonymous

    wget http://archive.inductiveautomation.com/ia.publich.key should be changed to wget http://archive.inductiveautomation.com/ia.public.key under command-line installation

    1. Thank you for pointing this out! We've corrected the typo.