4.9 Scheduling Jobs

This topic describes the about the information on scheduling the jobs.

All jobs for scheduling are stored in a static data store and each job is associated with a name indicating where the job has to execute. Jobs are created in the Application Server and are scheduled based on this data.

Note:

The job name should be unique across the schedulers available in the system.

When the application server starts, the job details from static data store will get cached. These cached jobs will then be scheduled using either the quartz or flux scheduler.

For example, the notification process can be handled by the job schedulers as follows:

• When a contract is created in Oracle FLEXCUBE, a database level trigger acting on the contract main table inserts details like base table name, primary key fields, primary key values and branch code into a notification log table and sets the process status of the inserted record as U (unprocessed).
• The scheduled job polls the notification log table for unprocessed records and validates whether notification is required.
• If notification is not required, then the process status is set to N (not required) in notification log table.
• If notification is required then notifications are sent to the respective destination and the process status of the record is changed to P (Processed) in notification log table.

This topic contains the following sub-topics:

• Jobs Details
  This topic describes the about the information on controlling the jobs.