You might have to do this outside the FDMEE batch scheduler.

Simplest way would be to write batch script that checks for files and launches the batch via command line if files are present. You can then schedule this batch script via any scheduling tool.

Hi Ross,

I have the same issue that you do with openbatch being run without files being present. Did you find any built in solutions?

Also how did you manage to set the batch to run each 15 min, as the lowest frequency it seems to allow is hourly?

Any information would be much appreciated,

Thanks you in advance,

Marina

It is on the road map.

In the meantime, as suggested, you can use external file watcher or have a custom script after batch which deletes all batch details in the database and batch folder if no files were processed. Second option may require some database housekeeping every night (rebuilding indexes, shrinking....)

Hi Francisco,

What about the scheduling with minute frequency? Is it possible with 11.1.2.3.5?

Unfortunately, unlike FDM Classic, the out-of-the-box batch processing scheduler in FDMEE only goes down to an hourly interval.

To execute every 15 minutes you could create one schedule for on the hour, another for 15 past the hour, another for 30 past the hour, and one more for 45 past the hour.

You really have more control using the Windows Batch/UNIX shell scripts with a third party scheduler.

Thanks both for your prompt reply.

I would dare to ask, is there a way to run openbatches using Windows Batch/UNIX shell scripts?

Thank you,

Marina

I don't think this is currently supported by the 'out of the box' functionality. It would be individual data load rules than can be co-ordinated using batch scripts and external schedulers. That is not to say you could not set up a custom batch script process to mimic the functionality of the openbatch operation

Are you talking about this one:

"To run the batch with a plain text password, at a Windows command window or UNIX

runbatch USER PASSWORD LOCATION_NAME SYNC_MODE"

-    where the LOCATION_NAME is the openbatch name?

yup