Running DataHub on Cumulocity IoT Edge

This section describes how to run Cumulocity IoT DataHub on the Cumulocity IoT Edge, the local version of Cumulocity IoT.

DataHub Edge overview

Documentation overview

The following sections will walk you through all the functionalities of Cumulocity IoT DataHub Edge in detail.

For your convenience, here is an overview of the contents:

Section Content
DataHub Edge overview Get an overview of DataHub Edge
Setting up DataHub Edge Set up DataHub Edge and its components
Working with DataHub Edge Manage offloading pipelines and query the offloaded results
Operating DataHub Edge Run administrative tasks

DataHub Edge at a glance

Cumulocity IoT Edge is an onsite, single-server variant of the Cumulocity IoT Core platform. It is delivered as a software appliance designed to run on industrial PCs or local servers. DataHub is available as an add-on to Cumulocity IoT Edge.

DataHub Edge offers the same functionality as the cloud-variant of DataHub, but stores the data locally. You can define offloading pipelines, which regularly move data from the internal Cumulocity IoT database into a data lake. In an Edge setup, a NAS is used as data lake. Dremio, the internal engine of DataHub, can access the data lake and run analytical queries against its contents, using SQL as the query interface.

Overview of DataHub Edge

DataHub Edge consists of the following building blocks:

DataHub Edge versus DataHub cloud deployments

DataHub Edge uses the same software as DataHub, though in the following aspects these two variants differ:

Area DataHub Edge DataHub
High Availability Depending on the underlying virtualization technology Depending on the cloud deployment setup
Vertical scalability Yes Yes
Horizontal scalability No Yes
Upgrades with no downtime No No
Root access No Yes, if customer is hosting
Installation Offline Online
Dremio cluster setup 1 master, 1 executor Minimum 1 master, 1 executor
Dremio container management Docker daemon Kubernetes
DataHub backend container management Docker daemon Microservice in Cumulocity IoT Core
Data lakes NAS ADLS, Azure Storage, S3, (NAS)

Setting up DataHub Edge


Before setting up DataHub Edge, you have to check the following prerequisites:

Item Details
Cumulocity IoT Edge The local version of Cumulocity IoT is set up on a Virtual Machine (VM). See also section Setting up Cumulocity IoT Edge.
DataHub Edge archive You have downloaded the archive with all installation artifacts from the Software AG Empower portal.
Internet access Internet access is not required.

Hardware requirements

The hardware requirements for running a bare Cumulocity IoT Edge instance are described in section Requirements. When DataHub Edge is additionally running, the hardware requirements of the virtual machine are as follows:

Hardware requirements for the host OS are excluded.

Setting up DataHub Edge

Copy the DataHub Edge archive to the Cumulocity IoT Edge.

scp datahub-<version>.tgz admin@<edge_ip_address>:/tmp

Log in as admin into Cumulocity IoT Edge.

ssh admin@<edge_ip_address>

Run the install script.

sudo /opt/c8y/utilities/ /tmp/datahub-<version>.tar

It takes a few minutes to complete the installation. After completion you can delete the DataHub Edge archive.

The install script runs the following basic steps:

The Docker containers will be restarted automatically if the container itself fails or the applications within are no longer reachable.

The containers are configured to store their application state on the data disk under /opt/mongodb:

Warning: You must not modify the contents of these folders as this may corrupt your installation.

Accessing DataHub Edge

The different DataHub Edge interfaces can be accessed in the same way as in a cloud deployment of DataHub.

Interface Description
DataHub Edge UI The UI can be accessed in the application switcher after you have logged into the Cumulocity IoT Edge UI. Alternatively you can access it directly under http:///apps/datahub-ui or https:///apps/datahub-ui, depending on whether TLS/SSL is used or not. A login is required as well.
Dremio UI On the DataHub Edge home page you will find a link to the Dremio UI. Alternatively you can access it directly under http://datahub. or https://datahub., depending on whether TLS/SSL is used or not. You can log in as admin using password ‘datahub4edge@customer!’.
DataHub JDBC/ODBC You find the connection settings for JDBC/ODBC in the DataHub Edge UI on the Home page.
DataHub REST API The path of the microservice which hosts the API is https:///service/datahub.
Dremio REST API The Dremio URL to run REST API requests against is either http://datahub. or https://datahub., depending on whether TLS/SSL is used or not.

Info: For JDBC/ODBC you have to configure Cumulocity IoT Edge so that port 31010 can be accessed from the host system. For instructions on port forwarding see section “Setting up port forwarding” under Setting up the environment.

Defining DataHub permissions and roles

The definition and assignment of permissions and roles is done in the same way as in a cloud deployment. See section Defining DataHub permissions and roles for details.

Setting up Dremio account and data lake

The setup of the Dremio account and the data lake is done in the same way as in a cloud deployment. See section Setting up Dremio account and data lake for details.

DataHub Edge is configured to use a NAS as data lake. When configuring the NAS use as mount path /datalake. This path is mounted to /opt/mongodb/cdh-master/datalake.

Working with DataHub Edge

DataHub Edge offers the same set of functionality as the cloud variant. See section Working with DataHub for details on configuring and monitoring offloading jobs, querying offloaded Cumulocity IoT data, and refining offloaded Cumulocity IoT data.

Operating DataHub Edge

Similar to the cloud variant, DataHub Edge UI allows you to check system information and view audit logs. See section Operating DataHub for details.

When managing DataHub Edge, the following standard tasks are additionally relevant.

Troubleshooting the system

In problems occur, you should follow these steps:

If you still need to contact Software AG support, include the output of the diagnostics script. See the Diagnostics section for details of how to run it.

Health check

Check DataHub Edge backend status

You can check the status of the backend in the Administration page of the DataHub UI. Alternatively you can query the isalive endpoint, which should produce an output similar to:

curl --user admin:<your_password> https://<edge_domain_name>/service/datahub/isalive

  "timestamp" : 1582204706844,
  "version" : {
    "versionId" : "",
    "build" : "202002200050",
    "scmRevision" : "4ddbb70bf96eb82a2f6c5e3f32c20ff206907f43"

If the backend cannot be reached, you will get an error response.

Check Dremio backend status

You can check the status of Dremio using the server_status endpoint:

curl http://datahub.<edge_domain_name>/apiv2/server_status

Dremio is running if OK is returned. No response will be returned if it is not running or inaccessible.

Log files

Log files are stored at /var/log/cdh.

File Usage
clean_history.log Log file for cleanup of job history
install.log Installation log file

In order to access the logs of the DataHub and Dremio containers, you have to use the Docker logs command. To follow the logs of cdh-master you have to run:

docker logs -f cdh-master

To follow the logs of cdh-executor you have to run:

docker logs -f cdh-executor

The containers are configured to rotate log files with rotation settings of two days and a maximum file size of 10 MB.


Cumulocity IoT Edge uses Monit for management and monitoring of relevant processes. See section Monitoring for details. The DataHub Edge processes, namely the DataHub backend and the Dremio nodes, are also monitored by Monit.

Data disk management and monitoring

The data disk is used for storing the state of DataHub and Dremio and serves as data lake. In order to ensure that the system can work properly, the disk must not run out of space. The main factors for the disk space allocation of DataHub Edge are the Dremio job profiles and the data lake contents.

Cleanup of Dremio job history

Dremio maintains a history of job details and profiles, which can be inspected in Dremio‚Äôs job log, i.e. the “Jobs” page of the Dremio UI. This job history must be cleaned up regularly to free the resources necessary for storing it.

Cleanup is executed by a preconfigured cron job, running the script

/opt/softwareag/cdh-executor/scripts/ <max_job_days>

This uses a Dremio admin command for the actual cleanup, but Dremio must not be running during execution of the admin command. The script will thus stop Dremio, run the Dremio admin command, and restart Dremio, so cleanup execution will cause a short outage of Dremio service. There is one parameter, max_job_days, specifying the number of days of job history to keep. By default, cleanup removes all job history except for the last 7 days, and the cron job is scheduled to run early Sunday morning at 2 a.m.

Job history cleanup can be reconfigured using the script

/opt/softwareag/cdh-executor/scripts/ <max_job_days> <cron_expression>

The arguments are:

Interface Description
max_job_days The number of days to keep job history (default: 7)
cron_expression The cron expression for running the cleanup job (default: ‘0 2 * * 0’, i.e. on Sundays at 2 a.m.)

Be sure to provide a proper cron expression and pass it to the configuration script in single quotes. The configuration can be verified by:

crontab -l

Cleanup of data lake contents

The data lake contents are not automatically purged, as the main purpose of DataHub is to maintain a history of data. However, if disk space is critical and cannot be freed otherwise, parts of the data lake contents need to be deleted.

Browse to the data lake folder /opt/mongodb/cdh-server/datalake. The data within the data lake is organized hierarchically. Delete the temporal folders you deem adequate to be deleted. After that you need to run the following query in Dremio:


Warning: Data being deleted from the data lake cannot be recovered anymore.

Backup and Restore

DataHub’s runtime state as well as the data lake containing offloaded data reside in the Cumulocity IoT Edge server VM. In order to back up and restore DataHub, its runtime state, and its data we recommend you to back up and recover the Cumulocity IoT Edge server VM as described in section Backup and restore.