Overview

Publishers can be considered the opposite of data sources. Instead of gathering data into the system, publishers distribute data out. This can be useful when using Mango to gather information from disparate systems in order to modify, cleanse, or otherwise manage it, and then send it in a common format to other systems. In this way, Mango is not only M2M, but M2M2M. Publishers can even be used to send data to other Mango instances, perhaps consolidating data among various field instances into head-office management data. Indeed, instance of Mango can use publishers to control each other in many ways.

Common publisher configuration

Every publisher has a Name which is used to visually identify it in lists. It is recommended that each publisher have a unique name, but is not required. The Enabled checkbox is used to enable or disabled the publisher.

Publishers use caches to ensure that every point update is delivered to its destination. If the destination for whatever reason does not accept these deliveries for an extended period of time, this cache can become very large. Undelivered point updates are never purged from the cache (except upon the disabling of the publisher), but a Cache warning size can be defined which causes an alarm to be raised whenever this size is exceeded. This alarm returns to normal when the cache size no longer exceeds the warning size, or when the publisher is disabled.

The Update event value determines whether all point updates are delivered, or only point changes.