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 / Introductory Examples / Java / Step 7"
(Small changes) |
m |
||
| Line 5: | Line 5: | ||
To do that, you have to configure the mqtt.properties, and the aas.properties file and pass it to the Docker container. | To do that, you have to configure the mqtt.properties, and the aas.properties file and pass it to the Docker container. | ||
| − | In the aas.properties you have to change the value aas.events as following: | + | In this example all the .properties files are in the C:\tmp\aas | C:\tmp\registry directory. |
| + | |||
| + | In the aas.properties / registry.properties you have to change the value aas.events / registry.events as following: | ||
# ############################# | # ############################# | ||
| Line 14: | Line 16: | ||
aas.events=MQTT | aas.events=MQTT | ||
| − | In the mqtt.properties you have to configure the server address and, if needed, | + | In the mqtt.properties you have to configure the server address and, if needed, Username and Password for authentication. |
You also have the ability to configure persistency as: File or InMemory. | You also have the ability to configure persistency as: File or InMemory. | ||
'''Note''':<code>InMemory is non-persistent</code> | '''Note''':<code>InMemory is non-persistent</code> | ||
| − | + | ||
To run the AAS Server container with the according configuration, execute: | To run the AAS Server container with the according configuration, execute: | ||
| Line 29: | Line 31: | ||
== Available Topics for subscribing == | == Available Topics for subscribing == | ||
A list of available Topics can be found [[BaSyx_/_Developer_/_Extensions_/_Eventing | here]] | A list of available Topics can be found [[BaSyx_/_Developer_/_Extensions_/_Eventing | here]] | ||
| + | |||
| + | Now you have the AAS Server and Registry Connected to your MQTT Broker. | ||
Revision as of 09:50, 13 September 2022
Enable MQTT eventing on the AAS Server and Registry
In order to enable MQTT eventing you have to configure the Docker container.
To do that, you have to configure the mqtt.properties, and the aas.properties file and pass it to the Docker container.
In this example all the .properties files are in the C:\tmp\aas | C:\tmp\registry directory.
In the aas.properties / registry.properties you have to change the value aas.events / registry.events as following:
# ############################# # MQTT # ############################# # Possible to enable MQTT events #aas.events=NONE aas.events=MQTT
In the mqtt.properties you have to configure the server address and, if needed, Username and Password for authentication. You also have the ability to configure persistency as: File or InMemory.
Note:InMemory is non-persistent
To run the AAS Server container with the according configuration, execute:
docker run -v C:\tmp\aas:/usr/share/config --name=aas -p 8081:4001 eclipsebasyx/aas-server:1.2.0
Same with the Registry Server
docker run -v C:\tmp\registry:/usr/share/config --name=registry -p 8082:4000 eclipsebasyx/aas-registry:1.2.0
Available Topics for subscribing
A list of available Topics can be found here
Now you have the AAS Server and Registry Connected to your MQTT Broker.