The document describes new functions in version 2.4.1 of ibaDatCoordinator including the ability to re-process existing HD data in arbitrary time ranges for scheduled jobs, open and modify analysis files used in tasks directly from within ibaDatCoordinator, and notes on using reports with remote configuration.
The document describes new functions in version 2.4.1 of ibaDatCoordinator including the ability to re-process existing HD data in arbitrary time ranges for scheduled jobs, open and modify analysis files used in tasks directly from within ibaDatCoordinator, and notes on using reports with remote configuration.
The document describes new functions in version 2.4.1 of ibaDatCoordinator including the ability to re-process existing HD data in arbitrary time ranges for scheduled jobs, open and modify analysis files used in tasks directly from within ibaDatCoordinator, and notes on using reports with remote configuration.
The document describes new functions in version 2.4.1 of ibaDatCoordinator including the ability to re-process existing HD data in arbitrary time ranges for scheduled jobs, open and modify analysis files used in tasks directly from within ibaDatCoordinator, and notes on using reports with remote configuration.
This document describes the new functions added to ibaDatCoordinator v2.4.1.
1 Re-process HD data In version 2.4.0 of ibaDatCoordinator we added an option to the Event Job to re- process existing events in arbitrary time-ranges. For the Scheduled Job we added a similar option.
When the option “Process triggers in the past” is selected, ibaDatCoordinator starts to process data from the HD-Server beginning with the selected date and time. Similar to the Event Job, this is a “one-time-option”. This means that when this option is selected and the job is started, ibaDatCoordinator begins to process the data and removes the checkbox again. When the job is stopped and started again the option is not automatically enabled again. To check which time-ranges are processed once you press the start button, use the button “Next trigger info” to check the triggers. 2 Open and upload Analysis files Every task where a pdo can be selected for configuration (Report, Extract, Condition, Splitter, HD offline events, and some plugins) has three buttons next to the pdo-selection-field.
1. Select a pdo using a file browser. If the ibaDatCoordinator service is on a remote
machine, it is possible to browse on this machine instead. 2. Open (a copy of) the selected pdo with ibaAnalyzer. 3. Upload the modified pdo (or apply changes) These buttons work as follows: When a pdo is opened via button 2, ibaDatCoordinator creates a local copy of the original pdo. If the ibaDatCoordinator service is on a remote machine, the original pdo is downloaded first and then the copy is created. You can see in ibaAnalyzer that the pdo name has a “_(ibaDatCoordinator)” suffix attached.
Modifications are saved to this copy and are transferred (or uploaded in case of a remote DatCoordinator service) when pressing button 3 or when changing the configuration tab. ibaDatCoordinator automatically detects any changes to the pdo.
If no changes are detected, the file will not be replaced.
2.1 Note on Reports In case of remote configuration, ibaDatCoordinator automatically copies the last modified *.lst file (which is needed for the Report Task to work) from the folder where the analysis is located. This means in order for the remote configuration to work with Report Tasks you need to place the report configuration next to the analysis. We recommend to use a separate folder for both files.
