Siebel System Administration Guide > Administering Siebel Server Run-Time Operations > Administering Component Jobs >

Starting a Repeating Component Job


This topic describes the procedure for creating and starting a repeating component job. You can define repeating component jobs using either components or component job templates, and you can schedule component jobs to run repeatedly at specific times over specific intervals. In order to run repeating component jobs, both the Server Request Broker (alias SRBroker) and Server Request Processor (alias SRProc) server components must be running. If you need to run repeating jobs at unspecified times or intervals, run repeating component jobs using a component job template.

For background information on component jobs, see About Component Jobs. For background information on component job templates, see Configuring Component Job Templates.

For information on creating an individual component job, see Starting a Component Job.

NOTE:  It is not possible to start a business service directly as a repeating component job. To accomplish this task, you first need to include the business service in a workflow process. You can then run the workflow process as a repeating component job using the Workflow Process Batch Manager component (alias WfProcBatchMgr).

To start a repeating component job

  1. Create a component job as described in Starting a Component Job, but do not start the component job.
  2. In the Job Detail view, enter data in the Repeating Info fields as described in the following table. Click the menu button, and then click Save Record.
    Field
    Description

    Repeating?

    Select this check box to make the component job a repeating component job.

    Repeat Unit

    This field determines the length of time before the component job repeats when it is set with the Repeat Interval field,

    Repeat Interval

    Set with Repeat Unit field, this field determines the length of time before the component job repeats.

    Repeat From

    This field has three possible settings:

    • Scheduled Start. Starts the next iteration of the repeating component job after the interval period has elapsed. The interval period is calculated from the time indicated by the field, Scheduled Start. For example, if the repeat interval is 5 minutes, the scheduled start time is 09:00, and the component job starts at 09:02, the next component job is scheduled to start at 09:05. Using this selection might result in a backlog of component jobs that will be started if the actual start time is later than the scheduled start time.
    • Actual Start. Starts the next iteration of the repeating-component job after the interval period has elapsed. The interval period is calculated from the time the component job starts rather than the time indicated by the Scheduled start field. For example, if the repeat interval is 5 minutes, the scheduled start time is 09:00, and the component job starts at 09:02, the next component job is scheduled to start at 09:07.
    • End. Starts the next iteration of the repeating-component job after the previous component job ends and the repeat interval has elapsed. For example, if the repeat interval is 5 minutes, the scheduled start time is 09:00, the component job starts at 09:02, and then the first component job ends at 09:04, the next component job is scheduled to start at 09:09.

    Repetitions

    This field determines the number of times the component job repeats.

  3. In the Jobs list, click the Submit Job button.

    The Status field changes from Creating to Active.

Siebel System Administration Guide Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.