Microsoft Azure Service Bus is a cloud messaging service between applications and services. This article describes how to configure the service in the Universal Data Hub.
|Action Name||Trigger on Audience||Trigger on Streams|
|Send Event Data to Queue or Topic||✗||✓|
|Send Visitor Data to Queue or Topic||✓||✗|
|Send Customized Data to Queue or Topic||✓||✓|
Go to the Connector Marketplace and add a new Microsoft Azure Service Bus Connector. Read the Connector Overview article for general instructions on how to add a Connector.
To configure your vendor, follow these steps:
In the Configure tab, provide a title for the Connector instance.
Enter Service Bus Namespace, Shared Access Policy Name and Key. For more information, see Namespace & Shared Access Policies.
Click Test Connection to verify API connectivity with the provided credentials.
Shared Access Policies can claim three type of permissions:
Manage. Provided policy must claim at least
Click Next or go to the Actions tab. It's where you'll set up Actions to trigger.
This section describes how to set up Parameters and Options for each Action.
All Actions support Message User and Broker properties. They provide useful and convenient information about a message using key-value pairs. But they are set as HTTP headers and do not reside within the message body. For more information see Message User & Broker Properties
|Content Type||Sets HTTP header
|Correlation ID||Unique identifier of the correlation|
|Session ID||Can be used to partition and route messages to particular consumers|
|Message ID||Overrides default auto-generated Message ID|
|Reply To||Can be used to specify where to send a response for message consumers|
|Time to Live in Seconds||Expire message after X number of seconds (overrides queue/topic level)|
|To||Send to address|
|Scheduled Enqueued Time||Scheduled date and time at which the message is enqueued|
|Reply to Session ID||Similar to Reply To but targets a session for a response|
|Partition Key||Unique identifier of the partitioned queue or topic|
If necessary, templates can also be referenced and injected in user and broker properties.