The xTuple Connect Batch Manager should be left to run continuously—like a service. However, the xTuple Connect Batch Manager is not a service. It is a graphical application—and so you will need to employ various techniques to ensure the xTuple Connect Batch Manager keeps running continuously. In other words, if the computer the xTuple Connect Batch Manager is running on goes down, the xTuple Connect Batch Manager must also be restarted when the computer is brought back up again.
In this section we explore some of the techniques you might use to avoid having to restart the xTuple Connect Batch Manager manually whenever the computer it is running on is restarted. Please do not consider the suggestions offered here as complete solutions. Certain issues, such as security, are not taken into account.
In the previous section we learned how to pass arguments to the xTuple Connect Batch Manager client at runtime. These arguments can also be used in a startup script that executes when a computer reboots and a user is logged on.