2.1 Define Jobs
This topic explains systematic instructions to define jobs.
- On Homescreen, type STDJOBMT in the text box, and click Next.The Job Maintenance screen displays.
Figure 2-3 Job Maintenance
- On the Job Maintenance screen, specify the fields.
Note:
The fields, which are marked with an asterisk, are mandatory.For more information on fields, refer to the field description table.
Table 2-1 Job Maintenance - Field Description
Field Description Job Code Specify the unique code to identify the job. Job Description Specify a brief description of what the job is supposed to do. Job Group Specify the job group name to represent the same group of jobs for identification. Job Type Select the type of job from the drop-down list: - PL/SQL
- JAVA
Max Number Instances Specify the maximum number of instances that needs to be queued up. For example, If a job runs for more than the duration defined, the next instance of the same job will be ready for processing. This parameter defines the jobs behavior in such cases. If the job is maintained as STATEFUL, then the number of such missed instances will be queued up so that it would start executing once this long-running job ends.
This field specifies the number of such job instances that needs to be queued up. If the job is maintained as STATELESS, it indicates the number of threads that can be executed in parallel. If the max number of instances is maintained as 0, no instances are queued or parallel processed till the current running instance is completed.
Scheduler Specify the name of the scheduler. The system defaults the name to SchedulerFactory. However, the scheduler name can be modified. This signifies the scheduler name which is configured as part of infra. Trigger Type Select the type of trigger from the drop-down list:- Simple - Interval based jobs (that is every hour)
- Cron: Time based jobs (that is Friday 4:30PM).
Note:
When the scheduler trigger type is set to CRON, and the parameter is TIMEZONE, then the system triggers the jobs based on the time zone set. If the TIMEZONE property is not available, then the server time zone will be used to trigger the scheduler job.Scheduler Type Select the type of scheduler from the drop-down list:- Quartz
- Flux
Priority Select the priority on which the system should execute the jobs in the scheduler from the drop-down list:- Normal
- High
- Low
Message Queue Specify the default JMS queue to which a job needs to send the message. Specify this only if the job has to send messages to JMS. Cron Expression Specify the corresponding Cron expression for a job with the trigger type as Cron. The user needs to do this to determine the time and interval of job firing. Class or Procedure Specify the Java class file name if the job type is Java or the PL/SQL procedure name if the job type is PL/SQL. This denotes which java class or PL/SQL procedure the system should call when a job fires. Number of Submissions Specify the number of times a job can fire before it is unscheduled from the scheduler. This applies only to trigger types maintained as Simple. Interval In Seconds Specify the time interval between jobs. This applies only to trigger types maintained as Simple. Trigger Listener Specify a java class as a trigger listener which will be notified of events such as before a job is fired, after a job is completed, and after misfired jobs. Active Check this box to set the job as active. The scheduler does not pick the inactive jobs for scheduling. Ds Name Specify the name of the database schema to which the job has to connect. This attribute is used in case of multi-instance deployment of Oracle FLEXCUBE Universal Banking application. Logging Required Check this box to indicate that system should log each firing of the job. This helps in logging the firing time of the job and key log info as part of that firing. This also enables tracking of each jobs firing times and helps in identifying miss-fired jobs. Veto Blocked Trigger Check this box to trigger a veto block. Start up Mode Specify the start up mode of the job from the drop-down list:- Auto - The job starts automatically when the Oracle FLEXCUBE Universal Banking application starts.
- Manual - Start the job manually in the job controller by resuming the job.
Table 2-2 Parameter Details - Field Description
Field Description Parameter Name Specify the name of the job parameter. The parameter name specified here is passed to the job class or procedure at run time. Data Type Specify the data type of the parameter. Parameter Value Specify the value of the parameter. - Click Exit to end the transaction.
Parent topic: Job Scheduling