BaSyx / Documentation / Components / Registry / Features

AAS Registry Features

The AAS Registry Components supports a multitude of features with a great range of configuration options:

• Storage Backend
• MQTT Eventing
  • Simple MQTT Eventing

Authorization

Authorization is disabled by default. Basic authorization can be configured in the registry.properties:

registry.authorization=Enabled
registry.authorization=Disabled

Tagged Directory

The TaggedDirectory is disabled by default. It can be configured in the registry.properties:

 registry.taggedDirectory=Enabled
 registry.taggedDirectory=Disabled

Tagged Directory

[Disclaimer: In development branch]

A tagged directory is an implementation of the registry that allows to associate AAS with tags. When in use, AAS can be retrieved based on tags.

Disclaimer: Currently only works with an InMemory backend. Persistent backends (SQL and MondoDB), as well as combination with Authorization, or MQTT is yet to be supported.

Authorized AAS Registry

As stated above in context configuration there are some properties stated related to JWT based Authorization. This Authorization mechanism makes authorized access to the AAS Registry. Read and write authorization is enabled. In order to read from the registry or write to the registry there is a need of authorization token.

Example demonstrating above scenario is here Authorized AAS Registry.

Eventing with MQTT

Additionally, to the registry.properties file, you need to edit the mqtt.properties file in order to connect to the right MQTT broker. The MQTT configuration file can be found in the same folder as the backend configuration. It allows you to add credentials and a Quality of Service level (default: 1) besides the mandatory server address.

Information about what events will be published can be found in the eventing extension.