OASIS Batch Services provide the processing infrastructure used to run automated background jobs in OASIS. Instead of requiring a user to manually initiate every repetitive task, batch technology allows configured processes to execute in the background according to system settings.
OASIS Online documentation explains that batch technology is responsible for automatic processes such as updating Tiles and emailing Scheduled Reports. Administrators can manage this environment through Batch Services, Batch Jobs, and Job Administration. Access to these features requires Admin access to Software.
Understanding OASIS Batch Services is important for administrators because a batch job can be configured correctly but still fail to execute as expected if the service responsible for processing jobs is inactive, outdated, overloaded, or incorrectly configured.
This guide explains how OASIS Batch Services work, where administrators can find them, which service attributes matter, how concurrent processes are configured, and how to troubleshoot common background-processing problems.
What Are OASIS Batch Services?
OASIS Batch Services are part of the software infrastructure responsible for executing background jobs.
A batch job is a process that can run without continuous user input. OASIS describes a Batch Job as a feature that runs in the background and notes that jobs can be standard OASIS functionality or custom code created for a customer.
Batch Services provide the environment in which these automated jobs can operate.
Examples of batch-related automation can include:
- Scheduled reports
- Tile updates
- Email reminders
- Database-related processes
- Other recurring background tasks
- Customer-specific automated processes
The exact jobs available depend on the OASIS installation and configuration.
Where to Find OASIS Batch Services
In OASIS Online, administrators can access batch technology from the Configuration area.
The documented path is:
- Open the OASIS menu.
- Select Configuration.
- Open the Jobs menu.
- Select Batch Services.
The same Jobs menu also provides access to Batch Jobs and Job Administration.
Because these functions affect automated software operations, OASIS requires Admin access to Software for users who want to view or manage them.
Active and Not Active Batch Services
OASIS Online organizes Batch Services into two categories:
- Active
- Not Active
An active service is currently available for batch processing, while a service shown as Not Active is not currently operating as an active batch service.
This distinction provides administrators with a quick way to review the overall batch environment.
If automated jobs unexpectedly stop running, checking whether the expected Batch Service appears as active is a useful early troubleshooting step.
Batch Service Viewer
Opening a service displays the Batch Service Viewer.
OASIS currently documents several important service attributes:
- Software
- State
- Update
- Active
- Server
- Processes
The Software field identifies the software version used by the service. The State field shows service status. Update indicates when the service last responded, and OASIS states that this value should normally update every two to five minutes.
These fields can provide valuable diagnostic information.
Understanding the Active Field
The Active value indicates whether the service is running.
OASIS displays true when the service is running and false when it is not.
If jobs are not processing, administrators can check this field before making more complicated configuration changes.
An inactive service may explain why otherwise valid jobs are waiting rather than executing.
Understanding the Server Field
OASIS Batch Services can distinguish between servers and non-server services.
The Batch Service Viewer displays Y when the service has been identified as a server. OASIS documentation notes that non-server services normally do not run jobs while designated servers are available.
This architecture can help organizations control which machines are primarily responsible for batch processing.
It also means that administrators troubleshooting jobs should understand which machine is intended to function as the server.
Concurrent Batch Processes
The Processes value controls how many batch job processes can run concurrently on a service.
OASIS allows administrators to edit this number through the Batch Service Editor.
Concurrency matters because a service with multiple scheduled jobs may need to process several tasks during the same period.
However, simply increasing the process count is not always the correct response to slow processing.
Administrators should consider:
- Server capacity
- Database workload
- Job complexity
- Expected runtime
- Scheduling patterns
- Other system activity
Changing concurrency without understanding the workload can create additional resource pressure.
Editing an OASIS Batch Service
Authorized users can edit a Batch Service from the Batch Service Viewer.
Current OASIS documentation allows administrators to change the number of processes permitted to run concurrently and identify whether the Batch Service should be treated as a server.
These settings can influence how jobs are distributed across available services.
Changes should be made carefully because they can affect multiple automated processes.
OASIS Batch Service Restart Behavior
OASIS Online documentation states that each installation contains an implementation of the OASIS Batch Service that becomes active when OASIS starts. The service also restarts when the computer restarts.
This behavior is especially relevant for machines dedicated to batch processing.
Administrators should understand how system restarts, OASIS updates, and service availability interact before diagnosing failed jobs.
Software Version and Updates
Software version is another useful diagnostic field.
OASIS notes that if a new software version is deployed, a Batch Service can take itself offline until OASIS is restarted and the new version is loaded.
If batch processing stops after an update, administrators should therefore verify:
- Software version
- Service state
- Last update response
- Whether OASIS has been restarted
- Whether the expected server is active
This can be more effective than immediately editing individual jobs.
OASIS Batch Services and Batch Jobs
Batch Services and Batch Jobs are related but different.
A Batch Job defines the work to be performed.
A Batch Service provides processing capacity for running that work.
A simple conceptual model is:
Batch Job = what should run.
Batch Service = where or how the job receives processing capacity.
Job Administration = tools for managing and reviewing the automated environment.
Understanding these distinctions makes troubleshooting much easier.
Email Reminders Batch
OASIS provides a practical example of batch automation through its Email Reminders Batch.
Documentation explains that email reminders can be sent automatically through a Batch Job running through the OASIS Batch Service. The documented setup can send reminder emails periodically from the server running the service.
This demonstrates why Batch Services matter: the reminder functionality depends on background processing rather than a user manually sending every reminder.
Batch Service and Email Configuration
Automated email jobs can require additional configuration.
For the Email Reminders Batch, OASIS notes that the Batch Service user must have appropriate email preferences configured. SMTP is recommended for batch job usage.
If a job appears to run but emails are not delivered, the problem may therefore involve email configuration rather than the Batch Service itself.
Administrators should distinguish among:
- Service problem
- Job problem
- Email configuration problem
- Recipient information problem
Batch Service Status Troubleshooting
When automated OASIS processing stops, begin with basic service information.
Check:
- Is the expected service Active?
- What is the State?
- When did Update last change?
- Is the service identified as a Server?
- How many Processes are configured?
- Is the software version current?
OASIS states that the service response time shown under Update should normally refresh every two to five minutes.
A stale response can therefore provide a useful troubleshooting signal.
Batch Jobs Running Slowly
Slow jobs can result from many factors.
Potential causes include:
- Limited concurrent processing
- Long-running jobs
- Database workload
- Server resource limitations
- Multiple jobs scheduled simultaneously
- Job-specific errors
Administrators should review both service capacity and individual job behavior.
Increasing concurrent processes without investigating job runtime can simply move the bottleneck elsewhere.
OASIS Desktop Batch Services
Batch-related configuration also exists within OASIS Desktop.
Current OASIS Desktop documentation identifies Batch Services within Software configuration and describes this area as the place to configure the Batch Service, view existing batches, and check statuses.
Organizations using Desktop, Online, or hybrid workflows should therefore understand which environment their automated process belongs to before following configuration instructions.
Batch Services and Database Backups
OASIS Batch Job Monitor documentation identifies database backup as one example of a standard background job. The documented architecture allows batch processing to run periodic tasks that share information or back up the OASIS database.
Automating these processes can reduce manual administrative work, but administrators should still monitor results and confirm that critical jobs complete successfully.
OASIS Batch Service Security
Batch Services can execute automated processes with significant system access.
Administrative permissions should therefore be restricted appropriately.
Organizations should protect:
- Administrator accounts
- Batch configuration
- Database access
- Email credentials
- Job output
- Server access
Never provide OASIS administrative credentials to an independent informational website.
Frequently Asked Questions
What are OASIS Batch Services?
They are part of the OASIS background-processing infrastructure used to execute automated Batch Jobs.
Where can I find Batch Services in OASIS Online?
Administrators can open Configuration, select Jobs, and choose Batch Services.
Who can manage OASIS Batch Services?
OASIS states that Admin access to Software is required for these features.
What does Active mean?
The Active field indicates whether a Batch Service is currently running.
What does Processes mean?
Processes indicates how many Batch Job processes the service is allowed to run concurrently.
Why might a Batch Service go offline after an update?
OASIS notes that a service can take itself offline after a new software version is deployed until OASIS is restarted and the new version is loaded.
Final Thoughts
OASIS Batch Services provide the processing foundation for automated background jobs. Administrators can use the Batch Services environment to review active services, software versions, service status, response times, server designation, and concurrent process limits.
Successful batch administration requires understanding both sides of the system: Batch Jobs define automated tasks, while Batch Services provide the environment that executes those tasks.
When background processing fails, administrators should review service health and job configuration systematically before making major changes.