Skip to main content

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.

Jump to: navigation, search

BaSyx / Documentation / Components / DataBridge / Features / Timer

< BaSyx ‎ | Documentation ‎ | Components ‎ | DataBridge ‎ | Features
Revision as of 05:57, 31 January 2023 by Ghazanfar.Danish.iese.fraunhofer.de (Talk | contribs) (Created page with "= Timer = The Timer trigger is used to generate message exchanges when a timer fires. It means that the configured route would start processing the message when the configured...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Timer

The Timer trigger is used to generate message exchanges when a timer fires. It means that the configured route would start processing the message when the configured timer is triggered.

Configuration

You can specify "trigger": "timer" in routes.json [Link] configuration file. Apart from this, you have to specify the timer name as a trigger data inside routes.json.

Sample Route Configuration with Timer

[
  {
    "datasource": "httpsource",
    "transformers": ["jsonataA"],
    "datasinks": ["ConnectedSubmodel/ConnectedPropertyB"],
    "trigger": "timer",
    "triggerData" : {
    	"timerName": "timer1"
    }
  }
]

When configuring the timer as a trigger, you have to include another configuration file i.e. timerconsumer.json, for the configuration of timerconsumer.json please check Protocol Integration Timer[Link]. For e.g. As the above sample route configuration shows httpsource as datasource and the trigger is timer, then there will be two consumer configuration files i.e. httpconsumer.json and timerconsumer.json along with other configuration files.

Back to the top