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 / Features / Request
< BaSyx | Documentation | Components | DataBridge | Features
Revision as of 06:35, 31 January 2023 by Ghazanfar.Danish.iese.fraunhofer.de (Talk | contribs) (Created page with "= Request = The Request trigger is used to generate message exchanges on demand. The routes would be triggered when a request is made on the configured REST endpoint and the p...")
Request
The Request trigger is used to generate message exchanges on demand. The routes would be triggered when a request is made on the configured REST endpoint and the processed data will be returned as a response.
Configuration
You can specify "trigger": "request" in routes.json [Link] configuration file. Apart from this, you have to specify the trigger data in routes.json. This trigger data comprises of the host, port, and the service path, basically this would be the endpoint when requested, triggers the specified route, and return the processed data as a response.
Sample Route Configuration with Timer
[
{
"datasource": "httpsource",
"transformers": [
"jsonataA"
],
"trigger": "request",
"triggerData": {
"host": "localhost",
"port": "8090",
"path": "/valueA"
}
}
]
Please check the example HttpPolling-JsonAta-Delegator [Link] to know more about this.
Disclaimer: The endpoint configured with trigger data accepts only the GET request.