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 / Protocol Integration / HTTP"
< BaSyx | Documentation | Components | DataBridge | Features
(Created page with "= HTTP = The HTTP source can be integrated with DataBridge. The data from the specified HTTP endpoint is fetched, processed and then delivered to the sink. == Configuration =...") |
m (→Working Example) |
||
| Line 23: | Line 23: | ||
== Working Example == | == Working Example == | ||
| − | The integration example with HTTP as a data source, JsonAta as a transformer, and AAS as a data sink is on [https://github.com/eclipse-basyx/basyx-databridge/tree/main/ | + | The integration example with HTTP as a data source, JsonAta as a transformer, and AAS as a data sink is on [https://github.com/eclipse-basyx/basyx-databridge/tree/main/databridge.examples/databridge.examples.httppolling-jsonata-aas GitHub DataBridge Example]. |
Revision as of 03:10, 10 May 2023
Contents
HTTP
The HTTP source can be integrated with DataBridge. The data from the specified HTTP endpoint is fetched, processed and then delivered to the sink.
Configuration
To configure HTTP in DataBridge you need to provide the unique id, and the HTTP server details like host, port, and service path (query).
Sample Configuration
[
{
"uniqueId": "httpsource",
"serverUrl": "127.0.0.1",
"serverPort": 1234,
"query": "foo"
}
]
Similarly, you can configure multiple HTTP consumers inside the configuration file.
Naming Convention
The name of the HTTP consumer configuration file should be httpconsumer.json.
Working Example
The integration example with HTTP as a data source, JsonAta as a transformer, and AAS as a data sink is on GitHub DataBridge Example.