Skip to main content
Announcements
Qlik Connect 2025! Join us in Orlando join us for 3 days of immersive learning: REGISTER TODAY

Qlik Talend and Camel 4: Migrating routes leveraging Camel RabbitMQ (from cMessagingEndpoint to cRabbitMQ)

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
DenisSergent
Employee

Qlik Talend and Camel 4: Migrating routes leveraging Camel RabbitMQ (from cMessagingEndpoint to cRabbitMQ)

Last Update:

Mar 12, 2025 6:01:58 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 12, 2025 6:01:58 AM

When migrating Camel 3 projects that use the camel-rabbitmq library to interact with RabbitMQ, several important changes in components, dependencies structure and connection configuration must be considered. The primary change involves shifting from the native camel-rabbitmq component to the spring-rabbitmq component, as well as updating the connection configuration approach.

This article outlines all the necessary steps to successfully migrate projects that use the cMessagingEndpoint component with RabbitMQ.

Changes in Talend Studio that were made

  • A new component, cRabbitMQ, has been added. This component must now be used in all Talend Studio routes to produce or consume messages from RabbitMQ.
  • Additionally, a new type of configuration has been introduced in the cMQConnectionFactory component: MQ Server = RabbitMQ. This configuration is used to set up connections to RabbitMQ for any cRabbitMQ component.
  • In Camel 4, the camel-rabbitmq dependency has been removed and replaced by the dependency for the new spring-rabbitmq component. This dependency is automatically added when the new component is used.

How to Migrate from cMessagingEndpoint with camel-rabbitmq to the New cRabbitMQ Component

  1. The first step in the migration process is to replace the cMessagingEndpoint component (Fig. 1) with the new cRabbitMQ component (Fig. 2) in your project.
    The cRabbitMQ component has two base parameters: Exchange Name and Connection Factory.
  2. The URI is now constructed based on Connection Factory properties and the values provided in the Advanced Settings of cRabbitMQ. Any additional needed options you can add in  Advanced Settings

    Now generated URI for the cRabbitMQ component will start from “spring-rabbitmq:” instead of “rabbitmq:” that it was in cMessagingEndpoint.

    Figure 1 - Old approach that used cMessagingEndpointFigure 1 - Old approach that used cMessagingEndpoint

    Figure 2 - New approach that uses cRabbitMQ and cMQConnectionFactory componentsFigure 2 - New approach that uses cRabbitMQ and cMQConnectionFactory components

  3. Since cRabbitMQ uses the cMQConnectionFactory component for connection setup, you will also need to add this component. In its settings, specify the MQ Server type as RabbitMQ, and provide your connection parameters: Host name, Port, Virtual host, as well as authentication parameters or SSL settings if necessary.

    Figure 3 - Example of cMQConnectionFactory settingsFigure 3 - Example of cMQConnectionFactory settings

  4. With the transition to the spring-rabbitmq component in Camel 4, there may be some changes in the format and support for certain parameters. For up-to-date information on the parameters supported in Camel 4, it is recommended to refer to the official Spring RabbitMQ component documentation: https://camel.apache.org/components/4.8.x/spring-rabbitmq-component.html

Related Content

 

Labels (1)