Page History

The Azure Injector module provides the ability to push Tag data to an Azure IoT Hub.  The settings configuration for this module are located under the Configure tab of the Ignition Gateway web UI.                                                                      

Image Added

Once in the configuration section there are three tabs: Azure IoT Hubs, Sets, and Tag Agents.  Each of these tabs is described in detail in the following sections.

Azure IoT Hubs

The first tab is the list of Azure IoT Hub endpoints that the module should connect to to push tag data.

Image Added

One or more Azure IoT Hub endpoints can be configured on this tab. The configuration options for an Azure IoT Hub connection are listed below.

• Setting Name
  • This is a friendly name of the Azure IoT Hub used to easily identify it (must be unique).
• Connection String
  • This is the Azure IoT Hub connection string used to connect.  This string can be one of the following:
    • An IoT Hub connection string with the following format:
      • HostName=<Host Name>;SharedAccessKeyName=<Key Name>;SharedAccessKey=<SAS Key>
    • An IoT Hub's Event Hub-compatible connection string with the following format:
      • Endpoint=<ENDPOINT>;SharedAccessKeyName=<Key Name>;SharedAccessKey=<KEYVALUE>
    • An IoT Hub device connection string with the following format:
      
      • HostName=<Host Name>;DeviceId=<Device Name>;SharedAccessKey=<Device Key>
• Protocol
  • The protocol to use when connecting to the Azure IoT Hub.  Can be one of the following: 
    • MQTT
    • HTTPS
    • AMQPS
    • AMQPS_WS
• Set
  
  • The Set to associate this Azure IoT Hub connection with.
• Certificates
  • The server certificates to use if required.

Clicking on the "Create new Azure IoT Hub Setting..." link will bring up the following form for adding a new Azure IoT Hub endpoint.

Image Added

Sets

The Sets tab contains a list of Azure Sets.  Each set represents a grouping of Azure IoT Hub endpoints.  When a set is referenced by a Tag Agent the Agent will push Tag data to all Azure IoT Hub endpoints contained within that Set. The Sets are disjoint, meaning that a single Azure IoT Hub endpoint cannot be in more than one set.  Out of the box the Azure Injector module will have one "Default" set defined.

Image Added

Additional Sets can be configured for situations where multiple Tag Agents will need to push to different Azure IoT Hub endpoints. The configuration options for Sets are listed below.

• Name
  • This is the friendly name of the set used to easily identify it.
• Description
  
  • This is a friendly description of the set.

Clicking on the 'Create new Azure Set...' link will bring up the following form to add a new Set.

Image AddedTag Agents

Tag Agents are the workers within Azure Injector that monitor tag events, convert them to a JSON representation, and push them to one or more Azure IoT Hub endpoints. Out of the box the Azure Injector module will have one "default" Tag Agent defined.

Image Added

Tag Agents are configured to point to a single folder.  All Tags within that folder will be monitored by the Tag Agent. 

Each Tag Agent setting has the following fields

• Tag Provider Name
  
  • The name of the Tag provider containing the tags.
• Tag Path
  • An optional folder path under the Tag provider where the root folder of the Tags can be found.
• Tag Pacing Period
  • The buffer period, in milliseconds, that Tag events will be aggregated into a single payload before pushing.
• Set
  • The Set of Azure IoT Hub endpoints that the Tag Agent will push to.
• Convert UDTs
  • Whether to convert UDT members to normal Tags before publishing.  If enabled the Tags representing the UDT member will retain their member path prefixed by the UDT Instance name.

• Group ID
  • An ID representing a logical grouping of MQTT Edge Of Network (EoN) Nodes and Devices into the infrastructure.
• Edge Node ID
  • An ID that uniquely identifies the MQTT Edge Of Network (EoN) Node within the infrastructure.
• Device ID
  • An optional ID that uniquely identifies a Device within the infrastructure.

Note that if a 'Device ID' is not specified, any folder within the folder specified by the Tag Path will be considered a device folder and any Tags within it will be published as device Tags. 

Clicking on the 'Create new Custom Settings..' link will bring up the following form to add a new Server.