> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/amqp-producer/options-amqp-producer/setup-tab.md).

# Setup tab

![AMQP PRODUCER STEP Setup tab](/files/N1iG97AKgyMMuVkSTQKl)

The **Setup** tab defines connections for publishing messages, queue names, exchange name and type, and routing keys or headers.

| Option            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Connection**    | Specify the URI address of the AMQP broker which this step will connect to publish messages into PDI. For more information see: <https://www.rabbitmq.com/uri-spec.html>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| **Exchange name** | <p>Specify the exchange name to which this step will publish messages.</p><p>To use <strong>DEFAULT</strong> as the <strong>Exchange type</strong> (below), leave this option blank and set the <strong>Exchange type</strong> to <strong>DIRECT</strong>.</p><p>Leave this option blank if you did not specify an <strong>Exchange name</strong> in the <a href="/pages/Gtt1cJOuPUuUnmXMhLU4">AMQP Consumer</a> step.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| **Exchange type** | <p>Specify the type pattern this exchange is using.</p><ul><li><strong>DIRECT</strong></li></ul><p>Routes messages to queues based on the message <strong>Routing key</strong> (specified below).</p><ul><li><strong>DEFAULT</strong></li></ul><p>To use the <strong>DEFAULT</strong> exchange type, do not specify an <strong>Exchange name</strong> (above) and set the <strong>Exchange type</strong> to <strong>DIRECT</strong>.</p><ul><li><strong>FANOUT</strong></li></ul><p>Routes messages to all the queues that are bound to the fanout exchange and the routing key is ignored.</p><ul><li><strong>TOPIC</strong></li></ul><p>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. Specify the <strong>Routing key</strong>in the option below.</p><ul><li><strong>HEADERS</strong></li></ul><p>Routes messages using one or more key/value pairs that are more easily expressed as message headers than a routing key. Specify the headers in a table using the <strong>Headers</strong> option.</p> |
| **Routing key**   | <p>If you selected <strong>DIRECT</strong> or <strong>TOPIC</strong> as the <strong>Exchange type</strong>, you must select a routing key retrieval method:</p><ul><li><strong>Specify Routing Key</strong>: Select this retrieval method to enter a specific routing key name.</li><li><strong>Get data from field</strong>: Select this retrieval method to specify a field from which to retrieve routing key data.</li></ul><p>To use the <strong>DEFAULT</strong> configuration:</p><ol><li>Do not specify an <strong>Exchange name</strong> (above).</li><li>Choose <strong>DIRECT</strong> as the <strong>Exchange type</strong> (above).</li><li>Specify the queue name in this <strong>Routing key</strong> field. The queue name you specify here must match the queue name you specified in the <strong>Queue name</strong> option in the <a href="/pages/Gtt1cJOuPUuUnmXMhLU4">AMQP Consumer</a> step.</li></ol>                                                                                                                                                                           |
| **Headers**       | <p>If you selected <strong>HEADERS</strong> as the <strong>Exchange type</strong>, you must specify a retrieval method, and then specify the <strong>Name</strong> and <strong>Value</strong> in the accompanying table. To specify the retrieval method, select one of the following:</p><ul><li><strong>Specify headers</strong> - Enter the header <strong>Name</strong> and <strong>Value</strong>.</li><li><strong>Get data from field</strong> - Enter the field from which to retrieve the header <strong>Name</strong> and <strong>Value</strong>.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| **Message field** | Specify this step's input field from which this step will retrieve the message you are publishing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/amqp-producer/options-amqp-producer/setup-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.