The Sets tab contains a list of IBM Cloud Sets. Each set represents a grouping of IBM Cloud MQTT endpoints. When a set is referenced by a Tag Agent the Agent will push Tag data to all IBM Cloud MQTT endpoints contained within that Set. The Sets are disjoint, meaning that a single IBM Cloud MQTT endpoint cannot be in more than one set. Out of the box the IBM Cloud Injector module will have one "Default" set defined.
Additional Sets can be configured for situations where multiple Tag Agents will need to push to different IBM Cloud MQTT endpoints. The configuration options for Sets are listed below.
- This is the friendly name of the set used to easily identify it.
- This is a friendly description of the set.
- Push Policy
- This defines which endpoints to push to. If PUSH_TO_ALL is selected, every endpoint that is part of this set will receive all messages. If PUSH_TO_ANY is selected, only one of the endpoints that is part of this set will receive any given message. PUSH_TO_ANY is useful when adding endpoint configurations to increase the throughput of the Injector.
Clicking on the 'Create new IBM Cloud Set...' link will bring up the following form to add a new Set.
Tag Agents are the workers within IBM Cloud Injector that monitor tag events, convert them to a JSON representation, and push them to one or more IBM Cloud MQTT endpoints. Out of the box the IBM Cloud Injector module will have one "default" Tag Agent defined.