# cMessagingEndpoint

Allows two applications to communicate by either sending or receiving messages.

For more information, see the Apache camel documentation https://camel.apache.org/components/latest/.

## 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

| Properties | Description |
| --- | --- |
| URI | URI of the messages to send or receive. It can be of different<br>format:<br><br>-File: "file:/",<br><br>-Database: "jdbc:/",<br><br>-Protocols: "ftp:/", "http:/"<br><br>-etc.<br><br>You can add parameters to the URI using the generic URI syntax,<br>for example:<br><br><br>"file:/directoryName?option=value&option=value"<br><br>For more information on the different components that can be used<br>in cMessagingEndpoint, see Apache Camel's Website: http://camel.apache.org/components.html.<br><br>Information noteNote: If you<br>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<br>use the subscribe operation. For example:<br><br><ul> <li> <span>salesforce:subscribe:&lt;topic_name&gt;</span>, </li> <li> <span>salesforce:subscribe:event/&lt;event_name&gt;</span> </li> <li> <span>salesforce:subscribe:data/ChangeEvents</span> </li> </ul> |

## Advanced settings

| Properties | Description |
| --- | --- |
| Dependencies | By default, the camel core supports the following components:<br>bean, browse, class, dataset, direct, file, language, log, mock,<br>properties, ref, seda, timer, vm.<br><br>To use other components, you have to provide the dependencies<br>corresponding to those components in the cMessagingEndpoint component. To do so:<br><br>Click the plus button to add new lines in the Camel component list. In the line added, select<br>the component you want to use in cMessagingEndpoint. For more information about the commonly<br>used Camel components, see [Commonly used Camel components](https://help.qlik.com/talend/en-US/components/8.0/mediation-messaging-endpoint/cmessagingendpoint-cmessagingendpoint-commonly-used-camel-components).<br><br>Information noteNote: To work with Apache ActiveMQ, you can add<br>camel-activemq in the Camel<br>component list without selecting the Use a custom<br>component check box. |
| Use a custom component | If you want to use a custom component, select this check box and<br>click the [...] button to upload a jar file with your<br>own component.<br><br>Information noteNote:<br><br>All the transitive dependencies of this custom component<br>should be included in the jar file. |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component can be used as sending and/or receiving message<br>endpoint according to its position in the Route. |
| Limitation | n/a |

**Related concepts**

* [Moving files from one message endpoint to another](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-messaging-endpoint/cmessagingendpoint-moving-files-from-one-message-endpoint-to-another)
* [Sending files to another message endpoint](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-messaging-endpoint/cmessagingendpoint-sending-files-to-another-message-endpoint)
* [Using an XQuery endpoint to filter messages](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-messaging-endpoint/cmessagingendpoint-cprocessor-cfile-cfile-using-xquery-endpoint-to-filter-messages)