Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "BaSyx / Documentation / Components / AAS Server / Features / Simple MQTT"
< BaSyx | Documentation | Components | AAS Server | Features
Line 20: | Line 20: | ||
aas.events=MQTT | aas.events=MQTT | ||
− | |||
The MQTT broker endpoint can be configured via [[BaSyx_/_Documentation_/_Components_/_MQTT | '''mqtt.properties''' file]] | The MQTT broker endpoint can be configured via [[BaSyx_/_Documentation_/_Components_/_MQTT | '''mqtt.properties''' file]] |
Revision as of 03:23, 28 November 2022
Contents
Simple MQTT Eventing
User Story & Use Case
As AAS Components user
I want simple MQTT topics in the AAS Server Component
so that I can receive MQTT events without having to worry about subscribing to detailed topics
If the hierarchical topics presented in Hierarchical MQTT Eventing are too complicated, this feature will support event-driven use cases.
Feature Overview
Information about what events will be published can be found in the eventing extension.
Feature Configuration
Eventing via MQTT is disabled by default. It can be enabled in the aas.properties file as well. This will publish events for every action to a separately specified server:
aas.events=MQTT
The MQTT broker endpoint can be configured via mqtt.properties file