Scenario: Replacing the content of messages with their extracts – Docs for ESB 6.x
Scenario: Replacing the content of messages with their extracts This scenario applies only to a Talend solution with ESB. In this scenario, file messages are routed from one endpoint to another, with the content of each message replaced with the information extracted from it. The following is an example of the XML files used in…
Scenario: Route a message to multiple endpoints and set a new body for each – Docs for ESB 6.x
Scenario: Route a message to multiple endpoints and set a new body for each This scenario applies only to a Talend solution with ESB. In this scenario, a cMulticast component is used to route a message to two endpoints. The source message and the message on each endpoint is then set a new body. The…
Scenario: Routing a message to multiple recipients – Docs for ESB 6.x
Scenario: Routing a message to multiple recipients This scenario applies only to a Talend solution with ESB. In this scenario, a cRecipientList component is used to route a message to a list of recipients. To build the Route, do the following. Document get from Talend https://help.talend.com Thank you for watching.
Scenario: Parsing delimited file using the cFlatPack component – Docs for ESB 6.x
Scenario: Parsing delimited file using the cFlatPack component This scenario applies only to a Talend solution with ESB. In this scenario, a cFile component reads a delimited file from the local file system, which contains the customers information including id, first name, surname, and order id, as shown below:
|
1 2 3 4 5 |
1,"Harry",Carter,21 2,Padre,Boulevard,22 3,Andrew,Polk,23 4,Herbert,Reagan,"24" 5,Chester,Eisenhower,25 |
The file is parsed by…
Scenario: Providing and consuming a REST service using cREST – Docs for ESB 6.x
Scenario: Providing and consuming a REST service using cREST This scenario applies only to a Talend solution with ESB. This scenario demonstrates how to use the cREST component to provide and consume a REST service. To do so, two Routes are built, a service provider Route and a consumer Route. The service provider Route will…
Scenario: Reading files from one directory and writing them to another – Docs for ESB 6.x
Scenario: Reading files from one directory and writing them to another This scenario applies only to a Talend solution with ESB. In this scenario, an input cFile component is configured to visit a local file directory and send the files in the directory to an output cFile component which writes the files in another directory….
Scenario: Receiving messages from a list of URLs – Docs for ESB 6.x
Scenario: Receiving messages from a list of URLs This scenario applies only to a Talend solution with ESB. In this scenario, we will use the Camel component HTTP4 and the cContentEnricher component to retrieve messages from a list of URLs. To do this, we need to build two sub-routes, one to read a file with…
Scenario: Sending messages to and receiving messages from Amazon’s S3 service – Docs for ESB 6.x
Scenario: Sending messages to and receiving messages from Amazon’s S3 service This scenario applies only to a Talend solution with ESB. This scenario will show you how to use the cAWSS3 component to send messages to and consume messages from Amazon’s S3 service. To do this, two Routes are built, a message producer Route, and…
Scenario: Sending messages to and receiving messages from Amazon’s SQS queue – Docs for ESB 6.x
Scenario: Sending messages to and receiving messages from Amazon’s SQS queue This scenario applies only to a Talend solution with ESB. This scenario will show you how to use the cAWSSQS component to send messages to and consume messages from an SQS queue. To do this, two Routes are built, a message producer Route, and…
Scenario: Sending messages to and receiving messages from an AMQP broker – Docs for ESB 6.x
Scenario: Sending messages to and receiving messages from an AMQP broker This scenario applies only to a Talend solution with ESB. This scenario will show you how to use the cAMQP component to send messages to and consume messages from a JMS Queue or Topic. To do this, two Routes are built, a message producer…