Skip to main content Skip to complementary content

How to define connection settings of a Route

You can display the properties of a connection by selecting it and clicking the Component view tab, or by right-clicking the connection and selecting Settings from the contextual menu. This section summarizes connection property settings.

Catch connection settings

About this task

You can set a Catch link to catch the exception thrown by the try link of the cTry component.

Procedure

  1. Simply select the Catch link of your Route to display the related Basic settings view of the Components tab.
  2. In the Exceptions field, type in the name of the exception class that is likely to occur in the try routing. If you type in java.lang.Exception.class, mother of all exceptions, any exception will be caught. But you can try to fine-tune the exception generated by specifying a more precise exception class.
    Basic settings view.

Results

When executing your Route, if an exception occurs in routing following a try link, it will be caught by the catch link corresponding better to the exception. For more information, see Row connection.

When connection settings

About this task

You can set a When link to filter messages according to a condition and route those filtered messages:

Procedure

  1. Simply select the When link of your routing to display the related Basic settings view of the Components tab.
  2. In the Type list, select the type of condition you want to use in the routing.
  3. In the Condition field, type in the condition you want to use to filter your messages.
    Basic settings view.

Results

When executing your Route, messages matching the condition defined in the when link will be passed to the following component and messages not matching it can either be lost or retrieved via an otherwise link. For more information, see Catch connection settings and for a scenario using those links, see Talend Components documentation.

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!