Skip to main content Skip to complementary content

cMessagingEndpoint Standard properties

These properties are used to configure cMessagingEndpoint running in the Standard Job framework.

The Standard cMessagingEndpoint component belongs to the Core family.

Basic settings


URI of the messages to send or receive. It can be of different format:

-File: "file:/",

-Database: "jdbc:/",

-Protocols: "ftp:/", "http:/"


You can add parameters to the URI using the generic URI syntax, for example:


For more information on the different components that can be used in cMessagingEndpoint, see Apache Camel's Website:
Information noteNote: If you have installed the R2023-08 Talend Studio Monthly update or a later one delivered by Talend, the operationName is mandatory in Salesforce URI. All consumer URIs now use the subscribe operation. For example:
  • salesforce:subscribe:<topic_name>,
  • salesforce:subscribe:event/<event_name>
  • salesforce:subscribe:data/ChangeEvents

Advanced settings


By default, the camel core supports the following components: bean, browse, class, dataset, direct, file, language, log, mock, properties, ref, seda, timer, vm.

To use other components, you have to provide the dependencies corresponding to those components in the cMessagingEndpoint component. To do so:

Click the plus button to add new lines in the Camel component list. In the line added, select the component you want to use in cMessagingEndpoint. For more information about the commonly used Camel components, see Commonly used Camel components.
Information noteNote: To work with Apache ActiveMQ, you can add camel-activemq in the Camel component list without selecting the Use a custom component check box.

Use a custom component

If you want to use a custom component, select this check box and click the [...] button to upload a jar file with your own component.

Information noteNote:

All the transitive dependencies of this custom component should be included in the jar file.


Usage rule

This component can be used as sending and/or receiving message endpoint according to its position in the Route.



Did this page help you?

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