Data Stream Designer – What is a Remote Agent?

How Can We Help?

Data Stream Designer – What is a Remote Agent?

< Back

When designing a Data Stream, you may decide to run some of the stream’s logic on one host or set of Stream Hosts, and some on another. For instance, if there is a need to monitor sensor readings and escalate any anomalies, it may be desirable to filter out the important data close to the source to avoid constant unnecessary data transfer.

 

In such cases, the boundaries between the Stream Hosts must be bridged to allow data to flow between them. “Remote” agents are the mechanism that the Data Stream Designer uses for this task.

Every Category of Stream Hosts can nominate one “Remote Publisher” and one “Remote Receiver.” This will be inserted into a stream at every point a Stream Object assigned to that Category receives data from a Stream at every point a Stream Object assigned to that Category receives data from a Stream Object in another category.  Remote Agents do not need to be configured on all Categories; only on those that expect to receive data from another host.

Remote Agents must be configured using the Category blade and should be paired in such a way that the Category’s Receiver will be able to receive the data from its own Publisher. For instance, if you decided to use the MQTT Listener as the Receiver, you should always use an MQTT Action Agent as the Publisher and configure both with the same server details. If you do not, any data sent by the Publisher would not be received and the data stream would be broken.

To better understand the process, as well as potential pitfalls, it may help to visualize the process as two separate streams, separated along the boundary. The Data Stream Designer will insert the configured Publisher into the stream to run on the “sending” host, like so:

and will similarly insert the configured Receiver into the stream to run on the “receiving” host:

 

Comments are closed.

This is the legacy version of the XMPro Documentation site. For the latest XMPro documentation, please visit documentation.xmpro.com

X