cMessagingEndpoint Standard properties - 7.3

Messaging Endpoint (Mediation)

Version
7.3
Language
English (United States)
Product
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Routing components (Mediation) > Messaging Endpoint components (Mediation)
Data Quality and Preparation > Third-party systems > Routing components (Mediation) > Messaging Endpoint components (Mediation)
Design and Development > Third-party systems > Routing components (Mediation) > Messaging Endpoint components (Mediation)

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

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

-File: "file:/",

-Database: "jdbc:/",

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

-etc.

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

"file:/directoryName?option=value&option=value"

For more information on the different components that can be used in cMessagingEndpoint, see Apache Camel's Website: http://camel.apache.org/components.html.

Advanced settings

Dependencies

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.

Use a custom component

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

Note:

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

Usage

Usage rule

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

Limitation

 n/a