Usually the data transfer through the xBus is started by calling a receiver for some specific interfaces. Since data transfer is needed regularly, a scheduler triggers these calls according to a specified time schedule.

One of the major design principles of the xBus is to keep things as simple as possible. One way of achieving this goal is to use existing functionalities whenever it is feasible. For this reason, no scheduling tool will be build within the xBus. Instead external schedulers are used.

The xBus provides some batch files, which start the execution of processing one or more interfaces in both directions. The scheduling of these batch files will be configured in a the external scheduler. To determine which batch file should be use for the specific tasks, read Scripts description from the Operation topics.

On UNIX machines cron offers scheduling services.

On Windows servers scheduled tasks may be configured from the control panel.