Skip to main content Skip to complementary content

Creating custom routine JARs

Talend Studio allows you to create custom routine JARs and set up custom routine JAR dependencies on Jobs and Joblets.

The custom routine JAR allows you to package multiple user routines with their dependencies into a single archive. By setting up custom routine JAR dependencies on Jobs and Joblets, the code dependencies for Jobs and Joblets become more explicit and this can help reduce dependency conflicts.

About this task

To create a custom routine JAR:

Procedure

  1. In the Repository tree view, right-click Code > Custom Routine Jars and select Create Routine Jar from the contextual menu.
    The New Routine Jar dialog box is displayed.
  2. Fill in the generic properties such as Name, Purpose (optional), and Description (optional).
    The information you fill in the Description field will appear as a tooltip when your mouse pointer is moved over the custom routine JAR in the Repository tree view.
  3. Click Finish to save the new custom routine JAR.
    The newly added custom routine JAR is displayed under the Custom Routine Jars node.

    Now you can create inner routines and add them into the new custom routine JAR by right-clicking it and selecting Create routine from the contextual menu. For more information, see Creating user routines.

    You can add any existing global user routine into a custom routine JAR by right-clicking the global user routine and selecting Copy Routine to... from the contextual menu.

    Information noteNote: A global user routine will be kept as a global one after being copied into a custom routine JAR.

    If you have installed the 8.0 R2023-01 Talend Studio monthly update or a later one provided by Talend, you can rename a custom routine JAR or an inner routine by right-clicking it, selecting Edit properties from the contextual menu, and then editing its name in the dialog box displayed.

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