...
This can only be done by suitably authorised users, and should follow a carefully defined scheduling plan. These users must have access to the admin interface tool (see Admin Interface manual).
A run that is to be enhanced must have already been submitted to the Master Controller and available in the Scheduled Forecasting Lists. The run is identified by its tag available in that list.
The actions that can be defined are;
...
For each an appropriate action configuration must be defined. A task that is to be enhanced, changed or a oneoff task that is to be submitted must have already been scheduled to the Master Controller and available in the Scheduled Tasks Lists as a suspended scheduled task. The run is identified by its tag available in that list.
The procedure in defining an action config is.
...
NOTE: when deleting action configurations, the Action Event EventAction Mapping must be deleted first due to relations in the database.
...
Note3: It is recommended to set the interval to 1 second if the action should be executed for every event code (e.g. in the case of sending alert messages), but should be increased if it is not desirable to execute several workflows in a short period (e.g. the case of creating web reports). It also needs the "template task" with the relevant tag scheduled (in suspended mode) as a single/one-off task.
Example of a scheduled (and suspended) task in the Admin Interface
| Code Block | ||
|---|---|---|
| ||
<task>
<taskStatus>S</taskStatus>
<taskTag>import_hirlam_dim</taskTag>
<runOnFailOver>false</runOnFailOver>
<taskProperties>
<workflowId>Import_DIM_HIRLAM</workflowId>
<taskSelection>
<singleTask>
<time0>2014-01-13T14:56:00.000Z</time0>
</singleTask>
</taskSelection>
<forecastPriority>Normal</forecastPriority>
<makeForcastCurrent>true</makeForcastCurrent>
<makeStateCurrent>true</makeStateCurrent>
</taskProperties>
</task>
|
Dual MC with failover mode triggers suspended tasks with runOnFailOver from remote MC
...