6.54 Scheduling Editor

Use to schedule the executions of your scenarios using the Oracle Data Integrator built-in scheduler.

A schedule concerns only one scenario, but a scenario can be scheduled in several ways, and can have several schedules. Each enables a start date and a repetition cycle to be specified.

For example:

  • Schedule 1: Every Thursday at 9 PM, once only.

  • Schedule 2: Every day from 8 AM to 12 noon, repeated every 5 seconds.

  • Schedule 3: Every day from 2 PM to 6 PM, repeated every 5 seconds, with a maximum cycle duration of 5 hours.

The Scheduling Editor has the following tabs:

6.54.1 Definition

Properties Description
Context Execution context of the scheduled scenario.
Agent Agent responsible for executing the scenario.
Log Level Logging level. All the tasks whose logging level is lower than or equal to this value are saved in the log at the end of execution.

Status

Defines the activation of the schedule.

Icon Properties Description
Surrounding text describes active_schedule.gif. Active Schedule is active when the agent is restarted or when the scheduling of the physical agent is updated.
Surrounding text describes inactive_schedule.gif. Inactive Schedule is not active and will not run.
Surrounding text describes active_schedule_for_period.gif. Active for the period Activity range of the schedule. A schedule active for a period of time only runs within this given period.

Execution

Defines the frequency of execution of each execution cycle

Properties Description
Execution Frequency of execution (annual, monthly, simple, and so forth). This option is completed by a set of options that depend on this.

6.54.2 Execution Cycle

The execution cycle shows the repetition mode of the scenario.

Properties Description
None (Execute once) Scenario is executed only one time.
Many times Scenario is repeated several times.

  • Maximum number of repetitions: The maximum number of times the scenario is repeated during the cycle.

  • Maximum Cycle Duration: The maximum duration of time, after which the scenario is no longer restarted and the cycle stops.

  • Interval between repetitions: The downtime between each scenario execution.

    Notes:

    • The minimum value allowed for a schedule is 1 second.

    • Repetition interval is the time between the start of two jobs. If the first execution takes longer than the repetition interval, then overlap is possible between the first job execution and its repetition.
Constraints Allows limitations to be placed on one cycle iteration, in the event of a problem during execution.

  • Number of attempts on Failure: Maximum number of consecutive execution attempts for one iteration.

  • Stop Execution after: Maximum execution time for one iteration. If this time is reached, the scenario is automatically stopped.

6.54.3 Variables

When you create a schedule for a scenario or Load Plan, you can define the values taken by the parameter variables for the scheduled executions.

Properties Description
Name Name of the variable. It is prefixed by GLOBAL for a global variable, or by the code of the project containing the variable.
Latest Value The variable takes its last value (or its default value if it has never been set) if this check box is selected. If this check box is not selected, the variable takes the value indicated in the Value field.
Value Value taken by the variable for the execution.

Related Topics

"Scheduling Scenarios and Load Plans" in the "Running Integration Processes" chapter in Oracle Fusion Middleware Administering Oracle Data Integrator