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.
Difference between revisions of "BaSyx / Documentation / Components / DataBridge"
| Line 4: | Line 4: | ||
= Asset Integration made Easy with the DataBridge = | = 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. | + | The DataBridge supports integrating various protocols with Asset Administration Shells. Data can be acquired from various endpoints, be transformed and pushed into SubmodelElements. By being provided as easy-to-use off-the-shelf component on [https://hub.docker.com/r/eclipsebasyx/databridge DockerHub], it can easily be integrated in own use cases. |
Currently, the DataBridge supports three different types of integration: | Currently, the DataBridge supports three different types of integration: | ||
| Line 11: | Line 11: | ||
* Integration via Delegation | * Integration via Delegation | ||
| − | For all three integration patterns, transformation of data is supported. | + | For all three integration patterns, transformation of data is supported. A running example utilizing the DataBridge is provided on [https://github.com/eclipse-basyx/basyx-java-examples/tree/main/basyx.examples.deviceintegration/src/main/resources GitHub] |
== Integration via Cyclic Updates == | == 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 | 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 | ||
| − | |||
| − | |||
== Event-triggered Integration == | == 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. | 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. | ||
| − | |||
| − | |||
| − | |||
== Integration via Delegation == | == Integration via Delegation == | ||
| Line 29: | Line 24: | ||
By supporting various endpoints and complex transformations, the data can be tailored to the specific Property's needs. | By supporting various endpoints and complex transformations, the data can be tailored to the specific Property's needs. | ||
| − | |||
| − | |||
Revision as of 06:57, 27 January 2023
| 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. By being provided as easy-to-use off-the-shelf component on DockerHub, it can easily be integrated in own use cases.
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. A running example utilizing the DataBridge is provided on GitHub
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
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.
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.