A job is a non-interactive processing task. For example, to export records you configure the export, then when you tell EnterWorks to start the export, an export job is started that runs until the job finishes exporting records (the job completes), the job fails, or the job is aborted.
When a job is processing a lot of records (such as an import, export, or validation job), the records are split into 200 record batches and run as separate threads. If one of the batches fails, the other batches may still complete successfully. In that case, the job would have completed with errors.
If a user tells EnterWorks to abort a job, an abort indicator is set that tells the job to abort. The job routinely checks the indicator to see if it needs to abort itself. If the indicator is set, it aborts itself. If the job is stuck, it may not be able to check the abort indicator, therefore it may not abort itself.
The Job Monitor allows the user to view and manage their jobs. It displays information about jobs that are currently running and jobs that have recently run.
Job scheduling is the function that allows pre-scheduling one-time or repeated activities:
-
Imports
-
Exports
-
Promotions
Each of the three types of scheduled activities has its own set of repositories and workflows:
-
A workflow that triggers a scheduled activity to occur.
-
A Scheduling Repository that stores the configuration details for each instance of an activity; one record per each defined activity. Configuration details might include settings such as which template to use, transmission options, or how often to perform the activity.
For example, there might be an export of the Product IDs from the product repository to a particular target scheduled to run every Tuesday night. There would be a record in the Scheduled Exports repository that would include the name of the export template, the name of the repository, how often the export should run, and other pertinent settings.
-
A Scheduled Jobs Repository that contains records representing the currently active or recently completed jobs. When a job is initiated, a record for the job is created in the scheduled jobs repository. The details of the job are copied to the record and the record is subsequently updated to reflect the current status of the job.
To continue the example, every Tuesday night, the workflow would kick off the export of the Product IDs, and it would store the details about the export in the Scheduled Exports Jobs repository, such as the completion status of the job and error indicators.