The options and settings in the AMQP Consumer Setup tab make it possible for you to create a new AMQP message queue the first time you run the AMQP Consumer step in a transformation. The new AMQP message queue will default to the following properties:
- Durable
- Non auto-delete
- Non-exclusive
When you use the AMQP Consumer to create a new queue, the broker bindings are initialized the first time you run the AMQP Consumer step in a transformation. Once you initialize the bindings, you can then start the AMQP 0-9-1 message producer before running the AMQP Consumer step. As a recommended best practice, always run the AMQP Consumer step first, before you start producing or publishing any messages through the AMQP producer.
To create a new AMQP message queue on the broker, define the Connection, Queue name and Exchange name 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 a new AMQP message queue from which this step will ingest messages. The new queue will be created automatically the first time you run the transformation. The new queue and its exchange attributes will default to the following properties:
Note: If you specify a queue name that already exists on the broker, but the
existing queue has parameter settings that differ from these, or if the specified
queue has an Exchange type (below) that is different, the
transformation will abort.
|
| Exchange name |
Specify either a new exchange name or an existing exchange name from which to bind the queue. If the exchange name does not already exist, it will default to the following
properties:
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 will require a matching blank entry in its Setup tab for the Exchange name. |
Set up the remaining Exchange type, Routing Keys or Headers options as explained in Use an existing AMQP Message Queue.