Currently im in migrating project from previous ETL tools to Talend (with TAC).
I dont want to make major changes from what we did on previous tools.
On my previous tools, we have a lot of project which it have dependencies with another project,(like : EDW Project -> Datamart Project) ,we make it in different project to make it easier to maintain if error occured.
So, is it possible to design ETL job in talend in the same way?
or in talend have specific best practice to handle this requirements?
Solved! Go to Solution.
Since you are using TAC, I assume you have shared repositories either SVN or Git to store the Talend metadata where each project has its own URL.
By using tRunJob , we can refer only jobs within project.
We can't cross refer the jobs across multiple projects in Studio.
But we can schedule jobs from different projects in same execution plan in TAC.
Take a look at the Talend Metaservlet API. I assume you are using the Enterprise Edition. You can create tasks, deploy tasks, start tasks, etc, etc, using the MetaServlet and it does not matter which project the jobs come from.
If you are using enterprise edition ,then you can do,since your jobs store in same repository.in community edition is not accessable the same.
i am new to Talend, would you mind to share the step / flow how to do that?
My idea is to make a common job which can be call by different project as of when it is needed.