Skip to main content Skip to complementary content

Setting up code dependencies on a Route

If you want to enable your Route to call any function in a custom Bean jar, routine, or custom routine jar, you need to set up code dependencies, namely custom Bean jar, routine, or custom routine jar dependencies, on the Route.

For more information about custom Bean jars, routines, and custom routine jars, see Creating a custom Bean Jar, What are routines and Creating custom routine JARs.

Procedure

  1. In the Repository tree view, right-click the Route and select Setup Codes Dependencies from the contextual menu. Otherwise, select Setup routine dependencies.
    The Setup Codes Dependencies window is displayed. You can set up custom Bean jar, custom routine jar and global routine dependencies on the Route on the corresponding tab. By default, all system routines are automatically set as dependencies for Routes.
    Setup Codes Dependencies dialog box.
  2. Click the [+] button on a tab if you need to set up the corresponding dependencies on the Route.
    A dialog box is displayed, which lists all the corresponding custom Bean jars, routines, or custom routines jars.
  3. Select one or more custom Bean jars, routines, or custom routine jars containing the functions that your Route calls.
  4. Click OK to save your changes and close the dialog box.

    When a custom Bean jar, routine, or a custom routine jar does not contain any function that your Route calls, you can remove it by selecting it on the tab and then clicking the [x] button. This helps avoid redundancy in the exported dependencies.

    Information noteTip: You can right-click a custom Bean jar, routine, or a custom routine jar to use the Impact Analysis feature. This feature indicates which Routes use the custom Bean jar, routine, or the custom routine jar and would therefore be impacted by any modification. For further information about Impact Analysis, see Analyzing repository items.

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!

Leave your feedback here