August 15, 2023

cContentEnricher – Docs for ESB 6.x

  2. Talend for ESB Docs
  3. Docs 6.x
  4. cContentEnricher – Docs for ESB 6.x

cContentEnricher

Uses a consumer or producer to obtain additional data, respectively intended for
event messaging and request/reply messaging.

cContentEnricher Standard properties

These properties are used to configure cContentEnricher running in the Standard Job framework.

The Standard
cContentEnricher component belongs to the Transformation family.

Basic settings

Resource URI

This refers to the destination to which a message will be
delivered if using a producer is
selected; it refers to the source from which a message will be
obtained if using a consumer is
selected.

Using a producer

Select this check box to use a producer to provide additional data, that is to say
sending a message to the defined URI.

Using a consumer

Select this check box to use a consumer to obtain additional data, that is to say
requesting a message from the defined URI.

Use Aggregation Strategy

Select this check box to define the aggregation strategy for
assembling the basic message and the additional data.

Specify timeout

This area appears when Using a
consumer is selected. The timeout options are as
follows:

Wait until a message arrive: the
component keeps waiting for a message.

Immediately polls the message:
the component immediately polls from the defined URI.

Waiting at most until the timeout
triggers: select this check box to type in a timeout
value in Millis. The component waits for the message only within the
defined time period.

Usage

Usage rule

cContentEnricher allows you to use
a consumer or producer to obtain additional data, respectively
intended for event message messaging and request/reply
messaging.

Limitation

 n/a

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 a list of URLs and
send the messages to the local file system, the other to retrieve the messages on these
URLs.

In this use case, we will take a list of URLs on the local Tomcat server as the
example. So we need to start Apache Tomcat before executing the Route.

A TXT file URLlist is used to provide the list of URLs, as shown
below.

use_case-ccontentenricher1.png

Dropping and linking the components

  1. From the Palette, drag and drop a
    cSplitter, a cJavaDSLProcessor, a cContentEnricher, two cFile, two cMessagingEndpoint,
    and three cSetHeader components onto the
    design workspace.
  2. Label the components properly for better identification of their roles and
    link them using the Row > Route connection as shown above.

Configuring the components

Press Ctrl+S to save your Route.

Configuring the first sub-route

  1. Double-click the URLlist component to
    display its Basic settings view in the
    Component tab.

    use_case-ccontentenricher2.png

  2. In the Path field, browse to the file
    path where the URL list file is saved.

    In the FileName field, enter the filename
    URLlist.txt.
  3. Double-click the cSplitter component to
    display its Basic settings view in the
    Component tab.

    use_case-ccontentenricher3.png

  4. Select None in the Language list. In the Expression field, enter the code
    body(String.class).tokenize("
    ")     to split the message in
    each row into sub-messages.

    Note:

    Note that this piece of code is for Windows only. For Unix, change it
    to body(String.class).tokenize("
    ")    , and for Mac,
    body(String.class).tokenize("
    ")    .

  5. Double-click the cJavaDSLProcessor component to display its Basic settings view in the Component tab.

    use_case-ccontentenricher4.png

  6. In the Code area, enter the code
    .log("splitterOutput: ${body}") to get the split message
    body.
  7. Double-click the cContentEnricher component display its Basic settings view in the Component tab.

    use_case-ccontentenricher5.png

  8. Select using a producer to use a producer
    to provide additional data and send the message to a defined URI.

    In the Resource URI field, enter
    "direct:fetchURL" where the message will be delivered.
  9. Double-click the setFileName
    component to display its Basic settings
    view in the Component tab.

    use_case-ccontentenricher6.png

  10. Click [+] to add a row to the Headers table.

    In the Name field, enter
    org.apache.camel.Exchange.FILE_NAME to define the file name
    for each incoming message.
    Select Simple in the Language list.
    In the Value field, enter
    "${header.CamelHttpPath}" to get the URI’s path of the
    incoming message.
  11. Double-click the retrievedFiles component
    to display its Basic settings view in the
    Component tab.

    use_case-ccontentenricher7.png

  12. In the Path field, browse to the
    destination file path where you want the messages to be saved.

Configuring the second sub-route

  1. Double-click the fetchURL component to
    display its Basic settings view in the
    Component tab.

    use_case-ccontentenricher8.png

  2. In the URI field, enter “direct:fetchURL” that is defined in the
    cContentEnricher component.
  3. Double-click the setURI
    component to display its Basic settings
    view in the Component tab.

    use_case-ccontentenricher9.png

  4. Click [+] to add a row to the Headers table.

    In the Name field, enter
    org.apache.camel.Exchange.HTTP_URI to define the HTTP URI
    of each message.
    Select Simple in the Language list.
    In the Value field, enter
    "http://localhost:8080" of the local Tomcat server.
  5. Double-click the setPATH
    component to display its Basic settings
    view in the Component tab.

    use_case-ccontentenricher10.png

  6. Click [+] to add a row to the Headers table.

    In the Name field, enter
    org.apache.camel.Exchange.HTTP_PATH to define the HTTP path
    of each message.
    Select Simple in the Language list.
    In the Value field, enter
    "${body}" that is split from the original message.
  7. Double-click the http4Endpoint component
    to display its Basic settings view in the
    Component tab.

    use_case-ccontentenricher11.png

  8. In the URI field, enter “http4:localhost:8080” to consuming HTTP
    resources on the local Tomcat server.
  9. Click the Advanced settings view. Click

    plus_button.png

    at the bottom of the Dependencies list to add a row and select http4
    from the drop-down list. For more information about HTTP4, see the site
    http://camel.apache.org/http4.html.

    use_case-ccontentenricher13.png

Viewing code and executing the Route

  1. Click the Code tab at the bottom of the
    design workspace to have a look at the generated code.

    use_case-ccontentenricher12.png

    As shown above, a message route is built from the URLlist to
    the retrievedFiles via the .split,
    .log, .enrich, and .setHeader.
    The other message route is built from fetchURL to
    http4Endpoint via two .setHeader.
  2. Press F6 to execute the Route.

    RESULT: The split message is printed on the Run console.
    use_case-ccontentenricher14.png

    The messages from the list of URLs are saved in defined directory of the
    local file system.
    use_case-ccontentenricher15.png

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