The System section is a sort of catch all section that can do a lot of different things. The first window is the Overview page, which is what will first show up when navigating to the Configure tab. The Overview page only has links to other sections of the Config tab, but it is useful if you aren't exactly sure where the setting you are looking for is located, because the Overview page lists the most common configuration changes.
|Backup/Restore||The Backup/Restore page is where you can manually take a backup, and restore a previous backup. It also can upgrade a legacy backup.|
On the Ignition Exchange page you can access the Ignition Exchange to browse for resources. You can also import an Ignition Exchange Package that you've downloaded.
|Licensing||The Licensing page allows you to control any and all licenses currently activated on the Gateway. It will show all the modules that the license is currently good for, and have some options for activating a new or additional license.|
|Modules||The Modules page displays all currently installed modules and if they are active or not. This is where you can install a new module or upgrade an existing module.|
The Projects page can easily manage all of the projects currently configured in the Gateway, with settings that change the Name and Title, or the default database and authentication profile of the project.
The Redundancy page is where all of Ignition's redundancy settings are configured. This is where the master and backup nodes are configured as well as the network settings to make sure the two nodes can properly communicate.
|The Gateway Settings page is where all miscellaneous settings are located. Autobackups can be configured here to happen at certain times. SSL encryption can be turned on here as well as changing roles required to access certain parts of the Gateway for increased security.|
The Networking section deals with setup and management of the Gateway Network.
The Web Server page is for configuring the http and https ports, setting up the SSL / TLS certificate, redirecting traffic through a known address, and whether or not all http traffic should be forcefully redirecting to https. If you are allowing users to access your Gateway from outside your network (through the internet), you will need to configure the Public HTTP Address settings.
You can find out more about SSL in Using SSL.
The Gateway Network allows you to connect multiple Gateways together over a wide area network. The Gateway's connection settings can also be changed to only allow certain connections. The Gateway Settings set the basic rules for the system.
|The Email Settings section allows you to create an SMTP server connection in the Gateway that can be used by several different resources such as Alarm Notification and Report Schedules.|
Ignition provides serveral Security options to safeguard data and applications in Ignition which fall into the following categories, and are set up in the Config section.
Here you can set up an Audit Profile to record details about specific events that occurred.
Users and Roles
This is where you set up users and roles. Security policies are defined in terms of the roles set up in the system.
A security policy can be defined for each Security Zone and is set up in Service Security. The Security Policy has four sections: Alarm Notification, Alarm Status, History Provider Access, and Tag Access. They work together to define how the local Gateway gives access to incoming Gateway connections.
Identify Providers (IdP) provides a way for users to log in to Ignition using credentials stored outside of Ignition. An IdP creates, maintains, and manages identity (login) information while providing authentication services to Ignition. This provides a secure login that allows Ignition to use SSL and two-factor authentication (2FA).
Security Levels define a hierarchy for access inside a Perspective Session. This authorization system provides a way to map roles from an Identity Provider (IdP) to Ignition roles.
|A Security Zone is a list of Gateways, Computers, or IP addresses that are defined and grouped together. This group now becomes a zone on the Gateway Network, which can have additional policies and restrictions placed on it. Security Zones provide this functionality to the Gateway Network, limiting locations instead of people to be read-only for specific actions. This allows for greater control over the type of information that is passing over the network, improving security and helping to keep different areas of the business separate, while still allowing them to interconnect.|
The Databases section is where database connections are set up. Databases are used in historical data logging, reporting, storing alarm logs, and Tag storage.
Many of the advanced features of Ignition, such as the Transaction Groups and Tags Historian require a connection to an external database, and most databases require special permissions for each computer that wants to connect. Ignition takes care of all of this. You create a connection to your database once, and every system in Ignition will use that central connection. From here, you can create new database connections and edit existing connections.
JDBC drivers used in database connections are imported and configured in Drivers of the Database section.
Store and Forward
|The Store-and-Forward system provides a reliable way for Ignition to store data to the database. The Store-and-Forward system settings offer a good deal of flexibility in tuning. Different types of situations and goals will likely require different configurations.|
The Alarming section provides general alarm configuration settings to provide up-to-date status of alarms, store alarm history, build the logic for how, why, and when alarm notifications are delivered, manage alarm notifications for user groups, and send Email, SMS, or Voice notifications. With all these features and functions in Alarming, you can easily create alarms, and design and manage your alarm notifications any way you choose.
This General setting provides of some basic alarm configuration settings.
Alarm Journals are configured in the Alarming section to store basic historical information in a database about alarms that occurred, such as their source and timestamp, associated data on the alarm, and the values of the alarm's properties at the time the event occurred.
The On-Call Roster is where you create user groups to be notified when an alarm occurs. When an alarm is triggered, it is sent to a designated On-Call Roster where it evaluates the users schedules, and only notifies those users that have an active schedule. Users that are off-schedule will not be notified.
|Schedules||Defines the times of users on-call availability and unavailability by configuring Schedules.|
The OPC Client section is where connections from Ignition's internal OPC UA server to other OPC servers are located.
|OPC Connections||Configure OPC Connections to Ignition's built in OPC Server.|
|OPC Quick Client||The OPC Quick Client allows for quick and simple testing of any OPC Connections connected to the OPC server.|
The OPC UA Server is where Ignition's internal OPC UA server is configured.