- INDUCTIVE AUTOMATION IGNITION DATA HIGHWAY LICENSE KEY
- INDUCTIVE AUTOMATION IGNITION DATA HIGHWAY INSTALL
- INDUCTIVE AUTOMATION IGNITION DATA HIGHWAY PASSWORD
Interval (seconds) to send statistics to the EAM Controller (defaults to 5 when not specified)įilesystem path to store EAM Archives (gateway backups, etc) (defaults to data/eam_archive when not specified) Gateway Name (not hostname) of EAM Controller to bind to Set Agent or Controller to define the EAM target config (defaults to Agent when not specified)
Timeout (ms) for web socket # (defaults to 10000 when not specified) Set true or false to mark connection # enabled or disabled Number of missed pings allowed for connection # (defaults to 30 when not specified)
Ping Rate (ms) for connection # (defaults to 1000 when not specified) Port Number to use for connection n (defaults to 8060 when not specified) Hostname (or IP) for Outgoing GAN Connection Definition for #. See List of tzdata Entries for complete selection. Set to a valid TZ database name, like America/Los_Angeles. Maker Edition), used to set value for initial gateway auto-commissioning
INDUCTIVE AUTOMATION IGNITION DATA HIGHWAY LICENSE KEY
Set to standard, edge , or maker , used to set value for initial gateway auto-commissioning.Ĩ-digit license key ( XXXX-XXXX) for leased activation (e.g.
INDUCTIVE AUTOMATION IGNITION DATA HIGHWAY PASSWORD
Password value or salted hash to be used for initial gateway auto-commissioning.ĭefaults to 8088 when not specified, used to override the HTTP port used by the gateway container.ĭefaults to 8043 when not specified, used to override the HTTPS port used by the gateway container.ĭefaults to 8060 when not specified, used to override the Gateway Network port used by the gateway container. Set to true to have the restored gwbk disabled on startup.ĭefaults to admin when not specified, used to set value for initial gateway auto-commissioning. Set to Y to accept the Ignition EULA automatically (see Licensing section below). This is useful for secrets management systems where you want to keep the values out of the process environment (which might be able to be inspected by individuals with access to docker inspect, for example). Specifying any of the environment variables below with a _FILE suffix will direct the system to take that environment variable value as a path to a file containing the value of interest. The available environment variables can either accept explicit values or load the target values from a file. This section will detail the available configuration options and how best to use them. Various aspects of the Ignition Gateway can be configured through the use of either command-line arguments to the container, or environment variables. Guidance for the installation and configuration of Docker (on all platforms) are available here: Get Docker Configuration
INDUCTIVE AUTOMATION IGNITION DATA HIGHWAY INSTALL
If you are running Linux, you'll need to download and install the container runtime and tools such as Docker Compose individually. Docker Desktop, available for Windows and macOS, includes both the Docker Engine container runtime as well as container tooling and supporting tools such as Docker Compose. In order to get started with Ignition running as a container, you'll need a container runtime. Our official image is a Linux container, based on Ubuntu Linux. The Ignition Platform offers a container image for use on popular container runtimes such as Docker.