Connectivity setup guide

Use this guide to determine the best way to connect your data sources to Heisenware. Follow the questions below and click the links to navigate to the exact setup that fits your use case.

Do you need to connect an external data source?

• No, I am building an independent application that relies solely on the built-in databases and doesn't need external connectivity. You can skip this guide and start directly with the Overview.

• Yes, my use case requires reading or writing data to an existing database, machine, IT system, scanner, API, or industrial protocol. Continue with platform hosting.

How is your Heisenware tenant hosted?

The way you connect to external systems depends on where your Heisenware platform runs.

• Managed Cloud (SaaS)

• Self-hosted (on-premise or private cloud)

Managed Cloud Connectivity

Your tenant is hosted by Heisenware in the cloud. Is your data source accessible via the public internet, e.g., via API?

• Yes, the data source is reachable via the internet. You can use our standard connectors and don't need anything extra.

• No, the data source is in an isolated or local network. Continue with connecting isolated data sources.

Self-Hosted Connectivity

Your tenant is hosted on-premise or in your private cloud. Is your data source accessible from the network where the platform is deployed?

• Yes, the data source is in the same network. You can use our standard connectors and don't need anything extra.

• No, the data source is in an isolated network segment. Continue with connecting isolated data sources.

Connecting isolated data sources

Does Heisenware offer a standard connector for your specific data source?

• Yes, a standard connector exists. Continue with choosing your agent setup.

• No, I need to connect a custom source. As an advanced user, you can use our code adapter or build a custom extension. These features allow you to wrap custom code and expose it as visual function blocks to the platform. Alternatively, please contact our support team to discuss your specific requirements.

Choose your edge agent setup

To access isolated networks, you need to deploy an agent. The agent is a secure tunnel that maps data and enables remote logic configuration. It runs locally to bridge isolated networks and buffers data via MQTTS.

What infrastructure is available in your local network?

• Native Windows or Linux OS

• Docker runtime

• LXC runtime

Native agent

You can use the native binary. It runs as a highly efficient system service directly on your OS without requiring Docker. Continue to the native agent setup documentation for the next steps.

Docker agent

You can deploy the Docker container. This is the recommended approach for containerized environments on OT servers or edge devices. Continue to the Docker agent setup documentation for the next steps.

LXC agent

You can deploy the LXC agent. This setup is suitable for specific edge devices running LXC runtimes, such as INSYS routers. Continue to the LXC agent setup documentation for the next steps.