The ProTop scheduler configuration can instruct the DBMonitor process to execute tasks.
The configuration file follows Unix cron syntax, with the addition of the “[NOALERT]” modifier. By default, an information (blue) alert is uploaded to the ProTop web portal when a scheduled process is executed. The addition of [NOALERT] parameter prevents that upload. Read the top of the scheduler.cfg file for more detail.
Note: If you do not already have a localized version, copy etc/schedule.cfg to etc/schedule.[*].cfg. e.g. etc/schedule.yourCustId.cfg or etc/schedule.yourServerName.cfg. Edit your localized file and not the original etc/schedule.cfg file, which is overwritten at each update of ProTop.
foreachdb.sh[bat]
As found in [PROTOPDIR]/etc/schedule.cfg, foreachdb.sh will execute the given command against listed databases in etc/dblist.cfg AND which have the “monitor” flag set to “yes” AND which belong to the current server. It does not work with every ProTop script or batch file, i.e. hc.[sh|bat], so test and check the logs.
The -param is supposed to be the command to run, not the list of databases. The command will be fed the dbPath and friendlyName, which is assumed to be in that order.
On Windows
If you want to have the ProTop Scheduler run jobs in parallel, be sure to give each command a unique file name and put the "run it in the background" qualifier, "&" at the end of the line.