Microsoft Dynamics AX 2012 has the ability to run jobs in batch by leveraging the abilities of the batch framework. The batch framework has two main purposes:
Enable jobs to be scheduled.
Provide a mechanism to split jobs up into smaller parts and run them in parallel. By doing so, the batch job has a larger throughput and the response time is much better.
We want the service that we created earlier to use the same batch framework so that it has better performance. There are different approaches to this and each has its advantages and disadvantages. The two most commonly used approaches can be described as:
Individual task approach
Helper approach
This approach will divide the batch job into a number of work units also known as runtime tasks . For each work unit, a runtime task will be created. So you will have a one-to-one relation between work units and runtime tasks.
When your batch job is executing in batch, it is only responsible for creating the tasks...
