Menu
They seem to be doing more or less the same thing - taking data, processing it and sending it out.
Internet search results show that Talend Routes are almost the same as Camel Routes, but that does not say anything about what they are and how are they different from Jobs.
What are the Routes and Jobs in Talend ESB? What is the difference between them? When to prefer one over the other?
515
Talend Routes are geared towards web services and messaging system communications, and utilizes the features of Apache Camel as part of its feature set.
In this design, one or more components are connected with each other to run a data integration process. Thus, when you drag and drop components in the design pane and connect then with connectors, a job design converts everything to code and creates a complete runnable program which forms the data flow.
Procedure. Drag and drop a cFile, a cConvertBodyTo, a cMessageFilter and a cMessagingEndpoint from the Palette onto the design workspace. Label the components for better identification of their roles. Link the cMessageFilter component and the cMessagingEndpoint component using the Row > filter connection.
Right-click the Job you want to build in the Repository view. Select Build Job to open the [Build Job] dialog box. In the To archive file field, browse to the directory where you want to save your built Job. From the build type list, select the Standalone Job.
The main difference between Talend routes and jobs is that when you start a route, it listens indefinitely for input (file, message..etc), and whenever it is available it is processed and sent to destination ,until the route is stopped. On the other hand, a job is a batch process that is launched on demand to handle some input (files, database..etc) and ends when all input is processed.
115
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
