...
In order for the master controller (and Forecasting Shell Server) to run properly several maintenance workflows must be scheduled. These workflows make sure the database does not overflow (they run the rolling barrel) and that configuration marked to be removed using the Configuration Manager actually gets deleted. In addition, each FSS must also run a rolling barrel task, usually once a day. This task runs the rolling barrel on the FSS and deletes configuration marked for deletion.
- MC:_MarkedRecordManager - Removes records marked for deletion. This removes static entries only.
- MC:_Synchronisation - Syncronise Synchronise between several master controllers, only needed on duty standby systems
- MC:_RollingBarrel - Removes expired records from the MC database (e.g. timeseries, model states etc)
- MC_SystemAlerter - Optional, used for triggering emails on log event codes.
- RollingBarrel_FSS00 FSS (one for each FSS) - Removes synchronises the localDatastore and removes expired records from the FSS database
...
- .
...
Scheduling the workflows using the Administrator Interface (AI)
First, each workflow must be uploaded. For each of the MC workflows this is the same dummy workflow. In the AI go to the Workflows and FSSs -> Workflow menu and choose upload new workflow to do this.
| Info |
|---|
Please note that the Rolling Barrel for the FSS is a 'real' workflow (it can be run stand-alone) and should be uploaded using the Configuration Manager. |
| Info |
|---|
| Warning |
Please note that as of release 2009.01 Master Controller related tasks and workflows do not require upload of workflows anymore , and can directly but are automatically created. They can be scheduled as described here. Following the steps described below to upload MC worklows is no longer required. |
...