OASIS Batch Processing is the background automation system used to execute scheduled or repetitive tasks without requiring a user to manually start each process. Within OASIS Online, batch technology supports automatic functions such as Tile updates and Scheduled Report emails, while OASIS batch jobs can also be used for activities such as downloading information, processing reports, and synchronizing databases.
For administrators, understanding batch processing is important because an automated task can continue running even when ordinary users are not actively interacting with it. Proper configuration, scheduling, monitoring, and error review help ensure that background processes operate reliably.
This guide explains OASIS Batch Processing, Batch Services, Batch Jobs, scheduling patterns, job cycles, administration, monitoring, and common troubleshooting techniques.
What Is OASIS Batch Processing?
OASIS batch processing allows software tasks to run in the background according to configured rules.
A batch job can be a standard OASIS feature or custom functionality created for a specific customer. OASIS documentation notes that batch jobs have been used for more than a decade for tasks including factory-data downloads, report processing, and database synchronization.
Instead of requiring someone to manually initiate every repetitive task, administrators can configure jobs to run automatically.
OASIS Online Batch Technology
OASIS Online includes dedicated administration areas for batch technology.
Authorized administrators can access:
- Batch Services
- Batch Jobs
- Job Administration
These options are available from the Jobs menu within OASIS Online Configuration. Users must have Admin access to Software to manage these features.
What Is an OASIS Batch Service?
The Batch Service provides processing capacity for background jobs.
OASIS Online documentation states that every OASIS installation includes a full implementation of the batch service. The service becomes active when OASIS starts and restarts when the computer restarts. It can be disabled, although the underlying process itself cannot simply be stopped through the normal configuration workflow.
Batch Services are categorized as:
- Active
- Not Active
Administrators can inspect each service to understand its current state.
Batch Service Information
The Batch Service Viewer displays several useful attributes.
These include:
- Software version
- State
- Last update
- Active status
- Server status
- Number of concurrent processes
OASIS states that the Update value should normally refresh every two to five minutes.
This information can help administrators determine whether a service is responding normally.
OASIS Batch Jobs
A Batch Job is a background task that runs without ordinary user input.
OASIS Online organizes Batch Jobs into three categories:
- Active
- Not Active
- Disabled
The Batch Job Viewer displays the job name, status, summary, schedule, affinity, disabled status, and historical cycles.
This provides administrators with a central location for reviewing automated activity.
OASIS Batch Job Status
Job status helps administrators understand what a background process is doing.
Common statuses include Running and End. OASIS also uses Never Run when a job has not yet executed.
Legacy Batch Job Monitor documentation describes additional states including Setup, Spawned, Stopped, Unknown, Terminated, and Exception.
An abnormal state can indicate that further investigation is necessary.
Scheduling OASIS Batch Jobs
Batch Jobs can use Time Patterns to determine when they run.
Current OASIS Online documentation includes scheduling concepts such as:
- ONCE
- ALWAYS
- DELAY
- YEAR
- MONTH
- MDAY
- WDAY
- HOUR
- MINUT
These patterns allow administrators to configure one-time, recurring, or calendar-based processing.
ALWAYS Batch Jobs
An ALWAYS job attempts to run whenever processing resources are available.
This type of configuration can be useful for tasks that need to execute continuously or as frequently as system capacity allows.
Administrators should use continuous processing carefully because it can consume resources.
DELAY Batch Jobs
A DELAY pattern allows a job to wait a specified number of minutes before attempting to run again.
For example, a recurring background task might complete, wait for the configured delay, and then become eligible to execute again.
This is useful for tasks that need frequent processing without running continuously.
Calendar-Based Scheduling
Administrators can also schedule jobs according to calendar values.
Examples include:
- Specific year
- Month
- Day of month
- Day of week
- Hour
- Minute
This allows automated jobs to align with business processes such as reporting schedules or recurring maintenance.
Batch Job Affinity
OASIS Batch Jobs support affinity configuration.
Affinity can determine which host or database is allowed to run a job.
Current documentation allows administrators to configure Affinity Host and Affinity DB values.
This can be particularly useful in environments where several machines or databases participate in OASIS processing.
Editing a Batch Job
Authorized administrators can edit Batch Jobs.
Available settings include:
- Disabled status
- Number of historical cycles retained
- Affinity Host
- Affinity DB
- Time Pattern
- State
Administrators can also force a job to run as soon as possible through the available restart functionality.
Changes should be made carefully because they can affect automated business processes.
OASIS Batch Job Cycles
Each execution of a Batch Job is called a cycle.
OASIS maintains historical cycles according to the Keep Cycles setting.
A cycle can contain:
- Standard Output
- Standard Error
Standard Output provides information about background processing, while Standard Error contains errors generated during execution.
Reviewing cycles is one of the most useful troubleshooting techniques.
Standard Output
Standard Output functions similarly to a processing log.
It can help administrators understand what happened while a Batch Job was running.
Depending on the job, output may describe:
- Records processed
- Updates completed
- Files handled
- Other job-specific activity
This information can help confirm whether a job completed the expected work.
Standard Error
Standard Error records errors generated during a Batch Job cycle.
OASIS states that when an error occurs, the current job cycle ends and the system attempts to run the job again during the next scheduled cycle.
Administrators troubleshooting failures should therefore inspect the Standard Error information rather than simply restarting the job repeatedly.
Job Administration
OASIS Online also includes Job Administration.
This area can be used to specify the default database for newly created Batch Jobs. OASIS notes that Tiles rely on batch jobs for automatic data updates, and administrators can select the database where newly created jobs should be assigned.
The setting is not retroactive, so existing jobs may require separate configuration.
OASIS Tiles and Batch Processing
Tiles in OASIS Online depend on batch processing for automatic data updates.
If Tile information is not refreshing as expected, administrators may need to investigate the associated Batch Job configuration or service status.
This illustrates how batch technology can affect features visible to ordinary users even though the processing itself happens in the background.
Scheduled Reports
Scheduled Report emails are another example of automated OASIS Online processing.
Batch technology can handle the background work required to send reports according to configured schedules.
If scheduled reports stop arriving, batch processing may therefore be one area to investigate.
Email Reminder Batch
OASIS also supports an Email Reminders Batch.
Documentation explains that this job can automatically email reminders to the assigned user based on the reminder date, time, and email configured for that user’s account.
When run through the server batch service, the service user must have appropriate email preferences configured.
OASIS Batch Processing Architecture
Legacy technical documentation describes several components in the OASIS batch architecture:
- OASIS GUI
- OASIS Database
- Windows Service
- Job Initiator
- Job Monitor
- Job code
The GUI is primarily used for configuration and monitoring, while configuration information and job output are stored in the database.
Job Initiator
The Job Initiator reviews jobs defined in the OASIS database.
When configured time parameters match the current time, it launches a Job Monitor for the appropriate task.
This component therefore helps connect job scheduling with actual execution.
Job Monitor
The Job Monitor tracks execution and updates the job’s state.
Legacy OASIS documentation explains that the monitor periodically reports status to the database and may terminate a job if it exceeds configured runtime limits.
Monitoring helps administrators distinguish between normal processing and jobs that may have stalled.
Checking Batch Service Status
OASIS Desktop provides a way to review when the Batch Service last ran.
Documentation explains that users can open Batch Jobs and review the recorded date, time, and host. If the date is old, the service may need to be restarted.
A recent status can indicate that the service itself is functioning even if an individual job still has a problem.
Troubleshooting OASIS Batch Processing
When automated processing fails, troubleshoot systematically.
Start by checking:
- Batch Service status
- Job status
- Time Pattern
- Affinity settings
- Job history
- Standard Output
- Standard Error
- Database configuration
Do not immediately change multiple settings because doing so can make the original problem harder to identify.
Batch Processing Security
Batch Jobs can affect business information and automated workflows.
Administrative access should therefore be restricted.
OASIS Online specifically requires Admin access to Software for management of Batch Services, Batch Jobs, and Job Administration.
Users should also protect OASIS administrator credentials and avoid sharing privileged accounts.
Frequently Asked Questions
What is OASIS Batch Processing?
It is the background processing environment used to run scheduled or automated OASIS tasks.
What is an OASIS Batch Job?
A Batch Job is a feature that runs in the background without ordinary user input and can perform standard or custom automated processing.
What are Batch Services?
Batch Services provide processing capacity for OASIS background jobs and can be reviewed through OASIS configuration.
What is a Batch Job cycle?
A cycle is one execution of a Batch Job. Historical cycles can contain Standard Output and Standard Error information.
Who can manage OASIS Online Batch Jobs?
Users need Admin access to Software to view and manage OASIS Online batch technology.
Why is my OASIS Batch Job failing?
Potential causes include job configuration, service problems, affinity settings, scheduling, database configuration, or an error generated by the job itself. Review the job cycle and Standard Error information.
Final Thoughts
OASIS Batch Processing provides the automation layer behind many recurring and background tasks. Batch Services provide processing capacity, Batch Jobs define automated work, Time Patterns control scheduling, and Job Administration helps determine where new jobs run.
Administrators can use job history, Standard Output, Standard Error, service status, and affinity settings to understand how automated processes are operating.
Because batch technology can affect reports, Tiles, database operations, reminders, and other important business processes, configuration changes should be made carefully and only by authorized users.