Process overview
The following overview depicts the batch processing components in context.
• The Execute batch step is at the center of the process. This is the actual execution of the work that must be done. To optimize execution, the batch process must be prepared and after the work is done, it should be finished.
 | What exactly must be done in these phases depends on the actual implementation and can hardly be generalized. |
• During the execution of the process, the prepare, execute and finish phases have access to a batch process and step context in which data can be shared to optimize the execution.
• The batch process control and the batch logging are generic components:
◦ The control component gives users the possibility to control the process.
◦ The batch logging logs the progress and informs the users about the status of the batch process.
The batch process can be started in different ways, via an action, by a scheduler, or by any other trigger. It again depends on specific functionality, but it is always asynchronous. This means that when started manually, the user will only get a message such as ‘The process has started’. To control the batch process, a specialized GUI (TSI step) is available to inspect the batch process.