Microsoft Azure Service Bus Provider
You can write an application on Azure and subscribe to an Azure Service Bus to receive Reltio events.
Using Azure as your cloud provider, you can receive all streaming events using the Azure
Service bus so that you can develop your applications in a single technology stack. The
Azure Service Bus supports Queues for point-to-point communication
and Topics for publish or subscribe scenarios.
This feature provides the following advantages:
- Enables you to create a queue in the Azure Service Bus to which events are set.
- Enables you to provide authentication details for Reltio to use to connect to the queue.
- Enables you to write an application on Azure, subscribing to an Azure Service Bus to receive Reltio events.
- Enables you to secure your data at all stages of delivery (in transit and ensuring only authorized applications can connect to the service bus to receive messages).
- Your streaming queue to the Azure Service Bus is configurable per tenant physical configuration as another messaging destination.
- Enables the queue dashboard in your console to report on relevant Azure Service Bus-related metrics.
- Enables you to define the provider into a destination such as
azure://MySharedAccessKey:VFXO%2FZFPwkjK0Ti1VfYyPfIp75uuq84THTlUWDRnumI%3D@my-namespace
and specify a name of the queue, such as
<namespace>:{name}.
Microsoft Azure Service Bus Provider Parameters
The Microsoft Azure Service Bus Provider Parameters table explains various parameters for Service Bus Provider:
| Name | Required | Description | Example |
|---|---|---|---|
type |
Yes | Constant | azure |
host |
Yes | The name of the Azure Service Bus name space in which queues/topics are created or required in which to be created. | my-namespace |
username |
Yes | The Azure Service Bus Shared Access
(SAS) authorization policy rule name. This
authorization rule must have Manage rights in order to have
the possibility to create topic/queue on-the-fly. If this
possibility is not required, and all the topics/queues in tenant
configured destinations are pre-created, then the authorization rule
can be limited to only Send rights. It is not recommended to
use the default RootManageSharedAccessKey
authorization rule name. You must create another rule name with the
required rights. |
|
password |
Yes | The Azure Service Bus authorization policy rule Primary or Secondary Key. |
Microsoft Azure Service Bus Naming Restrictions
Name Spaces
The value must be between six and 50 characters long. The name space can contain only letters, numbers, and hyphens. The name space must start with a letter, and it must end with a letter or number. Name space names are case-insensitive.
Topics or Queues
Queue names can contain letters, numbers, periods (.), hyphens (-), underscores (_), and slashes (/), up to 260 characters. They must start and end with a letter or number. Queue names are also case-insensitive.
Adding New Providers at Run Time
A limited implementation of re-loading the dynamic configuration is supported for environment configuration. Currently, this includes the detection of new provider configurations without the need to restart the API server. In order to avoid loss of messages, it is important that a new provider be configured first in the appropriate environments using the messaging configuration file described in this topic. Only after this configuration has been updated must the Tenant's configuration be updated to reference the new provider.
For more information, see Events API.