Azure Service Bus Connector Guide > Azure Service Bus connections > Azure Service Bus source properties
  

Azure Service Bus source properties

You can configure an event source in an Azure Service Bus connection.
After you define an event source for an Azure Service Bus connection, you can publish the connection on the Cloud Server. You can then access the event source in a process and deploy the process on the Cloud Server to consume the events generated by the event source.
To create event sources for an Azure Service Bus connection, click Add Event Source on the Event Sources tab. Select the event source type as Azure ServiceBus Reader. You can add one or more event sources for each Azure Service Bus connection that you create.
The following table describes the basic event source properties that you can configure:
Property
Description
Name
Required. The event source name that appears in the Process Designer. The name must be unique for the connection.
The name must start with an alphabet and can contain only alphabets, numbers, or hyphens (-).
Description
Optional. A description for the Azure Service Bus event source that appears in the Process Designer.
Enabled
Select Yes to make the event source available immediately after it is published.
Select No to disable the event source until you are ready to use it.
Default is Yes.
The following table describes the advanced event source properties that you can configure:
Property
Description
Service Bus Type
Required. Select the service bus type based on whether you want to subscribe to a queue or topic.
Queue/Topic Name
Required. Enter the queue or topic name from which the message needs to be consumed. To consume a message from a dead letter queue (DLQ), you must provide the name appended with the $ symbol as a suffix as shown in the following format:
<queue_name or topic_name>/$deadletterqueue
Subscription Name
Optional. If you had selected the service bus type as Topic, enter the subscription name.
Content Format
Required. Select the content type for the Service Bus message that needs to be consumed. You can select Text, XML, or JSON.
Simplify Content
Required. Enable this option if the XML or JSON content to be processed does not match a valid process object structure. The event source modifies the content structure to match the process object format.