Connectors
Connectors are functions that handle translation between Heisenware and external systems. They let flows communicate natively with third-party systems, industrial protocols, and external databases.
Connection scenarios
The network location of the target system determines where a connector executes.
Direct connection
When the platform can reach the target system directly, execute the connector in the application backend. The platform automatically manages the connection and execution. This scenario applies to:
The Heisenware Cloud reaching systems on the public internet, such as a cloud API, a web service, or a public MQTT broker.
An on-premise installation reaching systems within the same network.
Local connection (via Agent)
If the target system resides in an isolated network segment without inbound access (such as a PLC in a machine network), deploy an Agent. Agents are available as a Native Agent or a Docker Agent.
Build
Compile a Native Agent directly inside the App Builder and select which connectors to include in the package.
Use
Once the Agent comes online, it appears automatically in the Function Explorer. The Agent displays the connectors selected during the build. These functions execute directly at the edge, next to local devices.
For a deep dive into the build process and deployment options, see the Agents article.
Instance creation
Most connectors require an instance configuration before they can interact with a target system. Create an instance using the create function. The instance preserves configuration schemas, tracks credentials, and manages the connection lifecycle.
Certain connectors provide purely static utilities (such as File I/O or the Operating System (OS)) and execute calls immediately without an instance configuration.
Available connectors
The following table lists the available connectors and their required configuration types. Each link leads to a detailed configuration guide.
Connects directly to Allen-Bradley PLCs for machine data acquisition and control.
Instance creation required
Counts digital pulses on Raspberry Pi GPIO pins, with automatic run/stop detection.
Instance creation required
Connects to Heidenhain DNC systems and requires a local connection scenario.
Instance creation required
Connects to Heidenhain controllers using the OPC UA protocol.
Instance creation required
Makes requests to standard web APIs and HTTP endpoints.
Mixed (Static and instance options)
Integrates natively with the Manufacturing Integration Platform (MIP).
Instance creation required
Connects to an OPC UA server for industrial automation data exchange.
Instance creation required
Deploys an OPC UA server to expose data from the application.
Instance creation required
Accesses statistics and information from the host operating system.
Static functions only
Integrates natively with SAP Digital Manufacturing.
Instance creation required
Connects directly to Siemens S7 PLCs for data acquisition and control.
Instance creation required
Last updated
Was this helpful?