For scheduled HD jobs, configure the processing schedule, the connection to the ibaHD-Server, and the query period in addition to the default settings. For scheduled jobs, the server connection settings are not required.

For information on the default settings, see Configuring a job. Detailed information about the job types can be found in Scheduled HD job and scheduled job.

General settings

In the General settings area, you can make the settings for the starting time and the period of execution.

Enabled

The job will only be executed if this option is enabled.

Automatically start on load

When enabled, the job starts automatically as soon as the XML configuration file has been loaded. This is the case if you load the configuration manually via the File – Open menu, or if the ibaDatCoordinator client or service starts.

Retry failed operations of previous session

Enable this option if you want to ensure that operations that could not be completed in the previous session are repeated.

Retry failed operations every ... minutes

Set the time after which failed tasks, including HD queries, that are marked as failed will be performed again. ibaDatCoordinator only performs these tasks again.

Retry failed operations maximum ... times

Here you can define how many times the attempt will be made to reprocess am HD query. If the maximum number of attempts has been performed without success, the HD query is added to a file list of continuously failed DAT files.

If you disable this option, ibaDatCoordinator will not stop trying to process HD queries marked as failed.

Disable the data availability check

By default, ibaDatCoordinator checks whether data is available in the configured HD stores and ignores empty stores. If you enable this option, empty HD stores will also be included in processing.
Schedule

With these settings allow you to specify when ibaDatCoordinator should execute a job and process the configured tasks.

Start

Enter the time for the first job execution here. A calendar function is available for the date; you must enter the time manually in the format HH:MM:SS.

This point in time is decisive for all periodic executions, whether on a daily, weekly or monthly basis.

Then define whether the job is to be executed just once or every day, every week or every month. Depending on the period, additional settings options are displayed:

One time

Daily

Enter the intervals, calculated in days, at which the trigger is to be tripped. Number = 1 means every day.

Weekly

Enter the intervals, calculated in weeks, at which the trigger is to be tripped. Number = 1 means every week. Select the day of the week on which the trigger is to be tripped. You can select multiple options, e.g. on Monday, Wednesday and Friday. Thus, you can configure daily execution week by week.

Monthly

Select the month(s) in which you want the files to be processed. You can choose between execution on one or more days of the month or on certain weekdays of the month.

Repeat trigger

This option allows you to additionally schedule the job to run on an hourly or minute basis. If this option is enabled, execution will take place according to this fine-tuning within the higher-level planning (daily, weekly, or monthly).

In the first field, select the number of repetitions for the trigger. In the second and third fields, select the time interval at which the trigger is to be repeated.

With the number, determine how often the trigger will be repeated after the first trigger of the day/week/month.

  • Number of repetitions = 1: After the first trigger, the trigger will be tripped once more in the set interval.

  • Number of repetitions = 2: After the first trigger, the trigger will be tripped twice, each time at the set interval.

  • More values corresponding

  • Number of repetitions = infinite: After the first trigger, the trigger will be tripped again and again at the set interval until a new (main) trigger is tripped.

    This setting is useful if, for example, you want to run a task every 10 minutes over a 24-hour period on a daily basis. In this case, you do not have to calculate the number of repetitions (1440).

Example

With the Repeat trigger option, you can have a job executed several times a day, e.g. for creating shift reports.

Select a daily execution, starting at 6:00 a.m. and repeating the trigger every 8 hours. In combination with the time range of 8 hours for the HD query and a report task, you will receive 3 shift reports a day for the times between 10 p.m. and 6 a.m., 6 a.m. and 2 p.m., and 2 p.m. and 10 p.m.

Process triggers in the past

If activated, ibaDatCoordinator restarts processing after the last processed time range instead of from the configured start time. If ibaDatCoordinator cannot process certain time ranges (e.g. because the server is not available due to maintenance work), processing is continued with the next "unprocessed" trigger instead of waiting for the next trigger and skipping the missed triggers.

To reset the saved time range, click on thebutton. Processing starts from the configured start time when the job is restarted.

<Next trigger info>

This button opens a window listing the next 10 calculated trigger times with the corresponding time ranges of the HD queries.

<Trigger now>

For test purposes or if you want to trigger spontaneously, you can click on the <Trigger now> button. This button is only available if the job has been started (<GO>).
Time selection

With the setting in the "Time selection" area, you can determine the time period from which the measurement data are originated.

Start and Stop

Set the start and end of the query period under Start and Stop. The Start must be further in the past than the Stop.

Both entries refer to the trigger time.

Use previous trigger time

Select this option to use the time of the last trigger as the start time for the query period. This way, you can reliably implement a complete query. Additionally, set "0" for all fields at Stop (from trigger to trigger).

Preferred time base

Similar to HD queries with ibaAnalyzer, you can select a preferred time base. Depending on the setting of the time ranges and the number of samples contained therein for the HD query, the range of time bases changes.

If you do not need a specific time base for the query results, use the default setting "auto". This ensures that the query delivers the highest possible resolution, which can be particularly important for subsequent calculations.
ibaHD-Server connection (scheduled HD job only)

Here you can configure the settings for the connection to the ibaHD-Server and the HD store. ibaDatCoordinator requires this information and the following settings for the time selection for generating the correct HD query (HDQ file), which is then transferred to ibaAnalyzer for execution of tasks.

To open the server selection dialog, click the <Select server...> button. Select the desired ibaHD-Server from the table and close the dialog by clicking <OK>.

If user management is enabled for the selected ibaHD-Server, you must then enter a user name and the correct password.

For more information on ibaHD-Server connection and user management, see Establishing ibaHD-Server connection

Now select the desired HD store where the measurement data is stored under HD store selection. If you select multiple stores, the query criteria are applied to all selected stores. All data in the result of the HD query is processed by the job.