Admin: Queue Setup

RPI uses queues in the following contexts:

Collating Realtime states and metrics

Web form submission

Managing data from the Realtime cache

Queue listeners

Recommendation endpoint result collation

Queueing functionality can be provided by a range of Queue Providers, which are managed in the RPI application in a dedicated configuration interface. Please see the User Guide for more information. Note that a default MSMQ queue provider is automatically created at RPI installation.

A Copy JSON configuration to clipboard button is available at each queue provider. Clicking it copies to the clipboard a JSON snippet, structured as per the following example:

JSON

{
  "Assembly": "Redpoint.Resonance.AzureQueueAccess",
  "Type": "Redpoint.Resonance.AzureQueueAccess.AzureServiceBusQueueFactory",
  "Settings": [
    {
      "Key": "ConnectionString",
      "Value": "Endpoint=sb://Redpointinteractiondev.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=EcWsxCsX+xOLQCdt0H6kScI1bR252V+WGljpou5MjwQ=",
      "Values": null
    }
  ]
}

This text must be copied into the ClientQueueSettings setting at the RPI Realtime appsettings.json file. Queue Listener queue details are copied into ListenerQueueSettings. To determine if configured correctly, browse to the RPI Realtime status page: [RPI Realtime website]/status

Details of the specific queues required to support each of the above are provided separately.

Please note the following:

When setting up MSMQ queue config settings, the full path of the queue must be provided (e.g. ‘.\Private$\RPIWebCacheData’).

If using Azure queue, set its lock duration to the maximum permissible value (5 minutes).