Using the RabbitMQ Destination Component

The RabbitMQ Destination Component is an SSIS data flow pipeline component that can be used to send messages to a RabbitMQ Server. There are three pages of configuration:

  • General
  • Columns
  • Error Handling

General page

RabbitMQ SSIS Destination Component

Connection Manager

The destination component requires a RabbitMQ connection manager. The Connection Manager drop-down will show a list of all the RabbitMQ connection managers that have been created in the current SSIS package.

Exchange Name

The name of the exchange to send messages to.

Routing Key

The routing key of sent messages.

Delivery Mode

The delivery mode can be set to Persistent or Non-Persistent.

  • Persistent: Messages are stored on disk on the server, and will persist after a server restart.
  • Non-Persistent: Messages are only stored in memory.
Priority

The priority of sent messages. The possible range is 0 to 255.

Body Column Type (since v6.2)

The Body Column Type allows you to specify whether you want to write the binary content of the message or the text content of the message to RabbitMQ. There are two different modes available for Body column types: Binary and Text. The default setting is Text. 

Encoding

The encoding that will be used to convert the message body to a byte array when sending the text message. This option is only available when Body Column Type is Text.

Refresh Component Button

Clicking the Refresh Component button causes the component to retrieve the latest metadata and update each field to its most recent metadata. It will remove any custom fields that have been added on the columns page.

Map Unmapped Fields Button

By clicking this button, the component will try to map any unmapped attributes by matching their names with the input columns from upstream components. This is useful when your source component has recently added more columns, in which case you can use this button to automatically establish the association between input columns and unmapped destination attributes.

Clear All Mappings Button 

By clicking this button, the component will reset all your mappings in the destination component.

Expression fx Icon

Click the blue fx icon to launch SSIS Expression Editor to enable dynamic update of the property at run time.

Generate Documentation Icon

Click the Generate Documentation icon to generate a Word document which describes the component's metadata including relevant mapping, and so on.

Columns page

The Columns page allows you to map the columns from upstream components to destination attributes.

In the Columns page, you will see a grid as shown below.

RabbitMQ SSIS Destination Component - Columns

  • Input Column: You can select an input column from an upstream component here. 
  • Destination Field: The attribute/field that you want to write data to. 
  • Data Type: This column indicates the type of value for the current attribute. 
  • Unmap: This button provides a convenient way to unset the mapping for the selected attribute/field. 
Add Button
Clicking the Add button will bring up a dialog that will allow columns to be added that correspond to custom headers on outgoing messages.

Error Handling page 

The Error Handling page allows you to specify how errors should be handled when they happen. 

RabbitMQ SSIS Destination Component - Error Handling

There are three options available:

  1. Fail on error
  2. Redirect rows to error output
  3. Ignore error

When the Redirect rows to error output option is selected, rows that failed to write to RabbitMQ will be redirected to the 'Error Output' of the Destination Component. As indicated in the screenshot below, the green output connection represent rows that were successfully written, and the red 'Error Output' connection represents rows that were erroneous. The 'RabbitMQErrorMessage' output column found in the 'Error Output' may contain the error message that was reported by RabbitMQ or the component itself.

RabbitMQ Error Output

Note: Use extra caution when selecting Ignore error option, since the component will remain silent for any errors that have occurred.