4.1 Oracle Financial Services Job Protocol

The system initiates all jobs by using a standard operational protocol that utilizes each job’s metadata, which resides in a standard set of database tables. Oracle Financial Services Job Protocol processes include the following:

  • dispatcher: Polls the job metadata for new jobs that are ready for execution. This daemon process starts a mantas process for each new job.
  • mantas: Creates a new job entry based on a template for the job that has the specific parameters for this execution of the job (that is, it clones a new job).

As an Oracle Financial Services administrator, you invoke the dispatcher and mantas processes by running the shell scripts in the following table.

Table 4-1 Shell Scripts that Call OFS Processes

Process Description
start_mantas.sh Starts all jobs. This script invokes the cloner and mantas processes. This is the integration point for a third-party scheduling tool such as Maestro or AutoSys.
start_chkdisp.sh Calls on the check_dispatch.sh script to ensure that the dispatcher runs.
stop_chkdisp.sh Stops the dispatcher process.
restart_mantas.sh

Changes job status codes from the ERR status to the RES status so that the

dispatcher can pick up the jobs with the RES status.

recover_mantas.sh Changes job status codes for jobs that were running at the time of a system crash to the ERR status. After running this script, the restart_mantas.shscript must be run to change the ERR status code to RES in order for the dispatcher to be able to pick up these jobs.

In the Oracle Financial Services Job Protocol, the processes use a variety of metadata that the database provides. Some of this metadata specifies the jobs and their parameters that are associated with the regular operations of an installation. Some of this metadata captures the status of job execution and is useful for monitoring the progress of an operational cycle.

The following sections describe how the processes and metadata interact in the Oracle Financial Services Job Protocol.