DCM application has several system properties that control how the application works within an instance. System admin role is required to change some or all of these properties.
Going through properties is part of the DCM Guided Setup where some of these are explained in more detail. Otherwise properties can be found from the Navigation menu under Basic Setup >> Properties.
| Name | Description | Default value |
| x_jugr_dcm.notification.enable | Global setting for enabling or disabling notifications sent by DCM. Currently related to certification and remediation tasks. | false |
| x_jugr_dcm.license.send_report | Send DCM license report to DCM Support ([email protected]) | true, in production. false, in non-production instances |
| x_jugr_dcm.uam.auto_expire | Turn on automatic expiration of unupdated Unique Audit Messages that are still Open | true |
| x_jugr_dcm.uam.expiration_days | If automatic UAM expiration is enabled, then Open UAMs that have not been updated will be set to Expired after a given number of days. | 7 (used to be 31) |
| x_jugr_dcm.audit.run_parallelism | Number of simultaneous processes (1 to 8 ) used when handling scheduled audit run execution | 2 |
| x_jugr_dcm.audit.scheduled.chunk_size | Batch size of a scheduled audit run. The audit will split Audited Records into batches and handle them in a queue. The optimal batch size is between 100 and 250. | 250 |
| x_jugr_dcm.uam.weighing.chunk_size | Batch size for weight calculation of related Unique Audit Messages (UAM). This calculation occurs after the audit instance has been completed and will update weight values on all related UAMs. | 1000 |
| x_jugr_dcm.audit.scheduled.max_root_record_count | Maximum number of root records allowed for a scheduled audit | 60000 |
| x_jugr_dcm.audit.ondemand.max_root_record_count | Maximum number of root records allowed for an on demand audit | 1000 |
| x_jugr_dcm.task_domain | The default task domain on domain separated instances, use domain sys_id | (not set) |
| x_jugr_dcm.audit.check_multiplicity_backward | Should audit evaluate multiplicity backward while evaluating a container link against a record | false |
| x_jugr_dcm.excluded_rel_tables | List of tables to exclude from relationship tabl list. Each table name should be seperated with comma ( , ). | sys_event, ecc_event |
| x_jugr_dcm.logging.verbosity | Debug log level for DCM application scripts | warn |
| x_jugr_dcm.logging.destination | The target for DCM logging messages | db |
In most cases, the default value is OK for normal use of DCM in a production instance. On the other hand, the following properties often have non-default values:
- x_jugr_dcm.notification.enable
- x_jugr_dcm.audit.run_parallelism
In addition to these properties, DCM License Keys are also set as system properties. You can find more information about license keys here.