AMQP is a wire-level messaging protocol that describes the format of the data that is sent across the network. If a system or application can read and write AMQP, it can exchange messages with any other system or application that understands AMQP, regardless of the implementation language.
...
| Parameter | Description | Required | |||||
|---|---|---|---|---|---|---|---|
rabbitmq.connection.factory | The name of the connection factory. | Yes | |||||
rabbitmq.exchange.name | Name of the RabbitMQ exchange to which the queue is bound. Use this parameter instead of rabbitmq.queue.routing.key, if you need to use the default exchange and publish to a queue. | No | |||||
rabbitmq.queue.name | The queue name to send or consume messages. If you do not specify this parameter, you need to specify the rabbitmq.queue.routing.key parameter. | Yes | |||||
rabbitmq.queue.auto.ackWhether | to automatically send back an acknowledgment when consuming messages from queue. When you set this to false, it sets the configuration to handle the acknowledgement in the application level. Thus, it sends back the acknowledgement once it sends the request to the back-end. (i.e., It does not wait for the response) Defines how the message processor sends the acknowledgement when consuming messages recived from the RabbitMQ message store. If you set this to true, the message processor automatically sends the acknowledgement to the messages store as soon as it receives messages from it. This is called an auto acknowledgement. If you set it to false, the message processor waits until it receives the response from the backend to send the acknowledgement to the mssage store. This is called a client acknowledgement. | No | |||||
rabbitmq.consumer.tag | The client generated consumer tag to establish context. | No | |||||
rabbitmq.channel.consumer.qos | The consumer qos value. You need to specify this parameter only if the rabbitmq.queue.auto.ack parameter is set to false. | No | |||||
rabbitmq.queue.durable | Whether the queue should remain declared even if the broker restarts. | No | |||||
rabbitmq.queue.exclusive | Whether the queue should be exclusive or should be consumable by other connections. | No | |||||
rabbitmq.queue.auto.delete | Whether to keep the queue even if it is not being consumed anymore. | No | |||||
rabbitmq.queue.routing.key | The routing key of the queue. | No | |||||
rabbitmq.exchange.type | The type of the exchange. | No | |||||
rabbitmq.exchange.durable | Whether the exchange should remain declared even if the broker restarts. | No | |||||
rabbitmq.exchange.auto.delete | Whether to keep the queue even the exchange even if it is not used bound to any queue anymore. | No | |||||
rabbitmq.message.content.type | The content type of the consumer.
| No. The default value is text/xml. | |||||
rabbitmq.queue.autodeclare | Whether to create queues if they are not present. However, you should set this parameter only if queues are not declared prior on the broker. Setting this parameter in the publish URL to false improves RabbitMQ transport performance. | No | |||||
rabbitmq.exchange.autodeclare | Whether to create exchanges if they are not present. However, you should set this parameter only if exchanges are not declared prior on the broker. Setting this parameter in the publish URL to false improves RabbitMQ transport performance. | No |
...