To use an AMQP message queue that already exists on the broker, define the options in the Setup tab as follows:
| Option | Description |
|---|---|
| Connection | Specify the URI address of the AMQP broker to which this step connects to ingest messages into PDI. For more information see: https://www.rabbitmq.com/uri-spec.html |
| Queue name |
Specify the name of an existing AMQP message queue
name from which this step will ingest messages. The specified queue must conform to
these parameters:
Note: If you specify
the name of a queue which does not already exist, this step will create a new queue.
The new queue will conform to the same parameters. See Create a new AMQP Message Queue.
|
| Exchange name |
Specify an existing exchange name from which to bind the queue. Leave the Exchange name blank to use the DEFAULT as the Exchange type (below) and set the Exchange type to DIRECT. The AMQP Producer step requires a matching blank entry in its Setup tab for the Exchange name. |
| Exchange type |
Specify the type pattern this exchange is using: DIRECT routes messages to queues based on the message routing key.
FANOUT routes messages to all the queues that are bound to the fanout exchange and the routing key is ignored. TOPIC routes messages to one or many queues based on a match between a message routing key and the pattern used to bind a queue to an exchange. HEADERS routes messages using one or more key/value pairs that are more easily expressed as message headers than a routing key. |
| Routing Keys | Use the Routing Keys table to specify the routing keys that define the bindings between the exchange and the queue. See Specify Routing Keys for more information. |
| Headers | Use the Headers table to specify the Name and Value associated with the appropriate headers. See Specify Headers for more information. |