Custom Http Call

[water01]

I saw this included "at rollover" and didn't read the following bit properly, and just assumed that I could FTP a file "At End of Day" and then use the at Rollover function to run the Import process to my database.

Did NOT notice those words saying "just before"!! Any chance of there being a "5 mins after option"?

[beteljuice]

Just before is "end of day" isn't it ?

[HansR]

A free to define nr of minutes after rollover would be nice. Not only for custom http but also for run of external program..

[PaulMy]

David, would using the Minutes interval be feasible? i.e. 1440 set at 00:05
I haven't tried it and not sure what the maximum minutes, or seconds, are.

Enjoy,
Paul

[Mapantz]

David, would using the Minutes interval be feasible? i.e. 1440 set at 00:05
I haven't tried it and not sure what the maximum minutes, or seconds, are.

Enjoy,
Paul

I'm not sure it works like that.

You could manage it once by putting in 1441 and hitting save right at the stroke of midnight, but it'll not work again if CMX has to be restarted.

[mcrossley]

Be aware that the extra files are processed (and copied) during the day reset, but will not be FTP'd until the next FTP interval, which is asynchronous to the day reset.

The best way of doing stuff like this is to take control of it yourself...

The "external program" is called at the end of day reset processing (but before the end of day extra files processing - hmm, maybe that should change). I'd use that to call a script to do whatever you want, that could include a 5/10 minute delay at the start if you wish.

For instance I use it to run a database export and then backup the Cumulus data files, the dB export, and my web site to an external server.

[HansR]

The "external program" is called at the end of day reset processing (but before the end of day extra files processing - hmm, maybe that should change). I'd use that to call a script to do whatever you want, that could include a 5/10 minute delay at the start if you wish.

Not sure if the reversal of the "external program" and the "end of day extra files processing" would be a good idea. If the external program creates a file which should be processed, reversal would mean the processing would only take place a whole cycle later. That's probably not intended by the user.

NOTE: that is already taking place at the 'FTP' cycle (the NOT daily and NOT realtime cycle). The uploaded processed file is produced one cycle before.

[mcrossley]

Not sure if the reversal of the "external program" and the "end of day extra files processing" would be a good idea. If the external program creates a file which should be processed, reversal would mean the processing would only take place a whole cycle later. That's probably not intended by the user.

Agreed, there are use cases for having it either way around. But it's been that way round forever, so it stays that way.