1.1 Process Job Maintenance

This topic provides the systematic instructions to define and schedule a job.

A job is a business activity which the system performs repeatedly on timely basis.

Oracle® FLEXCUBE Investor Servicing enables you to define a job and schedule it using Job Maintenance screen.

  1. On Home screen, type STDJOBMT in the text box, and click Next.
    The Job Maintenance screen is displayed.

    Figure 1-1 Job Maintenance


    Description of Figure 1-1 follows
    Description of "Figure 1-1 Job Maintenance"

  2. On Job Maintenance screen, click New to enter the details.
    For more information on fields, refer to the field description table.

    Table 1-1 Job Maintenance - Field Description

    Field Description
    Job Code

    Alphanumeric; 100 Characters; Mandatory

    Specify the unique code to identify the Job.
    Job Description

    Alphanumeric; 200 Characters; Optional

    Specify a brief description of what the job is supposed to do.
    Job Group

    Alphanumeric; 200 Characters; Optional

    Specify the job group name to represent the same group of jobs for identification.

    Job Type

    Optional

    Select the type of job from the drop-down list. The following options are available for selection:
    • PLSQL
    • JAVA
    Max Number Instances

    Numeric; 2 Characters; Mandatory

    Specify the maximum number of instances that needs to be queued up.

    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 job’s behavior in such cases,
    • If you maintain the job 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 you maintain the job as STATELESS, it indicates the number of threads that can be executed in parallel.
    • If you maintain the max number instances as 0, no instances are queued or parallel processed till the current running instance is completed.
    Scheduler

    Alphanumeric; 100 Characters; Optional

    Specify the name of the scheduler. The system defaults the name to SchedulerFactory. However, you can modify this name. This signifies the scheduler name which is configured as part of infra.

    Trigger Type

    Optional

    Select the type of the trigger from the drop-down list. The following options are available:
    • Simple - Interval based jobs.(i.e., every one hour)
    • Cron - Time based jobs.(i.e., Friday 4:30PM)
    Scheduler Type

    Optional

    Select the type of scheduler from the drop-down list. The following options are available:
    • Quartz
    Priority

    Optional

    Select the priority on which the system should execute the jobs in the scheduler from the drop-down list. The following options are available:
    • Normal
    • High
    • Low

    If two jobs with different priorities fire at the same time, then system gives preference to the job with higher priority.
    Message Queue

    Alphanumeric; 100 Characters; Optional

    Specify the default JMS queue to which a job needs to send message. You can specify this only if the job has to send messages to JMS.
    Job Details It displays the following details.
    Cron Expression

    Alphanumeric; 400 Characters; Optional

    Specify the corresponding Cron expression for a job with trigger type as Cron. You need to do this to determine the time and interval of job firing. For instance, 40 * * * * ? Indicates job needs to be executed every 40 sections.

    Example: For time based jobs, if Cron Expression is defined as 0 0/15 11-23 * * ?, then Parameter Definition will be as follows:
    • TIMEZONE Parameter to be defined: Asia/Hong Kong
    • MODULEID: Job to be executed in FMGHKGDISTE
    • INTERFACEID: Interface ID to be mentioned

    Above scenario indicates that the Job to be started at 11:00 am Hong Kong Timezone and stops at 11:00 pm Hong Kong Timezone.

    Frequency will be every 15 minutes.
    Class or Procedure

    Alphanumeric; 400 Characters; Optional

    Specify the Java class file name if 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

    Alphanumeric; 3 Characters; Optional

    Specify the number of times a job can fire before it is unscheduled from scheduler. This applies only to trigger types maintained as Simple.

    Interval In Seconds

    Numeric; 2 Characters; Optional

    Specify the time interval between jobs. This applies only to trigger types maintained as Simple.

    Trigger Listener

    Alphanumeric; 200 Characters; Optional

    Specify a java class as a trigger listener which will be notified of events such as before job fired, after job completed, misfired jobs.
    Active

    Optional

    Check this box to set the job as active. The scheduler does not pick the inactive jobs for scheduling.
    Ds Name

    Alphanumeric; 100 Characters; Optional

    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 Investor Servicing application.

    Logging Required

    Optional

    Check this box to indicate that system should log each firing of job. This helps in logging the firing time of job and key log info as part of that firing. This also enables tracking of each job’s firing times and helps in identifying miss-fired jobs.
    Veto Blocked Trigger

    Optional

    Check this box to trigger veto block.
    Startup Mode

    Optional

    Specify start up mode of the job from the drop-down list. The following options are available:
    • Auto - The job starts automatically when Oracle® FLEXCUBE Investor Servicing application starts.
    • Manual - You should start the job manually in job controller by resuming the job.
    Parameter Details

    You can specify the job specific parameters, which are passed to job class or procedure at runtime. The following details are captured here.
    Parameter Name

    Alphanumeric; 200 Characters; Optional

    Specify the name of the job parameter. The parameter name you specify here is passed to job class or procedure at run time.

    For instance, INTERFACEID to be defined with Interface ID.

    Data Type

    Optional

    Select the data type of the parameter from the drop-down list. The list displays the following values:
    • Varchar
    • Date
    • Number
    Parameter Value

    Alphanumeric; 200 Characters; Optional

    Specify the value of the parameter.
  3. On Job Maintenance screen, process EOD.
    On completion of Pre-EOD, the job will process EOD.

    Table 1-2 Event Based - EOD

    Job Code EOD_FMGHKGDISTE
    EVENTCODE BEPREEOD
    Event Description Pre-EOD completed
  4. On Job Maintenance screen, process BOD.
    On completion of EOD, the job will process BOD.

    Table 1-3 Event Based - BOD

    Job Code EOD_FMGHKGDISTE
    EVENTCODE BE00003
    Event Description FMG EOD Completed
  5. The system will perform the following jobs to execute reports on completion of EOD.
    • Parameter Name: TASKID
    • Parameter Value: Tasks defined
  6. Below job will initiate a TASK – EODUHBALSTMT – Unitholder Balance Statement on completion of EOD.
    The TASK – EODUHBALSTMT is initiated.

    Figure 1-2 TASK – EODUHBALSTMT


    TASK – EODUHBALSTMT

Parent topic: Job Scheduling