Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
BaSyx / Documentation / Components / DataBridge
| Overview | Interface | Component | Features |
Contents
Asset Integration made Easy with the DataBridge
The DataBridge supports integrating various protocols with Asset Administration Shells. Data can be acquired from various endpoints, be transformed and pushed into SubmodelElements.
Currently, the DataBridge supports three different types of integration:
- Integration via Cyclic Updates
- Event-triggered Integration
- Integration via Delegation
For all three integration patterns, transformation of data is supported.
Integration via Cyclic Updates
In this integration pattern, the DataBridge periodically queries the data source and pushes it into the AAS Server. Thus, data is automatically kept up-to-date with aconfigurable time interval. If necessary, the retrieved data can be transformed
<<Bild>>
Event-triggered Integration
Similar to the Integration via Cyclic Updates, the DataBridge can transform and push data if an event is received. Currently, it is assumed that the event payload contains the data to-be-integrated.
<<Bild>>
Integration via Delegation
This integration pattern synergizes with the Property Delegation feature of the AAS Server. In contrast to the two integration patterns above, a pull principle is utilized, i.e., the AAS Server pulls the data from the DataBridge on demand. In this integration approach, the DataBridge provides an HTTP/REST endpoint that delivers a Property value, thus enabling the AAS Server to retrieve the data. Thus, the data integration is triggered by the AAS Server, i.e., in a pull principle.
By supporting various endpoints and complex transformations, the data can be tailored to the specific Property's needs.
<<Bild>>