Qlik Talend ESB: How to manage Routines with complex jar dependencies

wei_guo — Mon, 09 Mar 2026 07:28:38 GMT

Having complex JAR dependencies and organizing them through Global Routines in the Code > Routine design can lead to JAR conflicts. Different job types may require incompatible library versions. For instance, a DI OSGi web service implementation might need different JAR dependencies than a standard DI job, causing conflicts when both rely on the same Global Routine.

Resolution

Use a Custom Routine. Qlik Talend Studio enables you to create custom routine JARs with explicit dependency management at the Job and Joblet level.

Benefits of Custom Routine JARs:

Encapsulation: Package multiple user routines with their specific dependencies into a single archive
Explicit Dependencies: Jobs and Joblets declare their exact code dependencies, making the dependency chain transparent
Conflict Resolution: Isolating dependencies per custom routine JAR reduces the risk of version conflicts between different job types
Implementation: By configuring custom routine JAR dependencies directly on Jobs and Joblets rather than relying on shared Global Routines, each component can maintain its own compatible dependency set without interfering with other jobs' requirements.

For information on how to set up custom routine JARs, see Creating custom routine JARs.

Environment

Qlik Talend ESB

article Qlik Talend ESB: How to manage Routines with complex jar dependencies in Official Support Articles

Qlik Talend ESB: How to manage Routines with complex jar dependencies

Resolution

Environment