Deciphering Talend Installation

[Anonymous]

Greetings. Our Company has a Talend Installation setup on Linux VM's and unfortunately the person who set it up has left and there is minimal documentation. I have no familiarity with this tool and am trying to understand what we have and how to maintain and use it. I have a few very basic questions and would appreciate some direction.

The Talend System (v. 6.4) is embedded into a Jaspersoft Reporting Tool. I have located the main parts of the install (TAC, Job Servers, Nexus Repository, PSQL database). The piece I can't find is the Talend Studio. Is this referenced in any file? If I reinstall it and connect to the TAC, will that cause any issues if there is an existing installation. If I have to reinstall it, I would like to put it on my Windows Workstation and I assume that won't cause any issues.

There are about 60 running tasks (30 prod, 30 test). 

Where are the datasources defined? I didn't see anything in the TAC so I assume this is something I would see in the Design Center?  Any other hints or direction would be appreciated. Thank you.

[Anonymous · Accepted solution]

This might be a bit tricky if you have no experience, but I may be able to give some advice.

1. Talend Studio

This should have been delivered with the product. I am not sure how Jaspersoft distribute this, but you will need to contact Jaspersoft to see if they can send you the Studio or whether you need to come to us. I'm afraid I have never used Talend with Jaspersoft and am not entirely sure of the agreement.

2. Installing Talend Studio and its effect on other systems

You do not need to worry about this. Talend Studio is completely separate to the TAC. It is essentially a development tool based on Eclipse.

3. Datasources are defined within the Studio normally. You will need the Studio and Job Designs to see these. There is a possibility that they are parameterised and therefore you may find them in a database or flat file somewhere. Otherwise they are defined inside the jobs and are compiled in.

4. Job Designs

It is likely that you will find a SVN server somewhere holding the job designs. This is important to look out for. It will be configured within the TAC

5. Command Line

You *may* be using the Command Line product. Again, this should be configured with in the TAC

[Anonymous]

Thanks for your direction. 

I found what looks like executables for the Studio but the install was asking for the URL of the TAC to pick up the license and I was worried it would mess up the Production environment if I installed another Studio. If this doesn't cause any issues, I'll put in another installation and hopefully it picks up my Jobs when I connect to the TAC.

The configuration of the GIT and SVN are empty and there are errors for both command lines in the TAC Configuration. I'll tackle that as I learn more about this Product. The key jobs are working and my biggest concern is they will encounter issues before I have learned enough about this architecture to correct them.

It will be a challenge but this gets me pointed in the right direction so I appreciate the information

[Anonymous]

You will need to know where they kept their job designs before the old guy left. That is essential. 

Providing the URL of the TAC will be fine. You will need to set yourself up as a user within the TAC. Also look out for Projects in the TAC. This may help you find the Job Designs.