When a resource data forwarding rule is created Hagleitner senseManagement will create necessary infrastructure that can be used by 3rd party software systems to subscribe to this forwarded data. This includes an Azure Service Bus queue and a SignalR Hub Group. The necessary data that is needed to access the Azure Service Bus queue and the SignalR Hub Group is generated (including unique secrets so that each rule has its unique connection data).

For connecting to the Azure Service Bus queue created for a rule HsM provides the connection string and the Queue name. For The SignalR Hub HsM Group provides a connection string. Note that the SignalR Hub Group will only be created once a client connects with this connection string.

On deletion of a resource data forwarding rule HsM will also delete the Azure Service Bus queue.

Rotating connection data

As explained above the connection data for Azure Service Bus and SignalR Hub are exposed when creating a resource data forwarding rule. Clients will then use this connection data to subscribe to the forwarded data, i.e. the connection data is shared with those clients. If for some reason the clients should not have access any more, the connection data can be rotated, i.e. new connection data can be created for the same rule for the SignalR Hub Group and/or the Azure Service Bus queue.

Rotating the connection data will disable access to the Azure Service bus queue or the SignalR Hub Group with the previous connection data.