...
- Use Case
- Run a specific job within a job chain in multiple parallel instances, i.e. split a job for parallel processing.
- The use case is intended for execution of the same job within a job chain in parallel instances, not for parallel execution of different jobs.
- Typically each job instance is focused, e.g. on a partition in an Oracle database. The job chain is intended to query database partitions in parallel and to be parametrized individually.
- Resume processing of the job chain after all parallel instances have completed processing.
- Run a specific job within a job chain in multiple parallel instances, i.e. split a job for parallel processing.
- Solution Outline
- The number of parallel job instances is dynamically determined by an initial job.
- Subsequently the relevant number of orders to be executed in parallel are created for the job that is be executed in parallel. The number of parallel tasks can be restricted by a process class, forcing job instances to wait for a task to become free.
- Finally further processing is carried out after the processing of all the parallel job instances has been completed.
- References
- Availability
Display feature availability StartingFromRelease 1.11.4 - See How to Execute Jobs in a Job Chain in Parallel for more information.
Solution
- Download parallel_job_instances.zip
- Extract the archive to a folder
./config/live/of your JobScheduler installation. - The archive will extract the files to a folder
parallel_job_instances. - You can store the sample files to a any folder as you like, the solution does not make use of specific folder names or job names.
...