RabbitMQ properties

RabbitMQ connection

Select RabbitMQ in the list and configure the connection.

Select your engine from the list and set the main and advanced settings.

Main settings
Property	Configuration
Host name and Port	Enter the virtual host name and port of your RabbitMQ broker. By default, the port is: `5672`.
Username and Password	Enter the credentials used for the database authentication.
Use TLS	Toggle this option ON to enable the TLS encrypted connection.

Advanced settings
Property	Configuration
Use virtual host	Enable this option to use a virtual host for publishing or receiving messages. Specify the virtual host name to be used in the Virtual host name field.

After configuring the connection, give it a display name (mandatory) and a description (optional).

Dataset configuration
Property		Configuration
Dataset name		Enter a display name for the dataset. This name will be used as a unique identifier of the dataset in all Talend Cloud apps.
Connection		Select your connection in the list. If you are creating a dataset based on an existing connection, this field is read-only.
Type		Select the type of mechanism used to read messages: either Exchanges (where messages are published) or Queues (where messages are distributed then consumed).

Main settings
Property	Configuration
Queue properties	Schema: Type in or select the schema of the messages to be retrieved. You can manually add the `message` and `headers` fields here. Queue: Enter the name of the queue from which you want to read messages from between double quotation marks.
Exchange properties	Exchange type: Select the exchange type in the list. Exchange name: Enter the exchange name between double quotation marks.

Advanced settings
Property	Configuration
Return headers	Enable this option to retrieve header information from the received messages. Retrieved header information will be stored in the `headers` field. If you select this option, you need to make sure the last field in the schema is named `headers` and has a String type. You can add the `headers` field manually in the Schema field.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!