OASIS Batch Job Monitor is part of the background-processing architecture used to execute and monitor automated OASIS tasks. For advanced users and administrators, understanding job states, expected runtime, scheduling patterns, service configuration, and error output can make troubleshooting much more efficient.
Ingen Software’s Batch Job Monitor documentation describes an architecture consisting of the OASIS database, job initiator, job monitor, job code, OASIS user interface, and Windows Service. The interface is primarily used to configure and monitor jobs, while configuration information and job output are stored in the database.
This guide explains the main components of the OASIS Batch Job Monitor environment and how administrators can interpret common job states.
What Is the OASIS Batch Job Monitor?
The Batch Job Monitor is part of the infrastructure responsible for supervising background OASIS processes.
OASIS documentation describes periodic background tasks that can exchange information, perform recurring work, or handle functions such as database backups.
The system is designed so automated jobs can run without requiring a user to manually start each process.
OASIS Batch Architecture
The documented architecture contains several important components:
- OASIS GUI
- OASIS Database
- Windows Service
- Job Initiator
- Job Monitor
- Job code
Each component has a different role.
Understanding these roles helps administrators identify where a problem may be occurring.
OASIS GUI
The OASIS user interface is primarily used to configure and monitor jobs.
Administrators can review job definitions and change applicable configuration through the software interface.
The interface is therefore the administrator’s primary control point rather than the component actually performing every background task.
OASIS Database
The database stores Batch Job configuration information and job output.
This allows the system to maintain information about scheduled jobs and their execution results.
Database availability is therefore important to successful batch processing.
Job Initiator
The Job Initiator reviews jobs defined in the OASIS database.
When a job’s time parameters match the current time, the initiator launches a Job Monitor for that job.
This makes the initiator the component responsible for recognizing when a configured job should begin.
Job Monitor
The Job Monitor supervises the execution of the job.
OASIS documentation states that the monitor regularly updates job state information in the database and can terminate a job when it exceeds configured runtime limits under applicable settings.
Monitoring is important because background tasks can otherwise fail without being immediately visible to users.
Windows Service
OASIS Batch Jobs can use a Windows Service so background processing continues even when a user is not logged into the computer.
The service starts with the computer and can support persistent automated processing.
This differs from starting the initiator through the OASIS GUI, where closing the application can terminate that manually started processing environment.
Configuring OASIS Batch Jobs
The Batch Job listing shows defined jobs along with information such as name, time pattern, and current state.
Opening a job provides access to configuration fields.
Documented settings include:
- Job Name
- Affinity Host
- Time Pattern
- Run As
- Expected Runtime
- No Overtime
Each field influences how and where the job executes.
Job Name
Job Name identifies the automated task.
Clear names make administration easier, particularly when an OASIS environment contains many background jobs.
Administrators should avoid changing names without understanding how the job is referenced elsewhere.
Affinity Host
Affinity Host identifies the computer where the job should run.
This can be important when an organization has multiple servers or workstations.
If a job is configured for an unavailable or incorrect host, execution may not occur as expected.
Run As
Run As identifies the OASIS user under whose identity the job operates.
OASIS notes that this user’s ID can appear in updated-by information.
The selected account should therefore have the appropriate access required by the job.
Expected Runtime
Expected Runtime defines the maximum anticipated runtime in minutes.
This setting helps the monitoring environment identify processes that run significantly longer than expected.
Administrators should set realistic values based on actual workload.
A limit that is too short can cause legitimate long-running processes to be treated as failures.
No Overtime
When No Overtime is enabled and a non-zero Expected Runtime is configured, the monitor can terminate a job that exceeds the allowed runtime.
This can prevent a stuck process from running indefinitely.
However, administrators should investigate why a job exceeded its expected duration rather than simply increasing the limit repeatedly.
OASIS Job States
The Batch Job Monitor uses several states to describe job execution.
Documented states include:
- Never Run
- Setup
- Spawned
- Running
- Stopped
- Unknown
- Terminated
- Exception
- End
Understanding these states can significantly improve troubleshooting.
Never Run
Never Run indicates that the job has not executed previously.
For a newly created job, this can be expected.
For a job that should already have run, administrators should review scheduling and service configuration.
Setup
Setup indicates that the initiator has begun preparing the job.
This is an intermediate state in the execution process.
Spawned
Spawned indicates that the initiator has attempted to start the monitor for the job.
If a job remains around this stage unexpectedly, administrators may need to investigate whether the monitor or underlying process launched correctly.
Running
Running indicates that the Job Monitor has started the job code.