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 / Features / Event"
< BaSyx | Documentation | Components | DataBridge | Features
m (→Working Example) |
|||
| Line 19: | Line 19: | ||
== Working Example == | == Working Example == | ||
| − | The integration example with '''event triggered''' MQTT as a data source, JSONata as a transformer, and AAS as a data sink is available on [https://github.com/eclipse-basyx/basyx-databridge/tree/main/ | + | The integration example with '''event triggered''' MQTT as a data source, JSONata as a transformer, and AAS as a data sink is available on [https://github.com/eclipse-basyx/basyx-databridge/tree/main/databridge.examples/databridge.examples.opcua-jackson-jsonata-aas GitHub DataBridge Example]. |
Latest revision as of 03:06, 10 May 2023
Event
The Event trigger is used to generate message exchanges whenever an event occurs. This trigger is used when the data source produces data asynchronously for e.g. when an MQTT message is published on a topic then the route would start processing.
Configuration
You can specify "trigger": "event" in routes.json.
Sample Route Configuration with Event
[
{
"routeId": "namedRoute",
"datasource": "property1",
"transformers": ["jsonataA"],
"datasinks": ["ConnectedSubmodel/ConnectedPropertyA"],
"trigger": "event"
}
]
Working Example
The integration example with event triggered MQTT as a data source, JSONata as a transformer, and AAS as a data sink is available on GitHub DataBridge Example.