DataPower

 View Only

 AMQP Handler Configuration Question

Roberto Soto's profile image
Roberto Soto posted Tue July 15, 2025 11:18 AM

Hello All,

Is it possible to configure a Front Side Protocol AMQP handler in a similar fashion as an HTTPS handler with a local listening IP address/hostname and port?

Situation:

We want to configure an AMQP handler to listen on a local IP/host alias and port for an internal client to connect to it via AMQPS. We already configured an AMQP broker instance to connect to externally. We expect to have several AMQP topics that we will subscribe and publish to that are effectively not associated with each other for the purposes of this discussion e.g. not expecting a response from our external consumer for messages we publish to them and we are not planning to immediately reply to messages that we receive from topics we subscribe to; when we do reply it could be some time later and will be on a different topic than we received the messages on.

The latest online documentation for "Configuring an AMQP handler" states the following:

  • In the Source terminus field, specify the name of the source terminus to retrieve the message that might be the reply to a posted message.
  • In the Target terminus field, specify the name of the target terminus to post the message.
  • Set Ignore reply-to field to indicate whether to ignore the AMQP reply-to property.
    When disabled, uses the reply-to address instead of the address of the target terminus
  • Reference: https://www.ibm.com/docs/en/datapower-gateway/10.6.x?topic=configuration-configuring-amqp-handler

It is not clear which of these two fields (Source/Target) is the one to configure to listen other than that the Source is required per the DataPower management console webpage. Additionally it is not clear what is the format expected for specifying a host and port, along with allowing through multiple variations of topic names for publishing and subscribing to. Some examples would be much appreciated, specifically for AMQP topic exchanges.

Some examples of what we have already tried:

Source terminus:

  • amqp://hostname:port
    • op state = down
  • amqps://hostname:port
    • op state = down
  • hostname:port
    • op state = up 
    • DataPower ends up creating a queue with the name "hostname:port" on RabbitMQ on the default "/" virtual host

Thank you