Generally, ARIS Risk & Compliance Manager provides two options for starting automated server tasks in order to generate or change objects. You can trigger a server task manually using the ARIS Risk & Compliance Manager interface if you have the corresponding manager role. Or the server task is executed according to schedule by ARIS Risk & Compliance Manager. For example, this applies to generator and monitoring server tasks in the default configuration. Scheduled server tasks are configured by ACC commands.
While most of the configuration parameters are simple key value pairs, the configuration of server task scheduling is more complex. Server task configuration parameters always start with arcm.config.schedule.job, followed by the server task type (generator, monitor, updater), and then by the object type for which the server task is responsible. The cleaning server task does not have this object type appendix. The value of such a server task parameter is built up as a sequence of key value pairs, grouped by enclosing braces []. Key and value are separated by the pipe character (|).
Example
reconfigure arcm_m arcm.config.schedule.job.generator.testcase=[ jobitem | generatorJob ] [ startScheduler | true ] [ executionTime | 0 52 00 ? * SUN-SAT ] [ clientexcludinglist | ] [ clientincludinglist | ] [ objecttypes | TESTCASE ]
The individual parameters have the following meaning:
The server task to be executed. The parameter value must correspond to an EnumItem ID from the jobs enumeration in the enumerations.xml file.
Must be true so that the time control for this server task is active.
This expression states at which point in time the server task should be started. It has the format CronTrigger that allows the specification of time intervals.
The individual values mean the following from left to right:
In the example above, the monitor server task for checking test cases on each day of each month starts at 01:52. For further information, see the CronTrigger documentation on the Quartz home page.
The environments in the ARIS Risk & Compliance Manager database for which the server task should not be executed are listed here. The values can be specified separated by commas. This applies to environment specific server tasks only.
The environments in the ARIS Risk & Compliance Manager database for which the server task should be executed are listed here. If no value is specified, a separate server task is started for each individual environment. The values can be specified separated by commas. This applies to environment specific server tasks only.
The object types for which the server task should be executed. In the example above, this instance of the monitoring server task should only check the test cases. The values can be specified separated by commas.