The xTuple Connect Batch Manager is an application which connects to a database and waits for and then processes scheduled jobs that need to be run. These scheduled jobs are submitted from various places within the xTuple ERP application. Often the type of jobs that can be submitted are jobs that either take long periods of time to run or jobs that you would want to run periodically at a given time. When you submit a job to the Batch Manager, you specify a time for the job to start running. This job and others like it are stored on the database, waiting for the Batch Manager to process them. You can see a list of jobs submitted to the Batch Manager by selecting the "xTuple Connect Console" option from the System module.
For details on installing and setting up the Batch Manager at your site, please see the xTuple Connect Product Guide available in the Documentation area of the xTuple community website.
To access the system interface to the Batch Manager, select the "xTuple Connect Console" option. The following screen will appear:
When a report or other job is submitted to the Batch Manager with a scheduled time of ASAP, the Batch Manager sets the scheduled time to the current time. However, a job will not necessarily be run immediately if it is scheduled for the current time. Any pre-existing jobs with scheduled times prior to the current time must be completed first. In other words, ASAP jobs will not necessarily be run immediately. Previously scheduled jobs will be run first.
When managing Scheduled Jobs using the xTuple Connect Console, you are presented with the following options:
Specify the user(s) whose Batch Items you want to display.
Current User: Select to display Batch Items for the current user.
All Users: Select to display Batch Items for all users.
Selected User: Specify the user whose Batch Items you want to display.
Select to include completed Scheduled Jobs in the display.
Displays Scheduled Jobs using the specified parameters. Completed jobs will have a Run Status of Done
and a Completed timestamp. If the job failed for any reason, the first line of the error message will appear in the Exit Status column. If you allow the cursor to hover over the Exit Status text, the full version will appear in a tooltip window.
Read the exit status carefully. Jobs might show error messages for a number of different reasons. For example, a RunMRP job might fail with a database error or with an email error. The database error would mean that the planned orders were not created. The email failure would indicate that the planned orders were created as they should but this successful processing could not be reported properly.
Select to automatically update the display every minute.
The following buttons are unique to this screen:
Highlight a Job and then select this button to reschedule the Job.
Rerun one or more selected Jobs as soon as possible. This is a shortcut for the RESCHEDULE button. It allows rescheduling multiple jobs with one click. It will not reschedule existing jobs that have not yet completed.
Select to edit selected details of the Job.
Cancel (or delete) the selected Jobs, whether they have been run or not.
If the list of cancelled jobs contains all copies of a recurring Job, the recurrence will stop immediately. You will have to create a new copy of the Job and re-enter the recurrence schedule.