I have a route that monitors a database table and when records are inserted, action is being taken by the route. I can deploy a task for this route, with it's onw parameters and settings.
Now, I want to deploy a second task, based for the same route, but with different parameters in order to monitor a different database table.
I'm able to deploy one task and all works fine. But when I deploy the second task, I get :
Duplicate installation of kar ro_vcfe_consumer_AS400DB2dbTable_0.1.8.20250708123915 is not supported. The kar ro_vcfe_consumer_AS400DB2dbTable_0.1.8.20250708123915 is already installed on target Talend Runtime. The kar was instaled by Task ro_vcfe_consumer_AS400DB2dbTable (ID: 6870d4333a530e7f68bd77a5, Version: 7.7, Execution ID: 0f532e3f-b21d-4fc5-b4b8-28b0c507f90e)
Is it possible at all to deploy multiple tasks of one Route with a different configuration (other parameters and settings) ??
I have a route that monitors a database table and when records are inserted, action is being taken by the route. I can deploy a task for this route, with it's onw parameters and settings.
Now, I want to deploy a second task, based for the same route, but with different parameters in order to monitor a different database table.
I'm able to deploy one task and all works fine. But when I deploy the second task, I get :
Duplicate installation of kar ro_vcfe_consumer_AS400DB2dbTable_0.1.8.20250708123915 is not supported. The kar ro_vcfe_consumer_AS400DB2dbTable_0.1.8.20250708123915 is already installed on target Talend Runtime. The kar was instaled by Task ro_vcfe_consumer_AS400DB2dbTable (ID: 6870d4333a530e7f68bd77a5, Version: 7.7, Execution ID: 0f532e3f-b21d-4fc5-b4b8-28b0c507f90e)
Is it possible at all to deploy multiple tasks of one Route with a different configuration (other parameters and settings) ??
The "duplicate kar" error you encountered is because Talend Runtime does not allow the same route file to be deployed multiple times. To solve this and achieve your goal, you must modify your route to use **Context Variables** instead of hardcoded values. This allows you to deploy a single route file but create multiple tasks, with each task configured to use different parameters, such as a different database table name, at the time of deployment.
you can't deploy several tasks based on the same route on a single runtime.
That mean one unique route by task.
You can duplicate the route in the Studio as it will have a new name it will be considered as a different artifact and so you wil be able to associate each different route to a task.
Or you can try to centralize the main mechanism with a routelet and use the routelet in several routes. Then publish one route for each db monitoring.
