Navigation:  IM Sequencer > Schedule tasks >

Example scenarios

Previous pageReturn to chapter overviewNext page

Below are a couple examples for typical scenarios what you can do with scheduled tasks

Scenario 1:


Run every hour starting from 5:00 o'clock in the morning until 22:00 in the evening.
When the time is reached (for instance 6:00) copy a file from a source system in the network (//FILESRV001/ImportData/ImportData.csv) to the MAData directory for a specific import management agent. When the file is copied start the management agent that will import the file in the synchronization service that synchronizes the data within that import file.
The file will be checked for integrity, if there are for instance "1000 deletes" within the file. This can be blocked for synchronization because this could be an error when the file is generated or transported across the network.

Send a reports to configured recipients when the managements agent occurred errors during the synchronization, this reports will clearly show what is causing problems and corrective measures will be taken.
When the import file is processed copy this file to a specific directory "ProcessedImports"  and leave it there for 30 days.
Task contains:

Triggers: Hourly trigger that starts at 5:00 and ends on 22:00

Steps: 1) FileCopyMove step that copies the file

       2) SequencerStep stat executes the steps runprofiles and send a report

Scenario 2:


When there is data awaiting to be synchronized either in Omada or in the FIM portal execute the task.
When the task is started check if specific managements agents or other tasks are not running (start conditions). if they are not, the management agent is started and synchronizes the data that was pending in either Omada or FIM.
Task contains:

Triggers: Omada or FIM Trigger that checks for pending data

Steps: 1) SequencerStep stat executes the steps runprofiles and send a report

Conditions: Check if task "X"  and Management agent "Y" is not running
Scenario 3:


When there is pending (export/import) data available in a management agent the management agent could be started directly to only perform this export if there is data available. And no longer runs even if there is nothing to do. When the management agents generates a export file, deliver this export file to a shared directory on the network and upload it to an FTP server.


Task contains:

Triggers: Management agent trigger that checks for pending "export/import" data


       2) FileCopyMove step that delivers the export file.

       3) External process step that uploads the export file using for instance WinSCP.


Scenario 4:


Run every 1st day of the month at 0:00


When the 1st day of the month is reached execute a cleanup process that clears "stale" data within Omada


Task contains:

Triggers: Monthly trigger that starts on the first day of every month

Steps: 1) External process step stat executes application or script file



Page url: