Queues Management

Create Service Bus Queue

Create a Service Bus Queue from Cerebrata with full access to the properties of the Queue. Properties of Service Bus Queue is grouped into two types.

• Basic properties
• Advanced properties

Basic Properties of Service Bus Queue contains

1. Partitioned Queue - Partitions a queue across multiple message brokers and message stores. Disconnects the overall throughput of a partitioned entity from any single message broker or messaging store. This property is not modifiable after a queue has been created.
   1. Max Queue Size - Maximun size of a queue. Value can be 1GB, 2GB, 3GB, 4GB, 5GB.
2. Max Delivery Count - All the messages received after this max delivery count will be automatically Deadlettered.
3. Time To Live - TTL is the duration after which a message will be expired and made Deadlettered if Dead letter on message expiration is enabled.
4. Lock Duration is the fixed period for which the broker locks the message for a specific consumer, preventing other consumers' access. The maximum value of this section can be 5mins.
5. Enable Dead Lettering On Message Expiration - Queue enabled with this option will ensure that queue has dead-letter support on message expiration.

Advanced Properties of Service Bus Queue will have

1. Enable Auto Delete On Idle - Delete the queue immediately after it remains idle for a configurable amount of time.
2. Duplication Detection History Time Window
3. Auto Forwarding - Automatically forward messages to a queue or topic in the same/different namespace.
4. Forward Deadletterd messages - Automatically forward Deadlettered messages to a queue or topic in the same/different namespace.
5. Enable/Disable Batched Operation - Enable Server Side batched operation.
6. Enable/Disable Express - Express entities enable high throughput and reduced latency scenarios. If a message is sent to a queue or topic, it is not immediately stored in the messaging store in express entities. Instead, the message is cached in memory.
7. Requires Session - Service bus sessions allow ordered handling of unbounded sequences of related messages. With sessions enabled a queue can guarantee first-in-first-out delivery of messages.
8. Enable/Disable Message Ordering - Enable the queue with ordering
9. Requires Duplication Detection - Enabling duplicate detection configures your queue to keep a history of all messages sent to the queue for a configurable amount of time. During that interval, your queue will not accept any duplicate messages. Enabling this property guarantees exactly-once delivery over a user-defined span of time.

Open Service Bus Queue (View Messages)

A consumer can receive Service Bus messages in different retrieval modes. However, the quickest method is using the open messages option.

The consumer using this method will retrieve all active messages in Peek Mode.
To know more about different retrieval modes, click here.

Add New Message to a Queue

Messages can be pushed into a Service Bus queue right from Cerebrata itself. User can click on the add new message option available with each queue.

Cerebrata allows the users to send more than one message at a time to any Service Bus Queue. It is also possible to specify if each message must be sent with a unique message id or not by enabling the Update Message Id option.

Users can also send the messages in a Batch with required number of messages in the batch by specifying the Batch size and enabling the Send Batch option.

It is also possible to specify the Think Time while sending the messages so that each message or batch of messages are sent after the provided time interval.

User has the flexibility to add system and custom properties to Service Bus message.

• Message Text: User can add the content of the message in JSON, XML or OTHERS
• Time To Live(TTL): TTL is the duration after which a message will expire. This value cannot exceed the default message TTL value on the destination queue.
  

In the advanced properties, the user can add the following parameters.

• Message-Id
• Content-Type
• Correlation Id
• Label
• Session Id
• Partition Key
• Reply To
• Reply To Session Id
• To
• Via Partition Key
• Enable Force Persistence

Adding Custom Properties to a Service Bus message

Custom properties can be added to Service Bus messages using Cerebrata.

1. To add custom properties in a new Service Bus message, user can take advantage of the CUSTOM PROPERTIES option available.
   
2. Now user can click on New Property option and add the Name and Value for the custom property.
   
3. Click on OK. This will add the entered custom value properties to the message

User can even delete a custom property of a message.

Adding Enqueue Time

Enqueue time specifies the time after which a message will be enqueued.
User can provide Enqueue time using the Enqueue Time option.
{height="" width=""}
Then in the pop-up user can provide the time period after which a message should be enqueued.
User can even provide a specific date and time for a message to be enqueued.

View Messages Count

User can quickly get the count of active messages, dead lettered messages, Message count, scheduled messages count, transfer message count, transferred dead letter message count in a queue or topic subscription. To view the message count, user can click on

required queue name > Action > Messages count

Update Queue Status

Users can quickly update the status of the queues using Cerebrata. Queues can be set to any of the following properties.

• Active
• Disabled
• SendDisabled
• ReceiveDisabled

Settings

As an add on to Azure Service Bus Queue's management capabilities, Cerebrata also offers a settings option for the users.

1. Navigate to Files > Settings > Application Settings > Service Bus Settings.
   

2. User can specify the default tab to open while double clicking on Queue node. The default tab can be active messages, dead-letter messages or the monitor tab.

3. Define the maximum number of messages fetched per page. These messages have peeked, and the value provided must start from 100 and should be less than or equal to 10000.

4. Set Behaviour to display the messages in different pannel views.

5. User has an option to use AMQP over Websocket if required.