Rapido Jobs

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Introduction

Rapido jobs enable running batch processes on a large number of entities. The jobs run in the background, without impacting the day-to-day work of the library staff. To maximize efficiency, the system constantly performs optimization and prioritization of the running jobs to ensure that each job gets enough resources to complete. In addition, some jobs can run in parallel (Multi-threaded) – the job population is split into parts that can run in parallel to each other. Before a job is executed, it is examined by the system to check whether any dependent jobs or other instances of the same job are currently running.

Job Types

Rapido supports the following job types:

Scheduled Jobs – Scheduled jobs run periodically. Some of these jobs are scheduled by Rapido. For other jobs, you can configure the schedule using predefined job scheduling options. Note that scheduled jobs run as close as possible to their scheduled time. A job may wait until other jobs are done and the system has enough available resources.
In addition to their scheduled run times, Rapido provides the ability to run some of these jobs at any time.
Workflow Jobs – Workflow jobs run automatically when they are required. In some cases, you can also run or rerun these jobs at any time—for example, if the original run failed.
Manual Jobs – These jobs are available to run by you as required. Some manual jobs first require you to create sets (of items, users, and so forth) for the job to process. To run manual jobs, see Manual Jobs.

Jobs are sometimes called processes in the UI.
Some jobs are dependent on other jobs because they modify the same data. A job can also modify data that has a relationship with data updated in other jobs. To prevent these jobs from failing due to simultaneous data use, dependent jobs are scheduled to not run at the same time.

Configuring Jobs by Use of Profiles

Rapido uses profiles to configure and/or schedule certain types of jobs. You add the profile, give it a name, and configure its parameters. This creates a job that is available to run, either from a specific location within Rapido or automatically as a scheduled job.

Common profiles in Rapido include:

Integration Profile – Creates a job that exports information to, or imports information from, an external system, such as a Student Information System. For more information, see Configuring Integration Profiles.

Jobs Monitoring

To view scheduled jobs, see Viewing Scheduled Jobs.
To view running jobs, see Viewing Running Jobs.
To view job history and reports, see Viewing Completed Jobs.

The option to Abort a run job is further described in Viewing Running Jobs.

Expected Job Duration

As a multi-tenant cloud-based solution, Rapido has a sophisticated batch job management architecture, which accounts for various factors such as the types of jobs running, the time of the day, and the general load of the system, all to provide you with the services you require.

When using Rapido’s batch job services for managing your repository, it is useful to know how long processes can be expected to run. The guidelines provided below are based on Rapido’s actual production use of these services. Ex Libris expects that, on average, the job capacity is not less than listed, and often even better. This depends on the system load at any given time.

Off-Peak hours are during the night (relative to your data center location) and usually span 6 hours (for example, midnight to 6:00 AM).

For more information, see Scalability and Performance.