- Print
- PDF
The Azure Service Bus input module is used to pull messages from a Service Bus Queue or a Service Bus Subscription. Lasernet is notified of new messages by a Push-style notification system, so no Scheduler setup is required.
Configuration
To access the Azure Service Bus API, the properties must be correctly configured on the Setup page.
.png)
Type | Choose between Queue or Topic. Queues are used when you have one sender and one recipient, or if you need to balance the load by distributing messages between multiple recipients. If several input ports pull messages from the same queue, the messages will be distributed between them. Topics are used when you have one sender and several recipients. Each recipient must have its own subscription. Messages are delivered once to each subscription. |
Connection String | You can copy and paste the connection string from the Azure Portal. The remaining fields will be automatically populated by the content of the connection string. Alternatively, you can fill the remaining fields and the connection string will be automatically built. |
Subscription | Only visible in Topic mode. Enter the name of the subscription to pull messages from. |
Entity Path | The name/path of the Queue or Topic. |
SAS Key Name | The name of the Shared Access Service (SAS) key. |
SAS Key | The Shared Access Service (SAS) key used to authenticate Lasernet. |
Note
Batch mode for this module is controlled by a Batch mode checkbox on the General tab. For more information, see Multithreaded Processing Options for Input Modules in the Lasernet Developer 11 guide.
JobInfos
The following JobInfos are set for Jobs created from messages.
AzureServiceBusContentType | Content-type of message contents (see also MimeType). |
AzureServiceBusCorrelationId | The CorrelationId for this message, if specified by sender. |
AzureServiceBusDeliveryCount | The number of times the message has been delivered. |
AzureServiceBusExpiresAtUtc | Date and time in UTC at which the message is set to expire (RFC1123 format). |
AzureServiceBusForcePersistence | Sets a value to indicate whether the message is to be persisted to the database immediately instead of being held in memory for a short time. Ignored if message is sent to a non-express queue. |
AzureServiceBusLabel | A sender-assigned Label for the message, if present. |
AzureServiceBusLockedUntilUTC | Specifies when the initial lock expires – the lock is automatically extended by Lasernet if processing exceeds the lock timeout. |
AzureServiceBusMessageId | The (sender-assigned) message Id. Can be used to detect duplicates. |
AzureServiceBusMessagePropertyNames | Array of metadata field names to associate with the message. |
AzureServiceBusMessagePropertyValues | Array of metadata field values to associate with the message. |
AzureServiceBusPartitionKey | Partition key for sending a transactional message to a queue that is not session-aware. |
AzureServiceBusReplyTo | The queue or topic to send replies to, if specified by the sender. |
AzureServiceBusReplyToSessionId | The session ID to send replies to on a session-aware queue, if specified by the sender. |
AzureServiceBusScheduledEnqueuedTimeUTC | The time when the message was submitted to the queue or topic. |
AzureServiceBusSequenceNumber | The unique number assigned to the message. |
AzureServiceBusSessionID | The SessionID for this message, if session-aware queue is used. |
AzureServiceBusTimeToLive | The message’s time to live value in seconds. This is the duration after which the message expires, starting from when the message is sent to the Service Bus. |
AzureServiceBusTo | The send to address. |
AzureServiceBusViaPartitionKey | Partition key value when a transaction is to be used to send messages via a transfer queue. |
MimeType | The MIME type of the message content if specified by the sender. |
If any custom properties (metadata) are attached to the message, they will also be set as JobInfos. Properties are treated as key-value pairs. Objects and arrays (JSON) are not supported.