Skip to main content

Using cSEDA, cVM and cDirect to produce and consume messages separately

This scenario applies only to Talend ESB, Talend Data Services Platform, Talend MDM Platform, Talend Real-Time Big Data Platform, and Talend Data Fabric.

In this scenario, we will use a cTimer component to trigger a message exchange. The message is routed to a cSEDA, a cVM and a cDirect sequentially with a message body set for each of them, which is then consumed in another thread.

We will create a Route Resource to define the repeat count of the message exchange (the number of times the message should be sent), which will be used by the cTimer component.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!