Realtime Tags providers are configured in the Gateway's Config section under Tags > Realtime. After installation, the Ignition Gateway will start with an internal provider defined. You can edit its name and settings by selecting edit to the right of its entry in the table, or create new providers by selecting Create new Realtime Tag Provider below the table.
There are two types of Realtime Tag Providers that you can choose from:
Tags are stored inside of Ignition and executed by the system.
|Name||The name of the provider.|
|Description||The description of the provider.|
|Enabled||If true, tag provider is enabled. Default is true.|
|Default Database||The default database connection to use for expression tags that run SQL queries. All query tags with default database providers selected with run their queries against this database source.|
Tag Editing Permissions
Tag Provider from one Gateway is brought in to another Gateway.
|The name of the provider.|
|Description||The description of the provider|
|Gateway||The name of the Gateway on the Gateway Network that this provider is coming from.|
|Provider||The name of the provider as it is on the remote Gateway. This does not have to be the same as its name on the new Gateway.|
|History Access Mode||This setting dictates how tag history is queried for remote tags. Gateway Network will go through the Gateway Network to query history. Database will query the database directly.|
|History Datasource||The datasource to query when History Access Mode is set to Database.|
If querying the database directly, this is the gateway name of the remote system. It is used to identify data from that system in the database.
|History Provider||If querying the database directly, this is the name of the tag provider on the remote system. It is used along with driver name to identify the correct tags in the database.|
|Alarms Enabled||If true, alarms configured on the remote gateway will be enabled on the new Gateway.|
|Alarm Mode||How alarm state should be monitored. In 'queried', state will be queried through the Gateway network when necessary. In 'subscribed', the state will be subscribed, and updates will be sent asynchronously. Subscribed provides better performance, but uses more memory.|