Belden Horizon Data Manager FAQs
Belden Horizon Data Manager is the management suite for Belden Horizon Data Operations.
These attributes are sent by the devices. There is a special OMA object designated for this purpose. Also, a user can update them in the Device Details form.
- Try double checking your connection parameters.
- If the parameters are correct, check your firewall settings.
Data sent to Belden Horizon Data Manager must be in a special format, as shown in the JSON schema in the Project settings page. If Belden Horizon Data Manager cannot parse incoming messages, the messages only appear in the Raw tab.
Belden Horizon Data Manager supports two protocols to remotely manage a device: LWM2M and MQTT.
LWM2M
A Belden Horizon Data Manager specification that enables device management. The Explore tab for LWM2M devices supports WRITE/EXEC operations, so Belden Horizon Data Manager can directly manage LWM2M devices.
MQTT
Belden Horizon Data Manager supports 3 types of MQTT topics:
- request - to send manage requests to a device
- response - to receive responses from a device
- data - to receive data from a device
Request/response formats are not defined.
For example: If you can program your device to reboot when it receives {"command": "reboot"} from the request topic, you can reboot your device remotely.
If you open the MQTT tab on the Device Details form, you can see Request/Response tabs to manage MQTT devices online.
To accomplish management tasks, you must program your device.
The Batch Device Management feature offers operations similar to those described above, but you can define batch commands (MQTT or LWM2M) and schedule these commands to execute against a group of devices.
You can remove a project from the Project List or from the Remove Project section in the Project Settings > Settings tab.
Use Belden Horizon Data Operations. All data that appears in the Explore tab is available in Belden Horizon Data Operations as well
- We do security testing with every release.
- We prevent security issues through LWM2M, REST, and MQTT protocols. They only use secure transports, such as TLS and DTLS. We do not support unencrypted transports between the two products.
- All security credentials established during cloud activation are securely stores on the Belden Horizon Data Operations device and they are not exposed to the end user. It is impossible to alter these credentials after activation as long as physical security of the Belden Horizon Data Operations gateway is maintained.
- Alert - The Belden Horizon Data Manager Alerts feature allows a user to define notifications based on rules. Rules comprise a set of conditions that define an abnormal state of a device. For example: No data received from a device in more than two minutes, or the temperature went below 30 degrees. First, define Actions. Actions are the types of notifications, such as Slack or Webhook. Then, create a Trigger. A trigger is a combination of device tags, a set of rules, and an action. Once triggered, Belden Horizon Data Manager sends the alert notification to the defined destination. Alert notifications can be viewed on the Belden Horizon Data Operations Manager dashboard as well as from email and third-party web applications, such as Slack. The Incidents tab on the projects page lists the alerts that were generated.
- Event - Events list the Belden Horizon Data Manager configuration activities that occurred for a project within a company. For example: Added a new project, or deployed a new device.
- Incident - If a device reaches an abnormal state according to the rules, then Belden Horizon Data Manager will create a new incident and send notifications. The Incidents tab lists the alerts that were generated. When a device returns to a normal state, the open incident will be closed and Belden Horizon Data Manager will send another notification with an incident resolved message.
As many as you want, purchased or installed on the Site.
We strongly recommend ESXi version 6.7 or higher.
Find out the following:
- The version of the Belden Horizon Data Operations and the Belden Horizon Data Manager.
- The version of a component if it is not working.
- The type of license installed.
- If the network is properly configured.
- If the NTP/DNS settings are correct.
- If you are using the correct PLC driver and IP address.
Alert history is not deleted. It is kept as long as there is space in the database.
After the alert history database becomes full, the system stops accepting data. In upcoming releases, we will develop a more sophisticated data life cycle management.
Not at this time. In upcoming releases, Belden Horizon Data Manager will be able to deploy LDAP/AD settings for various Belden Horizon Data Operations devices.
Currently, a template consists of: PLC configurations (device settings and tags) and Flows.
You can select a mix of both types and create as many templates as you want.
These templates can then be uploaded from the Belden Horizon Data Manager Admin Console so that they are available to all the companies, or from the Belden Horizon Data Manager at a Company level so that they are available to all the Projects.
You can create different groups of Belden Horizon Data Operations devices and select which template you want to deploy to a selected group of devices.
In upcoming releases, we will include CC as well as a few other configurations.
- Belden Horizon Data Manager supports the MySQL protocol for ClickHouse. If the BI tool supports MySQL, it can connect to ClickHouse. Some smart BI tools may use MySQL system tables that are not present in ClickHouse, so they should be tested.
- Belden Horizon Data Manager allows you to connect to the ClickHouse underlying database. See https://clickhouse.tech/docs/en/interfaces/third-party/integrations/ to find the native connectors that ClickHouse uses.
When an activation fails, there will be an Activation Stage Message that reports the exact cause(s). Here are some potential fixes:
- Ensure port 443 is opened.
- Ensure 51820/UDP is open for the Belden Horizon Data Operations instance.
- Ensure the Remote Access protocol is not blocked at all.
- Ensure the time synchronizations setting between the Belden Horizon Data Manager and Belden Horizon Data Operations is working properly.
- For Docker-run Belden Horizon Data Operations instances, check for NETADM capability.
- For <3.2.0 Belden Horizon Data Operations instances, ensure Remote Access modules on each host system (where the LE is installed) are operating properly.