Documentation Index

Fetch the complete documentation index at: https://help.csgi.com/llms.txt

Use this file to discover all available pages before exploring further.

📢 Announcement:  Xponent Journey Hub, Bill Explainer, and Xponent Communication Control April 2026 (26.1) Release Notes are now available – Check out the latest updates published on April 2026.

Message Queue Connection

Prev Next

Message Queue Listeners or Message Queue Adaptors use Kafka Connections.





In Xponent Journey Hub, a queue connection is actually a pair of queues acting as a read/write queue pair. 

  • Type: the type of the message queue
    • Amazon SQS - Amazon web services simple queue service
      • Xponent does not currently support the AWS SQS FIFO queue type. The Standard Queue type provides unlimited throughput and offers faster processing as a result. 
    • Active MQ - Apache Active MQ version 5.9 upwards
    • Rabbit MQ - version 3 upwards 
    • Azure Service Bus - Microsoft's cloud messaging service
  • Read Queue: name of the Read/Listen Queue 
    • Amazon SQS - the queue name - not the URL or URN 
    • Active MQ - the queue name - e.g. dynamicQueues/Q1
    • Rabbit MQ - the queue name 
    • Azure Service Bus- the queue name
  •  Write Queue: name of the Write Queue
    • Amazon SQS - the queue name - not the URL or URN 
    • Active MQ - the queue name - e.g. dynamicQueues/Q1
    • Rabbit MQ - the queue name 
    • Azure Service Bus- the queue name
  • For Amazon SQS 
    • AWS Access Key Id
    • AWS Secret Access Key
    • AWS Region - one of the AWS regions e.g. us-east-1, eu-west-1 
  • For Active MQ and Rabbit MQ
    • User Name - username to connect to the queue - if required
    • Password - password to connect to the queue - if required
    • Host - IP address or fully qualified domain name of the queue broker 
    • SSL - select true if the queue is connected to using secure socket layers 
  • For Azure Service Bus
    • Key Name - the name of the shared access policy under which the message queues operate. The available permissions on the policy will determine actions possible on the message queue- send, listen, and manage
    • Key - primary or secondary keys of the shared access policy under which the message queue operates
    • Namespace - service bus namespace