August 17, 2023

Talend ESB Mediation Components – Docs for ESB 5.x

Talend ESB Mediation Components

Reference Guide

5.6.3

Adapted for v5.6.3. Supersedes previous
releases.

February 2, 2016

Copyright © 2011-2016 Talend Inc. All rights reserved.

Copyleft

This documentation is provided under the terms of the Creative Commons Public
License (CCPL).

For more information about what you can and cannot do with this documentation in
accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/

Notices

Talend and Talend ESB are trademarks of Talend, Inc.

Apache CXF, CXF, Apache Karaf, Karaf, Apache Cellar, Cellar, Apache Camel, Camel,
Apache Maven, Maven, Apache Archiva, Archiva, Apache Syncope, Syncope, Apache
ActiveMQ, ActiveMQ, Apache Log4j, Log4j, Apache Felix, Felix, Apache ServiceMix,
ServiceMix, Apache Ant, Ant, Apache Derby, Derby, Apache Tomcat, Tomcat, Apache
ZooKeeper, ZooKeeper, Apache Jackrabbit, Jackrabbit, Apache Santuario, Santuario,
Apache DS, DS, Apache Avro, Avro, Apache Abdera, Abdera, Apache Chemistry,
Chemistry, Apache CouchDB, CouchDB, Apache Kafka, Kafka, Apache Lucene, Lucene,
Apache MINA, MINA, Apache Velocity, Velocity, Apache FOP, FOP, Apache HBase, HBase,
Apache Hadoop, Hadoop, Apache Shiro, Shiro, Apache Axiom, Axiom, Apache Neethi,
Neethi, Apache WSS4J, WSS4J are trademarks of The Apache Foundation. Eclipse Equinox
is a trademark of the Eclipse Foundation, Inc. SoapUI is a trademark of SmartBear
Software. Hyperic is a trademark of VMware, Inc. Nagios is a trademark of Nagios
Enterprises, LLC.

All other brands, product names, company names, trademarks and service marks are
the properties of their respective owners.

This product includes software developed at AOP
Alliance (Java/J2EE AOP standards), ASM, AntlR, Apache ActiveMQ, Apache Ant, Apache Avro,
Apache Axiom, Apache Axis, Apache Axis 2, Apache Batik, Apache CXF, Apache Camel, Apache
Chemistry, Apache Common Http Client, Apache Common Http Core, Apache Commons, Apache
Commons Bcel, Apache Commons JxPath, Apache Commons Lang, Apache Derby Database Engine and
Embedded JDBC Driver, Apache Geronimo, Apache Hadoop, Apache Hive, Apache HttpClient, Apache
HttpComponents Client, Apache JAMES, Apache Log4j, Apache Lucene Core, Apache Neethi, Apache
POI, Apache Pig, Apache Qpid-Jms, Apache Tomcat, Apache Velocity, Apache WSS4J, Apache
WebServices Common Utilities, Apache Xml-RPC, Apache Zookeeper, Box Java SDK (V2), CSV
Tools, DataStax Java Driver for Apache Cassandra, Ehcache, Ezmorph, Ganymed SSH-2 for Java,
Google APIs Client Library for Java, Google Gson, Groovy, Guava: Google Core Libraries for
Java, H2 Embedded Database and JDBC Driver, HsqlDB, Ini4j, JClouds, JLine, JSON, JSR 305:
Annotations for Software Defect Detection in Java, JUnit, Jackson Java JSON-processor, Java
API for RESTful Services, Jaxb, Jaxen, Jettison, Jetty, Joda-Time, Json Simple, MetaStuff,
Mondrian, OpenSAML, Paraccel JDBC Driver, PostgreSQL JDBC Driver, Resty: A simple HTTP REST
client for Java, Rocoto, SL4J: Simple Logging Facade for Java, SQLite JDBC Driver, Simple
API for CSS, SshJ, StAX API, StAXON – JSON via StAX, Talend Camel Dependencies (Talend), The
Castor Project, The Legion of the Bouncy Castle, W3C, Woden, Woodstox : High-performance XML
processor, XML Pull Parser (XPP), Xalan-J, Xerces2, XmlBeans, XmlSchema Core, Xmlsec –
Apache Santuario, Zip4J, atinject, dropbox-sdk-java: Java library for the Dropbox Core API,
google-guice. Licensed under their respective license.


1. Context components
cBeanRegister
cBeanRegister properties
Related Scenario
cConfig
cConfig properties
Scenario: Implementing a dataset from the Registry
cMQConnectionFactory
cMQConnectionFactory properties
Related scenario:
2. Exception components
cErrorHandler
cErrorHandler properties
Scenario: Logging the exception thrown during a client/server talk
cIntercept
cIntercept properties
Scenario: Intercepting several routes and redirect them in a single new route
cOnException
cOnException properties
Scenario: Using cOnException to ignore exceptions and continue message
routing
cTry
cTry properties
Scenario: Using cTry to build Try/Catch/Finally blocks for exception handling
3. Messaging components
cAMQP
cAMQP properties
Scenario: Sending messages to and receiving messages from an AMQP broker
cCXF
cCXF properties
Scenario 1: Providing a Web service using cCXF from a WSDL file
Scenario 2: Providing a Web service using cCXF from a Java class
Scenario 3: Providing a Web service from a Route Resource
cCXFRS
cCXFRS properties
Scenario: Providing and consuming a REST service using cCXFRS
cDataset
cDataset properties
Scenario: Using cDataset to receive messages
cDirect
cDirect properties
Related scenario:
cDirectVM
cDirectVM properties
Scenario: Direct and synchronous messaging within the same JVM
cFile
cFile properties
Scenario: Reading files from one directory and writing them to another
cFtp
cFtp properties
Related scenario:
cHttp
cHttp properties
Scenario 1: Retrieving the content of a remote file
Scenario 2: Using cHttp to produce a Web service
cJMS
cJMS properties
Scenario 1: Sending and receiving a message from a JMS queue
Scenario 2: Setting up a JMS local transaction
Scenario 3: Sending and receiving a scheduled delivery of messages from a JMS Queue
using Camel Quartz
cMail
cMail Properties
Scenario: Using cMail to send and receive
mails
cMessagingEndpoint
cMessagingEndpoint properties
Commonly used Camel components
Scenario 1: Moving files from one message endpoint to another
Scenario 2: Sending files to another message endpoint
Scenario 3: Using an Xquery endpoint to filter messages
cMQTT
cMQTT properties
Scenario: Sending messages to and receiving messages from an MQTT broker
cSEDA
cSEDA properties
Scenario: Using cSEDA, cVM and cDirect to produce and consume messages
separately
cTimer
cTimer properties
Related Scenario:
cVM
cVM properties
Related scenario:
4. Miscellaneous components
cLog
cLog properties
Related scenario:
cLoop
cLoop properties
Related scenario:
cStop
cStop properties
Related scenario:
5. Processor components
cBean
cBean properties
Related Scenario
cDelayer
cDelayer properties
Scenario: Using cDelayer to delay message routing
cExchangePattern
cExchangePattern properties
Scenario: Enabling the InOut exchange pattern to get replies
cJavaDSLProcessor
cJavaDSLProcessor properties
Related scenario:
cProcessor
cProcessor properties
Related scenario:
cTalendJob
cTalendJob properties
Scenario: Using cTalendJob to call a DI Job
6. Routing components
cAggregate
cAggregate
Scenario: Aggregating three messages into one
cDynamicRouter
cDynamicRouter properties
Scenario: Routing files conditionally to different file paths
cIdempotentConsumer
cIdempotentConsumer properties
Scenario: Deduplicating messages while routing them
cLoadBalancer
cLoadBalancer properties
Scenario: Distributing messages to receiver endpoints based on round robin
cMessageFilter
cMessageFilter properties
Scenario: Filtering messages according to a criterion
cMessageRouter
cMessageRouter properties
Scenario: Routing messages according to a criterion
cMulticast
cMulticast properties
Scenario: Route a message to multiple endpoints and set a new body for each
cPipesAndFilters
cPipesAndFilters properties
Scenario: Using cPipesAndFilters to process the task in sequence
cRecipientList
cRecipientList properties
Scenario: Routing a message to multiple recipients
cRoutingSlip
cRoutingSlip properties
Scenario 1: Routing a message consecutively to a series of endpoints
Scenario 2: Routing each message conditionally to a series of endpoints
cSplitter
cSplitter properties
Scenario: Using cSplitter to split a message and aggregate replies from
sub-messages
cThrottler
cThrottler properties
Scenario: Throttling the message flow
Viewing the code and executing the Route
cWireTap
cWireTap properties
Scenario: Wiretapping a message in a Route
7. Transformation components
cContentEnricher
cContentEnricher properties
Scenario: Receiving messages from a list of URLs
cConvertBodyTo
cConvertBodyTo properties
Scenario: Converting the body of an XML file into an
org.w3c.dom.Document.class
cMap
cMap properties
Scenario: Mapping data with cMap
cSetBody
cSetBody properties
Scenario: Replacing the content of messages with their extracts
cSetHeader
cSetHeader properties
Scenario: Splitting a message and renaming the sub-messages according to contained
information
Related scenarios

Document get from Talend https://help.talend.com
Thank you for watching.
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x