Skip to main content Skip to complementary content
Announcements

Configuring the first sub-route

Procedure

  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("\r\n") to split the message in each row into sub-messages.
    Information noteNote:

    This piece of code is for Windows only. For Unix, change it to body(String.class).tokenize("\n"), and for Mac, body(String.class).tokenize("\r").

  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.

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 – let us know how we can improve!

Leave your feedback here