Question on external modules

Highlighted
Six Stars

Question on external modules

I have a question on using custom components.

 

Let's say I install the Amazon Redshift JDBC driver (which does not ship with Talend Studio by default). I then use the tRedshiftRow component in one of my jobs. When I deploy the job, do I also need to make sure that the Amazon Redshift JDBC driver is installed on the server too? Or is it included in the Talend job when I deploy it?

 

I an a Talend newbie and I am in the process of researching various scenarios.

 

Thank you.

Highlighted
Moderator

Re: Question on external modules

Hi,

Which server do you want to use? Nexus server or job conductor?

If you publish the job script from studio to nexus server, the dependency custom component will be export also. In Job conductor, add tasks from nexus.

You add custom components to a local folder first. Then, you point Studio to that folder via Window/Preferences/Talend/Components -> User component folder. Here's where you set the path to your user component folder. Once you build the job, the required code is included in the archive file. Up to this point, Nexus has nothing to do with that, it is only involved in storing the job builds. 

When commandline runs on a seperate (remote) machine, you need to make sure that the custom components are shared  across the project.

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

2019 GARTNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog