We are having talend jobs where Db2 is the database, so we have created connected using all tDb2* components. Now we are migrating from Db2 to Oracle, so all the jobs need to be touched to changed to db related functionality.
Could anyone please suggest an approach to have an connection implementation so that jobs will not be impacted during db migration.
Right now, we do not have a universal DB connection. You can change the DB value from the drop down for the DB components from the wrapper tDB* component list. But you will have to still do the setup of the component manually. If you are using a tDBComponent or table details from Metadata repository, you can reduce the amount of data to be filled for the various parameters.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved
I'm thinking to create a joblet where I will define my connection related stuff. Then use the same joblet across all job. In case ther is any connection change, we need only to update the joblet.
Joblet will be a good approach since it is actually part of the same job. The only change we are doing in the case of joblet is we are wrapping the repeatable or complicated part to a logical unit.
I like that approach.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved
If we create a remote common project and create the joblet in it and use it as dependency for all the other projects. That's how how can use the same joblet for all the projects. In case we need to change the connection, we can go to the common project and update the joblet. Then that will be reflected for individual projects and changes will be minimum.
