Schedule trigger

Operation name

Schedule trigger

Functional Overview

Schedule trigger is the function to execute the Service in the specified date/time according to the timing of daily/weekly/monthly/yearly/and interval.

Properties

Schedule trigger settings

Type	Description
Daily	Execute the script at the specified time each day.
Weekly	Execute the script at specified day of the week and time every week.
Monthly	Execute the script at specified day and time every month.
Yearly	Execute the script at specified month, day, and time every year.
Interval	Execute the script at constant time interval.

Daily

Daily schedule settings

Item name	Description	Remarks
Trigger name	Enter the name of the trigger.
Execution start time	Enter or select the start time of the executing schedule.	The default value is the current time. The specified format is "HH:mm". (HH = hour (24 hour time notation), mm = minutes) Example: "19:05" ->to start the script at 5 past 19 o'clock.
Start date of valid duration	Select when the schedule starts to be valid. [Start immediately after registration]: (default) The schedule becomes valid at the same time since the trigger is registered. [Specify start date]: Schedule will become valid since the specified date.	The default value is the current date The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20"-> becomes valid from 20 October, 2005 Date can also be selected directly from calender(launch by Down button).
End date of valid duration	Select when a schedule become disabled. [Execute indefinitely]: (default) Valid until DataSpiderServer stops. [Specify end date]: Schedule is valid until the specified date, and becomes disabled from the next day.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20" -> disabled on 21 October, 2005. Date can also be selected directly from calender(launch by Down button).

Weekly

Weekly schedule settings

Item name	Content	Remarks
Trigger name	Enter the name of the trigger.
Execution day of the week	Select a day to execute. [Sunday]: (default) [Monday]: [Tuesday]: [Wednesday]: [Thursday]: [Friday]: [Saturday]:	Multiple items can be selected. The default value is [Sunday].
Execution start time	Enter or select the start time of the executing schedule.	The default value is the current time. The specified format is "HH:mm". (HH = hour (24 hour time notation), mm = minutes) Example: "19:05" ->to start the script at 5 past 19 o'clock.
Start date of valid duration	Select when the schedule starts to be valid. [Start immediately after registration]: (default) The schedule becomes valid at the same time since the trigger is registered. [Specify start date]: Schedule will become valid since the specified date.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20"-> becomes valid from 20 October, 2005 Date can also be selected directly from calender(launch by Down button).
End date of valid duration	Select when a schedule become disabled. [Execute indefinitely]: (default) Valid until DataSpiderServer stops. [Specify end date]: Schedule is valid until the specified date, and becomes disabled from the next day.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20" -> disabled on 21 October, 2005. Date can also be selected directly from calender(launch by Down button).

Monthly

Monthly schedule settings

Item name	Content	Remarks
Trigger name	Enter the name of the trigger.
Execution day	Select or enter the execution day.	The default value is the current date. The format is "nn". (nn = 01 - 31) Example: "01" -> Executes on the 1st day of the corresponding month.
If date doesn't exist	Select the operation when the specified day does not exist in the corresponding month. [Do not execute]: Will not execute for that month. [Execute on the last day]: (default) Executes on the last day of the month. [Execute on the first day of next month]: Executes on the first day of the month.	Enabled if the [Execution day] is specified with "29", "30" or "31".
Execution start time	Enter or select the start time of the executing schedule.	The default value is the current time. The specified format is "HH:mm". (HH = hour (24 hour time notation), mm = minutes) Example: "19:05" ->to start the script at 5 past 19 o'clock.
Start date of valid duration	Select when the schedule starts to be valid. [Start immediately after registration]: (default) The schedule becomes valid at the same time since the trigger is registered. [Specify start date]: Schedule will become valid since the specified date.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20"-> becomes valid from 20 October, 2005 Date can also be selected directly from calender(launch by Down button).
End date of valid duration	Select when a schedule become disabled. [Execute indefinitely]: (default) Valid until DataSpiderServer stops. [Specify end date]: Schedule is valid until the specified date, and becomes disabled from the next day.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20" -> disabled on 21 October, 2005. Date can also be selected directly from calender(launch by Down button).

Yearly

Yearly Schedule Settings

Item name	Content	Remarks
Trigger name	Enter the name of the trigger.
Execute month/day	Enter or select the execution month and day.	The default value is the current date. The format is "MM/dd". (MM = month, dd = day) For example: "10/09"-> 9th October is the day to execute the script.
Execution start time	Enter or select the start time of the executing schedule.	The default value is the current time. The specified format is "HH:mm". (HH = hour (24 hour time notation), mm = minutes) Example: "19:05" ->to start the script at 5 past 19 o'clock.
Start date of valid duration	Select when the schedule starts to be valid. [Start immediately after registration]: (default) The schedule becomes valid at the same time since the trigger is registered. [Specify start date]: Schedule will become valid since the specified date.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20"-> becomes valid from 20 October, 2005 Date can also be selected directly from calender(launch by Down button).
End date of valid duration	Select when a schedule become disabled. [Execute indefinitely]: (default) Valid until DataSpiderServer stops. [Specify end date]: Schedule is valid until the specified date, and becomes disabled from the next day.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20" -> disabled on 21 October, 2005. Date can also be selected directly from calender(launch by Down button).

Interval

Interval Schedule Settings

Item name	Content	Remarks
Trigger name	Enter the name of the trigger.
Execution interval (h'm"s)	Select or enter the scheduled execution intervals.	The default value is "01'00"00". The format is "HH'mm"ss". (HH = hours, mm = minutes, ss = seconds) Example: "01'15"05" -> Executes the script every 1 hour 15 minutes 5 seconds. The valid entries is between 00'00"01 and 23'59"59
Execution time	Enter or select a range (time) of interval execution. [Execute for 24 hours] (default) Execute continuously. [Specify time range]: Execute continuously between the specified start time and end time. [Start]: [End]:	The default value is the current time. The format of [Start] and [End] is "HH:mm". (HH = hour (24 hour time notation), mm = minutes) Example: [Start] "06:10" -> Starts at 10 past 6 o'clock in the morning. [End] "23:05" -> Ends at 5 past 11 at night. [Start] and [End] can not be specified to cross date. Example: [Start] "6:10" [End] "4:10"
Launch limitations	Select trigger firing limitations. [Execute at regular intervals even during script execution]: (default) When firing the trigger, even if the script is running before the trigger fires, Interval Execute as the fire. [Wait till current execution ends]: When firing trigger, if the script is being executed when the trigger fires, waits for it to end and then fires.	The calculation of execution starting time when [Wait till current execution ends] is selected Execution start time can be calculated with the difference of "Earlier trigger estimate execution start time + Execution interval" and the current time. When the execution start time is earlier than the current time, the trigger fires right after the earlier trigger ends.
Start date of valid duration	Select when the schedule starts to be valid. [Start immediately after registration]: (default) The schedule becomes valid at the same time since the trigger is registered. [Specify start date]: Schedule will become valid since the specified date.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20"-> becomes valid from 20 October, 2005 Date can also be selected directly from calender(launch by Down button).
End date of valid duration	Select when a schedule become disabled. [Execute indefinitely]: (default) Valid until DataSpiderServer stops. [Specify end date]: Schedule is valid until the specified date, and becomes disabled from the next day.	The default value is the current date. The format is "yyyy/MM/dd". (yyyy = year, MM = month, dd = day) Example: "2005/10/20" -> disabled on 21 October, 2005. Date can also be selected directly from calender(launch by Down button).

Common settings

Holiday actions settings

Item name	Content	Remarks
Holiday action	[Execute on holiday]: (default) The trigger fires even on the holidays specified in [Holiday settings]. [Do not execute on holiday]: The trigger does not fire on the holidays specified in [Holiday settings]. [Execute on the day before]: If the target day is a holiday specified in [Holiday settings], move to one day earlier until its a non-holiday, and the trigger fires at that day.However, if the calculated date exceeds the limit of [Start date of valid duration], the trigger will not be fired and the not executable situation is output to the log. [Execute on the day after]: If the target day is a holiday specified in [Holiday settings], move to one day later until its a non-holiday, and the trigger fires at that day.However, if the calculated date exceeds the limit of [End date of valid duration], the trigger will not be fired.	[Execute on the day before] and [Execute on the day after] are disabled when Daily or Interval is selected in "Schedule trigger settings".
Holiday settings	[Default Calendar] : (default) The calender setting with Saturdays, Sundays and holidays set as holidays. [Custom]: Holiday settings can be defined by user individually.

Property Action

Item name	Content	Remarks
Open Holiday Settings	"Holiday Settings" property opens.	Refer to here for more information about holiday settings.

Execution content settings

Item name	Content	Remarks
Trigger owner	Select the owner of the trigger to be created.	Can only be selected by users with administrator privileges. (Ordinary users can select themselves only.)
Execution user name	Select the user to run script specified by [Script].
Password	Type the password associated with the user specified by [Execution user name].
Service	Select the script to run by trigger.	Project that was registered as a service displays.
Script	Select the script to run by trigger.	Script in the service specified by [Service] displays.
Script arguments	script input variables that is set in script specified by [Script] displays	The script output variable does not display. Refer to "Input variable / Output variable" for how to set script input variable on script and use it.
Script arguments / Variable name	Script variable name is displayed.	Can not be edited.
Script arguments / Type	Script variable number type is displayed.	Can not be edited.
Script arguments / Value	Enter a script variable value.	Environment variables can be specified from [Advanced Settings window].

Execution option settings

For more information about Setting execution option, refer to "Execution option settings".

Time input fields

[Execution start time], [Execution interval (h'm"s)], [Specify time range] of input field, such as how to set the following values.

Want to change "when" and "Minute" "second" ([Execution interval (h'm"s)] only) Highlight and drag the numbers on the right input field"▲""▼"or keyboard button"↑""↓"Please key.
Increase or decrease correspondingly to the value of the time.
Want to change "when" and "Minute" "second" ([Execution interval (h'm"s)] only) in focus between the two digits of the input field right"▲""▼"button or keyboard "↑ "↓" Please key.
Increase or decrease correspondingly to the value of the time.
You can also set a time by entering directly.

Specification Limits

Should holiday settings defined in the [Holiday settings] cannot found, error will occur.Do not delete holiday settings that are in use.

Main exceptions

Nothing.

Notes

After registering trigger, if you change the status of the services and scripts that are set to trigger (or add/delete script variables, change service name/script name), those changes are not reflected in the registered trigger.
Open the properties of the target trigger, after re-selection of services and scripts Click [Finish] to re-register.

These changes will not be reflected in a trigger in execution at interval schedule setting, even if contents of [Holiday settings] specified by trigger changes after select [Execute at regular intervals even during script execution] at [Launch limitations] and register.
Open the properties of the target trigger, click [Finish] button to register again.

When multiple [Execution day of the week] are selected Weekly, the execution schedule in one day of the week may be duplicated.In that case, it will only be executed once for a day.

Example: [Execution start time] to [Thursday] and [Friday] when set to 11/23 (Thu), 11/24 (Fri) movement
- [Holiday action]:[Execute on the day after]
- [Holiday settings]: [Default Calendar]
  (In this example, 11/23 (Thursday) is set to holiday)

In the interval schedule settings, when [Execution time] is [Specify time range] and the current time is before [Start] date/time, the execution date/time of the trigger is set as the [Start] date/time.

In the interval schedule settings, when [Execution time] is [Specify time range] and the current time is between [Start] and [End] date/time, the execution date/time of the trigger is set as follows.
1. Set start/end date/time based on the date/time of [Start] and [End].
2. Adds [Execution interval (h'm"s)] to the current date/time until it passes the start date/time.(The value adding [Execution interval (h'm"s)] to start date/time is "evaluation time")
3. When start time <= Evaluation time <= End time, set the evaluation date/time as execution date/time.
4. When evaluation date/time > end date/time, add 1 day to the start date as the execution date/time.

In the interval schedule settings, when [Execution time] is [Specify time range] and the current time has already passed the [End] date/time, the execution date/time of the trigger is set as follows.
1. Set start/end date/time based on the date/time of [Start] and [End].
2. Adds [Execution interval (h'm"s)] to current date/time.(The value adding [Execution interval (h'm"s)] to current date/time is "evaluation time")
3. If the evaluation date/time has not passed the start date/time, adds [Execution interval (h'm"s)] to the evaluation date/time until it passes the start date/time.
4. When start time <= Evaluation time <= End time, set the evaluation date/time as execution date/time.
5. When evaluation date/time > end date/time, add 1 day to the start date as the execution date/time.
Example: Current date and time "12/1 18:00", and the interval schedule is set as follows

Execution interval (h'm"s) Execution time Start End Start date of valid duration End date of valid duration

08'00"00 Specify a time range 03:00 09:00 12/1 Execute indefinitely
1. The [Start], [End] time of 12/1 has passed, so sets the start date/time "12/2 03:00" and end time "12/2 09:00" on 12/2.
2. Current date/time "12/1 18:00"< Start date/time, "12/2 00:00", so add [Execution interval (h'm"s)] 08'00"00 to the current date/time.
  -> Evaluation date/time will be "12/2 02:00".
3. Start time "00:00"<= Evaluation time, "02:00" <= End time "09:00", so set the evaluation date/time as execution date/time.
  -> execution date/time will be "12/2 02:00".
Example: Current date and time "12/1 18:00", and the interval schedule is set as follows

Execution interval (h'm"s) Execution time Start End Start date of valid duration End date of valid duration

08'00"00 Specify a time range 03:00 09:00 12/1 Execute indefinitely
1. The [Start], [End] time of 12/1 has passed, so sets the start date/time "12/2 03:00" and end time "12/2 09:00" on 12/2.
2. Current date/time "12/1 18:00"< Start date/time, "12/2 03:00", so add [Execution interval (h'm"s)] 08'00"00 to the current date/time.
  -> Evaluation date/time will be "12/2 02:00".
3. Evaluation time "02:00"< Start time, "03:00", so add [Execution interval (h'm"s)] 08'00"00 to the evaluation time.
  -> Evaluation date/time will be "12/2 10:00".
4. Evaluation time "10:00"> End time, "09:00", so add 1 day to the start date "12/2 3:00" as the execution date/time.
  -> execution date/time will be "12/3 03:00".

When the [Execution time] of interval schedule settings is [Execute for 24 hours] and the [Start date of valid duration] is [Start immediately after registration], adds [Execution interval (h'm"s)] to 08'00"00 of the register day, and find a time that is future than current time as the execution time.

Example: Current date and time "12/1 18:00", and the interval schedule is set as follows

Execution interval (h'm"s) Execution time Start date of valid duration End date of valid duration

08'00"00 Execute 24 hours Start immediately after registration Execute indefinitely
1. Add [Execution interval (h'm"s)] to 08'00"00 of the register day "12/1" .(12/1 08:00:00, 12/1 16:00:00...)
2. Because "12/2 00:00" is in the future than the current time, it is set as execution date/time.
  -> execution date/time will be "12/2 00:00".