Contents
 Contents

Editing Global Default DMQ Configuration

  1. Launch Fiorano Studio and open the appropriate profile through the Profile Manager
    The tree displayed shows all the queues and topics created under the node ptp > queues.

    Icon

    The queues are shown in off-line mode only if the server has been started with the same profile at least once before.

  2. Navigate to Fiorano > mq > ptp > QueingSubSystem.

DMQ related properties that are editable through the properties panel of this node are listed in the table below:

S.No

Parameter

Description

1

DMQExpiryTime

The amount of time (in milliseconds) that message live on DMQ.

2

CleanupDmqAtStartup

If enabled, all DMQ messages are deleted upon server startup.

3

EnableDMQOnAllQueues

Boolean value of DMQ status for all queues that have the DMQEnabled property configured to "Default".

Disabling DMQ on the  message level

An application can disable the DMQ function on a 'per message' basis by invoking the API, below, on a message prior to sending the message.

Since this is a proprietary API, using it requires that the application include the import statements below:

This API is effective only when the DMQ is enabled. If DMQ is not enabled, using this API with the boolean value set to true will not have any effect.

Enabling Notifications for Expired Messages

  1. Launch Fiorano Studio and open the appropriate profile using the Profile Manager tab.
    The tree displayed shows all the queues and topics created under the node ptp > queues & pubsub > Topics.

    Icon

    The queues are shown in the off-line mode only if the server has been started with the same profile at least once before.

  2. Navigate to Fiorano > mq > ptp > QueingSubSystem and edit the EnableNotificationsOnDeadMessage property.

Subscribing to Notifications for Expired Messages

When a message expires, the server, if configured (as Enabling Notifications), publishes a notification in the form of a JMS Text message on a system topic named ADMINISTRATOR_TOPIC. In order to receive this notification, a simple Subscriber can be created on this topic as per the JMS Semantics.

Disabling Expiry Notifications on a message level

An application can disable the notification function on a 'per message' basis by invoking the following API on a message before sending the same.

Since this is a proprietary API, using it requires that the application include the import statements below:

This API is effective only when the DMQ and the 'notification' are enabled on the queue.

Adaptavist ThemeBuilder EngineAtlassian Confluence