Once you have the xtConnect extension package and the xTuple Connect Batch Manager client installed, you are ready to begin the process of setting up and configuring your system. Before we dive into the particulars, here is a list of important points to keep in mind regarding the xTuple Connect Batch Manager:
If the xTuple Connect Batch Manager is not running, then jobs will not run when they are scheduled to run. If the xTuple Connect Batch Manager is not active for a period of time, it will immediately, when restarted, process all the jobs that are past due. Depending on the jobs, this might take some time.
Best practice for xTuple ERP is to run only PostgreSQL and the production xTuple ERP database on the PostgreSQL server. The xTuple Connect Batch Manager requires surprisingly little computing power, as most of the work on a job is actually done on the PostgreSQL server. Therefore, a computer or virtual machine with modest performance will suffice for running the xTuple Connect Batch Manager.
The permanent user you create to run the xTuple Connect Batch Manager should be a PostgreSQL superuser on the database. This is necessary so that the Schedule Server Maintenance job can reindex all tables. This user may also require specific application privileges for certain jobs. If you attempt to run a job through the xTuple Connect Batch Manager and the xTuple Connect Batch Manager user does not possess a required privilege, a message will indicate this condition under the "Exit Status" column on the xTuple Connect Batch Manager status screen.
The xTuple Connect Batch Manager connects to—and processes jobs for—only one xTuple ERP database at a time. If you need to use xTuple Connect with more than one xTuple ERP database, you will need to set up and run more than one xTuple Connect Batch Manager. To avoid potential conflicts, only one xTuple Connect Batch Manager instance should be connected to a particular xTuple ERP database at a time.
The xTuple Connect Batch Manager processes one job at a time. If two jobs are scheduled to run at the same time, the xTuple Connect Batch Manager will process them sequentially. Any time the xTuple Connect Batch Manager sees a pending job that is past due, it will process that job immediately. Once a job is completed, the user who submitted it will receive a notification email or System Message.