Talend Job on Talend for ESB doesn't trigger on generating touch file
Hi Talend Community,
I currently have a Talend Job on the server (Talend for ESB-Open Studio) which is supposed to trigger at 9:00AM each morning. For this there is a cron job which creates a empty touch file at 9:00AM to trigger the job. The issue is the job doesn't trigger on generating touch file,so had to configure the cron job in such a way that it creates a touch file, move jar file from deploy folder and then re deploy the job each time the touch file is generated. Only then the job is triggered. Can you please suggest on possibilities why this is happening.
Hi Are you using tWaitforFile in the job to trigger the execution? Can you please provide more information about the job or how you schedule job? So that we can know which step went wrong.
-->We have the jar file for talend job running inside the container on the server (Talend for ESB 6.5)
1)A cron job script generates a touch file with respect to the file mask that is given in File mask of tWaitForFile in the location where it is waiting for file.
2)Now that the file the twaitforlist is waiting for is generated we expect the talend job(jar inside container) to trigger.
But in this case the talend job doesn't trigger on the generation of touch file
so we had to do this additional step in cron job script.
1)Generate touch file
2)Pull the jar file from deploy folder to another location(xyz)
3)Again re deploy the jar file in deploy folder from location(xyz)
-->Then the job triggers and proceeds for further steps.
P.S: Image attached for tWaitForFile component configuration
This is a standard DI job, you just need to export the job script, execute the .bat file on Windows or .sh file on Linux, or schedule the job to run using scheduler. The ESB container (Talend Runtime) which is based on upon Apache Karaf, is used to run Route or service.
But my requirement is to build this job as on OSGI Bundle jar but not as a Standalone job. I'm having many such jobs which are doing perfect. Just this one job isn't responding to touch file unless it is redeployed each time the touch file is generated.
P.S: image of script that generates touch file with additional step to redeploy jar(only then the job triggers)
