Job: TemplateProcess is called by Job: Template and is responsible for calling Job: TemplateOrchestrate or, for simple applications, Job: TemplateTask. For most scenarios, you will need to make just a single change to this Job, simply identifying the child Job that should be called.
In some scenarios, where you are developing a Persistent Job, you may have requirement to also call a once-only child Job.
Key Features of this Job are: –
- File System Management
- Run Window Management
- Job Persistence Management
- Stop File Management
- User-defined Task Management (child Job)
- Run-once User-defined Task Management (child Job)
- Robust Error Handling
You will see that there are a number disabled components that handle execution of a run-once Job. This consists of a tJava and tRunJob component (coloured yellow), and a tDie component (coloured red).
You normally only need to configure the run-once Job, when you’re writing a Persistent Job. The purpose of the run-once Job is to perform any initialisation tasks that you may want to perform prior to your Job entering a persistent state.
You will see that there are a number components that handle execution of the Job: TemplateChild that makes up your own work. This consists of a tJava and tRunJob component (coloured yellow), and a tDie component (coloured red).
Depending on the complexity of your own work, your own work will consist of one or more child Jobs.
If your own work consists of multiple Jobs, then I would strongly recommend that the child Job called from Job: TemplateProcess is simply an orchestration Job, that is, it’s sole purpose is to call a number of other Jobs in the correct order, handle any Exceptions, and return the overall exit code.
I will talk more about an Orchestration Job in a later article. A future version of the Talend Framework will include a template Orchestration Job, which will be derived (as you should do) from Job: TemplateChild.