cContentEnricher – Docs for ESB 5.x

cContentEnricher

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 first sub-route

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

   

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.

   

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.

   

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.

   

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.

   

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.

    

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.

   

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.

   

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.

   

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.

   

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 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.

   

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

   

   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.

   

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