Control Server Configuration Parameters
Control Server Configuration Parameters
You can change default Control Server configuration parameter in the Administration → Control Server Configuration
For scope = CS you need to restart Control Server container to apply the new value.
$ docker-compose restart control-server
Here are the list of available parameters that intended to be configurable for administrators:
| Parameter name | Parameter type | Default value | Scope | Description |
|---|---|---|---|---|
| service.batch_size | number | 50 | CS | Defines number of record that will be used to process stopping/deleting runs |
| remoteExecutionService.splitCapacity | number | 30 | AP | The number of threads to use for all split tasks (split() methods) in execution service, i.e. the number of flow that could be running in parallel at the same time. If an Automation Process injects more flows that this parameret, the first splitSize flows will be running, the next flow will be executed asap an already executing flow finished. |
| remoteExecutionService.splitSize | number | 5 | AP | The number of threads to use for a specific split tasks flow in execution service, i.e. the number of flow that could be running in parallel for a specific split at the same time. It could be deadlock in your AP code if you use split in split, because of limit of the remoteExecutionService.splitCapacity. This parameter should depends of number of split in split tou are goung to use in your AP: splitCapacity> splitSize exponential(splitLevel) The default settings do not provides blocking for 2 level splits. |
| remoteExecutionService.maxSplitSize | number | 20 | AP | The maximum number of threads to use for a specific split tasks in execution service. The execution flow could be blocked on Human Task, in this case the execution service creates a new flow (the blocked on HT are still active). This number specified the overall flows that could be created. |
| remoteExecutionService.taskTimeout | number | 90 | AP | Task timeout in minutes. If task is running more that it specified here, the automation process that injects the task will be moved into STOPPED_IDLE status till the task completes. |
| remoteExecutionService.taskErrorTimeouts | JSON | {} | AP | Defines specific task error timeout as a map in the following way: {
".*HumanTask": 5,
".*MlTask": 2
}where key is regexp of task class and value is timeout in minutes. The specific task will be moved into error state after its timeout is elapsed. |
| remoteExecutionService.enableLocalExecution | boolean | true | AP | Parameter for execution service to run task without capabilities on the orchestrator node. Set it to false slows down execution, i.e. all tasks will be assigned of free nodes. |
| notification.channels.config | JSON | see the Notification Service | CS | Defines notification channels settings. |
| queue_max_length | number | 250 | CS | The maximum number of task that could be in Control Server queue and waiting appropriate node to deploy for execution. |
| queue_scan_sec | number | 30 | CS | Sleep interval in second during processing Control Server task assignment queue. |
| human_task_max_lock_time_in_min | number | 30 | CS | The maximum number of minutes that Human Task could be in IN_PROGRESS state, after expiration it will returned back and AVALIABLE to another users. |
| data_purge_keep_days | number | 90 | CS | The maximum number of days to keep data for executed runs. |
| data_purge_purge_interval_days | number | 1 | CS | The period in days to perform data purge (i.e. purge data every N days and remove all runs that older data_purge_keep_days). The data_purge_purge_interval_days must be < data_purge_keep_days |
| data_purge_connection_timeout_min | number | 10 | CS | Connection timeout for HTTP request in minutes. Depends on data purge size. Should be increased if DataPurge logs contains timeout errors. |
| store.ap.package | boolean | false | CS | Store imported AP packages. If true the imported AP will be available for download for APs. |
| store.ap.package.max.count | number | 100 | CS | The number of packages to store. |
| ENGINE_ARTIFACT_ID | string | eu.ibagroup:easy-rpa-engine:jar:<version> | AP | The easy rpa engine artifact id to use for run AP on nodes. |
| human_task_daemon_interval_in_sec | number | 30 | CS | Daemon interval to check Human Task expiration timeout. |
| cs.ldap_url | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_root_dn | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_user_dn_patterns | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_user_search_filter | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_manager_dn | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_manager_password | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_mail_attr | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_sn_attr | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_fn_attr | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |
| cs.ldap_user_attr | string | see the LDAP Integration | CS | Defines LDAP Integration setting. |